Pre-install eval

webflow-mcp:cms-best-practices Eval report.

A machine-readable install decision for agents: task fit, Trust Score, Audit Score, install safety, permission surface, and a concrete validation plan before this skill touches a workspace.

Needs reviewMedium riskREVIEW Policy
68
Eval report
68
Trust
74
Audit
54
Agent safety

manual review

Test manually in an isolated workspace and compare against safer alternatives.

Required gates

Checks an agent must pass before install

Open JSON

Task fit

94

pass

Task wording matches this skill metadata.

  • Evaluate webflow-mcp:cms-best-practices before installing it in an agent workflow
  • design-creative
  • Design and creative workflows; Claude Code teams; builders willing to evaluate younger projects

Install path

92

pass

Install handoff is available.

  • npx skills add webflow/webflow-skills --skill webflow-mcp:cms-best-practices

Install command safety

92

pass

standard package or runtime install path

  • npx skills add webflow/webflow-skills --skill webflow-mcp:cms-best-practices

Trust score

68

warn

Potentially useful, but at least one trust signal needs human inspection.

  • Manual review
  • 114 GitHub stars
  • MIT

Audit score

74

warn

Needs review

  • Permission surface may require sandboxing

Agent safety gate

54

warn

Sparse or mixed signals. Useful for discovery, but not for autonomous installation.

  • Test manually in an isolated workspace and compare against safer alternatives.
  • Permission surface may require sandboxing

License clarity

86

pass

MIT

  • MIT

Permission surface

60

warn

filesystem or document access, network or browser access

  • Network access: medium
  • Filesystem access: medium
  • Database access: medium

Validation plan

What the agent should do next

  1. 1Inspect repository, README/SKILL.md, license, and recent commits before production use.
  2. 2Install in an isolated workspace or sandbox with no production secrets available.
  3. 3Run the smallest representative task and record files touched, commands run, network access, and outputs.
  4. 4Compare the selected skill against at least one alternative when the eval status is review or failed.
  5. 5Promote only after the agent reports a successful verification result and unresolved warnings are accepted.

Do not use when

Conditions that require another skill

  • teams that need a vendor-supported SLA
  • production agents without a repository review
  • 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.
  • Permission surface may require sandboxing
  • 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.

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

pass

86

Metadata includes enough usage and workflow context

Recent maintenance

pass

88

2mo since push

Alternatives available

pass

82

Alternative skills are available for comparison.