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.
72
88%
Does it follow best practices?
Impact
—
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 Strapi CMS domain, lists concrete actions, and provides explicit 'Use when' triggers. It uses third person voice consistently and includes natural keywords that developers would use when seeking Strapi-related help. The description is concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: builds content types, extends controllers and services, implements lifecycle hooks, and configures REST/GraphQL APIs. | 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 specific 'Strapi' domain focus combined with Strapi-specific terminology like 'content types', 'lifecycle hooks', and 'Strapi plugins'. Unlikely to conflict with generic API or CMS skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable Strapi skill with executable code examples, clear file path conventions, and a well-structured workflow with validation steps. The content is mostly concise though a few lines could be tightened, and the progressive disclosure is reasonable but the referenced REFERENCE.md file is missing from the bundle. Overall it provides practical, immediately usable guidance for Strapi development.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but has some unnecessary framing (e.g., 'Generic Strapi CMS development methodology' preamble, rule #1 explaining what Content-Type Builder is). The critical rules section could be tighter, but the code examples are lean and purposeful. | 2 / 3 |
Actionability | Provides fully executable code examples for REST fetching, custom controller extension, and lifecycle hooks. File paths are specific, commands are concrete (yarn develop, yarn build), and the examples are copy-paste ready with realistic patterns. | 3 / 3 |
Workflow Clarity | The 'Quick workflow' section provides a clear 6-step sequence with explicit validation checkpoints (step 4 includes testing via admin UI and API, with a failure recovery path checking logs and running yarn build). This includes a feedback loop for error recovery. | 3 / 3 |
Progressive Disclosure | References both a project-specific config file (cms-config.md) and a REFERENCE.md for larger examples, which is good structure. However, REFERENCE.md is referenced but not provided in the bundle, making it impossible to verify. The inline content is reasonably sized but the API patterns section could potentially be split out for a cleaner overview. | 2 / 3 |
Total | 10 / 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
7a69a05
- 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.