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.

Quality

93%

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

93%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, highly actionable Strapi reference with concrete paths, code patterns, query examples, and a verification checklist. The only minor gap is the absence of an explicit validate-fix-retry loop in the Verify section.

Suggestions

Add an explicit retry loop to the Verify section (e.g., 'If assertions fail or schema errors surface under yarn build, fix and re-run before proceeding') to reach full workflow-clarity maturity.

Optionally surface the most common lifecycle-hook pitfalls (e.g., async errors swallowed in afterUpdate) as a one-line gotcha alongside the query gotchas.

Dimension	Reasoning	Score
Conciseness	Lean and efficient throughout — it assumes Claude's competence ('Strapi discovers code by path — a correct file in the wrong place is simply ignored') with no padding explaining what Strapi or its concepts are.	5 / 5
Actionability	Provides concrete file paths, executable code patterns (createCoreController('api::<type>.<type>', ({ strapi }) => ({ ... }))), specific query strings (?filters[status][$eq]=published), and commands (yarn develop, strapi generate plugin <name>).	5 / 5
Workflow Clarity	The Verify section gives a clear sequence with explicit validation checkpoints (assert GET returns 200 with a data array, assert populate returns expected relations), but lacks an explicit fix-and-retry feedback loop, falling just short of a 5.	4 / 5
Progressive Disclosure	Under 50 lines with well-organized section headers (File placement, Query gotchas, Verify) and a single clearly-signaled one-level reference to cms-config.md, satisfying the simple-skill exception.	5 / 5
	Total	19 / 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, third-person description with concrete capabilities and an explicit 'Use when' trigger clause. It clearly answers both what and when with low conflict risk.

Dimension	Reasoning	Score
Specificity	Lists four concrete actions ('Builds Strapi content types, extends controllers and services, implements lifecycle hooks, and configures REST/GraphQL APIs'), giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly states both what it does (four concrete actions) and when to use it ('Use when creating content types, writing custom controllers, developing Strapi plugins, or querying the API').	5 / 5
Trigger Term Quality	'creating content types, writing custom controllers, developing Strapi plugins, or querying the API' are natural user phrases with good coverage, but a few common variations (e.g. REST/GraphQL endpoints, lifecycles) are absent from the triggers.	4 / 5
Distinctiveness Conflict Risk	Strapi-specific niche with distinct, domain-scoped triggers; minimal overlap risk with other skills.	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/strapi/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.