contentful-cms

Creates Contentful content types, queries entries via GraphQL/REST, runs CLI migrations, and manages assets and locales. Use when building or modifying Contentful content models, writing queries, or migrating content.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

86%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 tight, expert-aimed skill body with concrete commands, code snippets, and a validation-backed migration workflow. The main gaps are a fully worked migration-script example and an explicit gate before the production promotion step.

Suggestions

Add a minimal complete migration.js example (createContentType + createField + displayField) so the script structure is executable, not just described.

Insert an explicit validation gate before the production promotion step (e.g. "Only promote when all three validation steps pass") to lift workflow_clarity from 4 to 5.

Show one concrete query snippet (REST with `include`, or a GraphQL selection) since querying entries is named in the description but not demonstrated in the body.

Dimension	Reasoning	Score
Conciseness	The body is lean: it assumes Claude knows what Contentful is, never explains basic concepts, and every bullet earns its place (e.g. "Use `sys.publishedAt` as the cache-invalidation key"). No padded or over-explained sections, matching the 5-anchor.	5 / 5
Actionability	It gives a copy-paste migration command and concrete validation snippets (`blogPost.createField('author')...validations([{ linkContentType: ['person'] }])`, `.validations([{ unique: true }])`). It falls short of 5 because the migration-script shape is described rather than shown as a complete example, and validation steps are procedural rather than executable code.	4 / 5
Workflow Clarity	The sandbox→migrate→validate→promote sequence is explicit with a post-migration validation section (exit non-zero on a miss) and a rollback feedback loop (delete sandbox, re-clone, re-run corrected migration). The destructive-operation cap is avoided since validation is present, but the promotion/maintenance-window step lacks an explicit pass-gate, keeping it at 4 rather than 5.	4 / 5
Progressive Disclosure	At ~33 lines with no bundle files needed, it is organized into clear sections (Gotchas, Migration command, Post-migration validation) and signals one-level-deep references cleanly ("Project config, content types, and API keys: [cms-config.md]" plus the official docs URL). No inlined material belongs in a separate file, fitting the 5-anchor for a compact skill.	5 / 5
	Total	18 / 20 Passed

Description

92%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 strong, well-scoped description that concretely lists capabilities and provides explicit, natural trigger phrases for a distinct named-CMS niche. Its only mild gap is keyword synonym breadth, which keeps trigger_term_quality at 4 rather than 5.

Dimension	Reasoning	Score
Specificity	"Creates Contentful content types, queries entries via GraphQL/REST, runs CLI migrations, and manages assets and locales" lists multiple specific concrete actions spanning Contentful's main surface with comprehensive coverage. It exceeds the 4-anchor (which allows minor gaps) by covering types, querying, migrations, assets, and locales.	5 / 5
Completeness	It explicitly states what ("Creates content types, queries entries..., runs CLI migrations, manages assets and locales") and when ("Use when building or modifying Contentful content models, writing queries, or migrating content") with concrete trigger phrases, matching the 5-anchor example exactly.	5 / 5
Trigger Term Quality	Natural terms like "Contentful content models", "writing queries", and "migrating content" match what users would say, plus technical hooks (GraphQL/REST, CLI migrations). Good coverage, but a few natural synonyms (e.g. "content entries", "spaces", "environments") are absent, so it sits below the comprehensive 5-anchor.	4 / 5
Distinctiveness Conflict Risk	"Contentful" names a specific CMS and every trigger is Contentful-scoped, giving a clear niche with minimal overlap risk against generic skills. This matches the 5-anchor (clear niche, distinct triggers).	5 / 5
	Total	19 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 suspicious	Warning

	Total	15 / 16 Passed

Repository: monkilabs/opencastle
Path: src/orchestrator/plugins/contentful/SKILL.md
Commit: fa0c341

Reviewed: 5 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.