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 ecosystem as its domain, lists specific concrete capabilities, and provides explicit 'Use when' trigger guidance. The description is concise yet comprehensive, covering both the what and when dimensions effectively while using natural developer terminology that would facilitate accurate skill selection.
| 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 REST/GraphQL 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
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 focusing on Strapi-specific patterns (factory functions, query operators, file structure conventions) rather than explaining general concepts. The content is concise yet comprehensive for its scope.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It avoids explaining 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). No unnecessary padding. | 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 correct API syntax. File paths are specific and concrete. | 3 / 3 |
Workflow Clarity | The 6-step workflow for creating a content type includes clear sequencing, an explicit validation checkpoint (step 4 with test entry creation and API verification), and a feedback loop for failure (check logs, run build, verify schema). Step 6 adds automated testing as a final verification. | 3 / 3 |
Progressive Disclosure | The skill provides a concise overview with clear references to project-specific config (cms-config.md) and detailed patterns (REFERENCE.md). References are one level deep and well-signaled. Content is appropriately split between quick-start patterns inline and deeper reference material externally. | 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.