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.
100
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%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 is a strong skill description that clearly identifies the platform (Contentful), lists specific concrete actions, and includes an explicit 'Use when...' clause with natural trigger terms. It follows third-person voice throughout and is concise without being vague. The description would effectively differentiate this skill from others in a large skill library.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: creates content types, queries entries via GraphQL/REST, runs CLI migrations, manages assets and locales. These are distinct, well-defined capabilities. | 3 / 3 |
Completeness | Clearly answers both what (creates content types, queries entries, runs migrations, manages assets/locales) and when ('Use when building or modifying Contentful content models, writing queries, or migrating content'). Explicit 'Use when...' clause is present. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Contentful', 'content types', 'GraphQL', 'REST', 'CLI migrations', 'assets', 'locales', 'content models', 'queries', 'migrating content'. Good coverage of terms a developer working with Contentful would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific platform name 'Contentful' and domain-specific terms like 'content types', 'CLI migrations', 'locales'. Very unlikely to conflict with other skills unless there were multiple Contentful-related skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that efficiently covers Contentful CMS operations with executable examples, a clear migration workflow with validation checkpoints and rollback procedures, and appropriate progressive disclosure. It respects Claude's intelligence by avoiding explanations of basic concepts while providing all the project-specific patterns needed for effective Contentful work.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It doesn't explain what Contentful is or how CMS systems work. Every section delivers actionable information without padding, and the inline comments are minimal and useful. | 3 / 3 |
Actionability | Provides fully executable code examples throughout: a typed GraphQL query, a migration script, a CLI command with actual flags, and a validation script. All are copy-paste ready with only placeholder values for project-specific IDs. | 3 / 3 |
Workflow Clarity | The migration workflow is clearly sequenced (1-5) with explicit validation at step 4, a feedback loop for failure (rollback or reverse migration), and a gate condition ('only when validation passes') before promoting to master. | 3 / 3 |
Progressive Disclosure | The skill provides a concise overview with clear one-level-deep references: project config points to cms-config.md, and longer migration patterns point to REFERENCE.md. Content is appropriately split between inline essentials and external details. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- monkilabs/opencastle
- Commit
f5c8508
- 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.