webflow-mcp:cms-best-practices Rapport d’audit.

Avertissements

• Permission surface may require sandboxing
• Financial research output is not financial advice; require human review before any live investment decision
• The skill assumes Webflow MCP tools are already configured and available, but does not document setup steps or fallback behavior if the MCP server is unavailable.
• Tool names such as webflow_guide_tool are referenced without explaining their expected schema or availability, which could cause integration failures in environments where those exact tools are not present.
• While the skill uses read-oriented tools, it does not explicitly instruct agents to avoid mutation, publishing, or destructive CMS actions unless the user explicitly requests them.
• Financial research output is not financial advice; require human review before any live investment decision.
• Quality score needs review
• Permission surface needs review: filesystem or document access, network or browser access
• Stars/forks activity: 114 stars, 18 forks; issue activity unavailable in current metadata
• Permission surface: filesystem or document access, network or browser access

Méthode

This report combines public metadata, AI review output, repository freshness, install readiness, OpenAgentSkill events, quality scoring, trust checks, and the agent safety gate. It is not a full source-code security review.