CtrlK
BlogDocsLog inGet started
Tessl Logo

webflow-automation

Automate Webflow CMS collections, site publishing, page management, asset uploads, and ecommerce orders via Rube MCP (Composio). Always search tools first for current schemas.

60

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/webflow-automation/SKILL.md

The canonical home for this skill is webflow-automation in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, actionable reference for Webflow MCP automation with clear sequenced workflows and explicit destructive-operation safeguards. Its main weaknesses are redundant pitfalls/quick-reference content that hurts conciseness and the absence of error-recovery feedback loops.

Suggestions

Remove the duplicated pitfalls: keep them either inline per workflow or consolidated under 'Known Pitfalls', not both, to tighten token use.

Add an explicit error-recovery feedback loop for destructive/batch operations (e.g., on 403, check OAuth scopes and reconnect; on publish rate-limit, wait and retry).

Consider moving the Quick Reference table and detailed field-value type mappings into a reference file to improve progressive disclosure now that the body exceeds 200 lines.

DimensionReasoningScore

Conciseness

The body is mostly efficient and information-dense, but pitfalls are stated twice (once per workflow's 'Pitfalls' subsection and again consolidated in 'Known Pitfalls') and the Quick Reference table rehashes tool slugs already listed in the sequences, which could be tightened.

3 / 5

Actionability

Provides concrete tool slugs, named parameters, field-value type mappings, and exact regex patterns for IDs — actionable MCP guidance with only minor gaps (no full example request payloads).

4 / 5

Workflow Clarity

Each workflow is a clearly numbered tool sequence with prerequisite/optional tags, and destructive operations carry explicit confirm-with-user and ACTIVE-status checkpoints; it falls short of 5 only because explicit error-recovery feedback loops (validate -> fix -> retry) are absent.

4 / 5

Progressive Disclosure

Content is well-organized into clear sections (Prerequisites, Setup, Core Workflows, Common Patterns, Quick Reference) with no nested references, but everything is inlined in a single ~240-line file with no bundle files to defer detail to.

4 / 5

Total

15

/

20

Passed

Description

75%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and distinct, naming concrete Webflow operations with clear domain scoping, but it omits an explicit 'Use when...' trigger clause, which caps completeness at 3. Trigger-term coverage is good though not exhaustive of synonyms.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases (e.g., 'Use when managing Webflow CMS content, publishing sites, uploading assets, or retrieving ecommerce orders').

Include a few synonym/variant trigger terms (e.g., 'Webflow CMS', 'Webflow ecommerce', 'publish a Webflow site') to broaden natural-language matching.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'CMS collections, site publishing, page management, asset uploads, and ecommerce orders' — giving comprehensive coverage of the Webflow automation domain, matching the anchor for multiple specific concrete actions.

5 / 5

Completeness

The 'what' is explicit and concrete, but there is no 'Use when...' trigger clause — 'Always search tools first for current schemas' is an instruction rather than usage guidance, so per the rubric cap completeness is held at 3.

3 / 5

Trigger Term Quality

Includes natural terms users would say ('Webflow CMS collections', 'site publishing', 'asset uploads', 'ecommerce orders'), but lacks synonym variations and there are no file extensions to cover, so it falls just short of the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

'Webflow ... via Rube MCP (Composio)' carves out a clear niche with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.