strapi-cms
Builds Strapi content types, extends controllers and services, implements lifecycle hooks, and configures REST/GraphQL APIs. Use when creating content types, writing custom controllers, developing Strapi plugins, or querying the API.
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 well-crafted skill description that clearly identifies the Strapi CMS domain with specific capabilities and explicit trigger conditions. It uses third person voice correctly, lists concrete actions, and includes a comprehensive 'Use when' clause with natural trigger terms. The description is concise yet thorough, making it easy for Claude to distinguish this skill from other API or CMS-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: builds content types, extends controllers and services, implements lifecycle hooks, and configures REST/GraphQL APIs. These are all distinct, concrete capabilities. | 3 / 3 |
Completeness | Clearly answers both what (builds content types, extends controllers/services, implements lifecycle hooks, configures APIs) and when ('Use when creating content types, writing custom controllers, developing Strapi plugins, or querying the API') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Strapi', 'content types', 'controllers', 'services', 'lifecycle hooks', 'REST', 'GraphQL', 'plugins', 'API'. These cover the main terms a developer working with Strapi would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the Strapi-specific focus. Terms like 'Strapi content types', 'Strapi plugins', and 'lifecycle hooks' in the Strapi context create a clear niche that is unlikely to conflict with generic API or CMS 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 Strapi development patterns with executable code examples, clear workflow steps with validation checkpoints, and appropriate progressive disclosure. It respects Claude's intelligence by jumping straight into Strapi-specific patterns without explaining general concepts. The content is comprehensive yet concise, covering content types, controllers, services, lifecycle hooks, and API querying in a scannable format.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It doesn't explain what Strapi is or how REST APIs work in general. Every section provides Strapi-specific knowledge that Claude wouldn't inherently know (query parameter syntax, factory patterns, lifecycle hook structure). | 3 / 3 |
Actionability | Provides fully executable code examples for REST queries, custom controller extensions, and lifecycle hooks. The examples are copy-paste ready with real Strapi factory patterns and proper file paths. | 3 / 3 |
Workflow Clarity | The 6-step workflow for creating a content type includes clear sequencing, explicit validation checkpoints (step 4 with admin UI verification and API check), error recovery guidance (check logs, run yarn build), and a final automated test step. | 3 / 3 |
Progressive Disclosure | Clean overview structure with two well-signaled one-level-deep references: project-specific config in cms-config.md and extended patterns in REFERENCE.md. The main content stays focused on essential patterns without becoming monolithic. | 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
18c6f2c
- 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.