agility-cms-automation

Automate Agility CMS tasks via Rube MCP (Composio). Always search tools first for current schemas.

Install with Tessl CLI

npx tessl i github:haniakrim21/everything-claude-code --skill agility-cms-automation

What are skills?

14.28x

Review — 46%

Does it follow best practices?

If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:

npx tessl skill review --optimize ./path/to/skill

Learn more

Evaluation — 100%

↑ 14.28x

Agent success when using this skill

Validation — 10 / 11 Passed

Validation for skill structure

SKILL.md

Review

Evals

Discovery

22%

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

This description is too vague to effectively guide skill selection. It names the platform (Agility CMS) and integration method (Rube MCP/Composio) but fails to specify concrete capabilities or provide trigger guidance. Users searching for content management help wouldn't know this skill handles their specific needs.

Suggestions

Add specific capabilities like 'create and publish content, manage assets, configure content models, handle webhooks'

Add a 'Use when...' clause with natural trigger terms like 'Agility CMS', 'headless CMS content', 'publish to Agility', 'content management'

Include common user phrases and task types that would indicate this skill is needed, such as 'manage website content', 'update CMS entries', 'content workflow'

Dimension	Reasoning	Score
Specificity	The description says 'Automate Agility CMS tasks' which is vague - it doesn't specify what tasks can be automated (content creation, publishing, asset management, etc.). 'Always search tools first' is procedural guidance, not a capability description.	1 / 3
Completeness	The 'what' is extremely vague ('automate tasks') and there is no 'Use when...' clause or equivalent trigger guidance. The description fails to answer when Claude should select this skill over others.	1 / 3
Trigger Term Quality	Contains 'Agility CMS', 'Rube MCP', and 'Composio' which are relevant technical terms, but lacks natural user language variations like 'content management', 'headless CMS', 'publish content', or common task-related keywords users would actually say.	2 / 3
Distinctiveness Conflict Risk	'Agility CMS' provides some distinctiveness from other CMS tools, but 'automate tasks' is generic enough that it could conflict with other automation or CMS-related skills. The Rube MCP/Composio reference adds some specificity.	2 / 3
	Total	6 / 12 Passed

Implementation

70%

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

This skill provides a solid structure for Agility CMS automation with clear workflow sequencing and good progressive disclosure. However, it suffers from some redundancy between sections and uses placeholder-style examples rather than fully concrete, executable patterns. The emphasis on 'always search first' is appropriate given the dynamic nature of the tooling.

Suggestions

Replace placeholder comments like '/* schema-compliant args from search results */' with a concrete example showing actual field names and values for a common Agility CMS operation

Consolidate the Setup and Core Workflow Pattern sections to eliminate redundancy - the connection check appears in both places

Add a concrete example showing a complete workflow from search to execution with actual response data to demonstrate the full pattern

Dimension	Reasoning	Score
Conciseness	The content is reasonably efficient but includes some redundancy - the 'Core Workflow Pattern' section largely repeats information from Prerequisites and Setup. The quick reference table adds value, but some explanations could be tighter.	2 / 3
Actionability	Provides concrete tool call patterns with parameter structures, but uses pseudocode-style examples rather than fully executable code. The placeholder comments like '/* schema-compliant args from search results */' reduce copy-paste readiness.	2 / 3
Workflow Clarity	Clear 3-step workflow with explicit sequencing (discover → check connection → execute). Includes validation checkpoint ('Confirm connection status shows ACTIVE before running any workflows') and the Known Pitfalls section addresses error prevention.	3 / 3
Progressive Disclosure	Well-structured with clear sections progressing from prerequisites to setup to workflow to pitfalls. External reference to Composio docs is one level deep and clearly signaled. Quick reference table provides efficient navigation for common operations.	3 / 3
	Total	10 / 12 Passed

Validation

90%

Warnings & errors only

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

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.