CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

72%

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 ./skills/webflow-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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.

A well-structured, highly actionable MCP tool reference with exact tool slugs, parameter schemas, and per-workflow pitfalls. It is held back by significant internal duplication, no post-action validation for destructive/batch operations, and a monolithic single-file layout with no progressive disclosure layering.

Suggestions

Add validation/feedback steps to destructive and batch workflows: verify a created item with WEBFLOW_GET_COLLECTION_ITEM, confirm publish outcome, and give error-recovery guidance (e.g. retry after the 1-publish-per-minute rate limit, handle 403 by checking OAuth scopes).

Deduplicate: the "Known Pitfalls" section and Quick Reference table largely repeat the per-workflow Pitfalls and tool sequences — keep one authoritative copy and remove the filler "When to Use" section.

Move the per-tool parameter details and Quick Reference table into a references/ file (e.g. TOOLS.md) linked from a concise overview to add progressive disclosure.

DimensionReasoningScore

Conciseness

The body is dense reference material with little concept explanation Claude already knows, but it is noticeably duplicated: the "Known Pitfalls" section restates pitfalls already given per-workflow (field slugs vs display names, publish-all-staged-changes, rate limit appear twice), the Quick Reference table repeats the tool sequences, and the closing "When to Use" section ("This skill is applicable to execute the workflow or actions described in the overview.") is pure filler. Not a 4 because this repetition is substantial rather than minor; not a 2 because there is no padded beginner-level explanation.

3 / 5

Actionability

Concrete, executable guidance throughout: exact tool slugs (e.g. "WEBFLOW_CREATE_COLLECTION_ITEM"), exact parameter shapes ("field_data: Object with field slug keys (NOT display names); must include name and slug"), ID formats with regex ("^[0-9a-fA-F]{24}$"), field value types, and md5 computation rules. Not a 5 because there are no example tool invocations/payloads for the common cases (e.g. a sample create-item call), which would make it copy-paste ready.

4 / 5

Workflow Clarity

The five workflows have clearly numbered tool sequences with prerequisites marked and a validated setup flow (confirm connection ACTIVE before proceeding), but destructive and batch operations (DELETE_COLLECTION_ITEM, PUBLISH_SITE deploying ALL staged changes, paginated iteration) lack post-action verification and error-recovery feedback loops — the only checkpoint is "always confirm with the user". Per the rubric guideline, missing validation/verification steps for destructive/batch operations caps workflow clarity at 3.

3 / 5

Progressive Disclosure

The skill is a single ~230-line file with no references/ bundle; the structure is well-sectioned, but bulk per-tool parameter reference and the Quick Reference table are inlined in SKILL.md where a one-level-deep reference file would keep the overview lean — matching the anchor of inline content that could be separate. Not a 4 because there is no reference layering at all; not a 2 because sections, headers, and the table make it navigable rather than a wall of text.

3 / 5

Total

13

/

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.

A specific, well-scoped description that comprehensively enumerates Webflow capability areas and names its mechanism, making it highly distinctive. Its main gap is the absence of an explicit 'when to use' trigger clause, which caps completeness at 3.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to manage Webflow CMS items, publish their Webflow site, upload assets, or retrieve ecommerce orders."

Include natural user phrasings/synonyms such as "blog posts", "products", "collection items", and "publish my Webflow site" to strengthen trigger term coverage.

Move the instruction "Always search tools first for current schemas" into the skill body so the description focuses on what/when.

DimensionReasoningScore

Specificity

"Automate Webflow CMS collections, site publishing, page management, asset uploads, and ecommerce orders via Rube MCP (Composio)" lists five specific concrete capability areas that comprehensively cover the skill's domain, and even names the access mechanism. Not a 4 because no capability area from the body's workflows is missing; not below because every object named is domain-specific, not generic.

5 / 5

Completeness

The "what" is clear (automate Webflow CMS/publishing/pages/assets/orders via Rube MCP), but there is no "Use when..." clause or equivalent trigger guidance — the second sentence "Always search tools first for current schemas" is an operating instruction, not a trigger. Per the rubric guideline, a missing 'Use when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Natural terms users would say are present: "Webflow", "CMS", "site publishing", "asset uploads", "ecommerce orders". Not a 5 because common phrasings like "blog posts", "products", "publish my site", or "upload images/files to Webflow" are absent; clearly above 3 since the key nouns users invoke are all there.

4 / 5

Distinctiveness Conflict Risk

"Webflow" is a clear niche trigger and "via Rube MCP (Composio)" further disambiguates the access path; virtually any request phrased around Webflow would map to this skill with minimal overlap risk against 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

Path

skills/webflow-automation/SKILL.md

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.