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

89%

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

86%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, well-organized skill body that earns its tokens with load-bearing paths, query gotchas, and concrete verify assertions. The main weaknesses are placeholder-only code in a couple of sections and a Verify sentence missing its leading verb, plus the absence of an explicit fix-and-retry feedback loop.

Suggestions

Fix the Verify sentence start — add a leading verb (e.g., 'Run the `develop` script, confirm the type appears in admin...') so the step is unambiguous.

Add a short validate→fix→retry loop in Verify (e.g., 'If `build` reports schema errors, fix and re-run before creating entries') to reach a full feedback loop for schema changes.

Provide a minimal executable lifecycles or services snippet instead of describing them as 'all business logic', or point to a one-level-deep reference file for the full pattern.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it states the load-bearing fact 'Strapi discovers code by path' and gives terse paths, query strings, and verify assertions with no padding or explanation of basics, matching the score-5 anchor.	5 / 5
Actionability	Concrete code (the createCoreController wrapper) and real query strings are provided, but paths use `<type>` placeholders requiring substitution, services/lifecycles are described rather than shown, and the Verify sentence is malformed at its start, so it sits at 4 with minor gaps rather than fully copy-paste-ready 5.	4 / 5
Workflow Clarity	The Verify section sequences run develop → confirm in admin → create entry → assert GET 200 with data array → assert populate returns relations, with explicit validation assertions and a build-script error-surfacing note, but no explicit validate→fix→retry feedback loop, so it fits anchor 4 rather than 5.	4 / 5
Progressive Disclosure	A short, well-sectioned overview (File placement, Query gotchas, Verify) that offloads project config and deployment detail to a clearly signaled one-level-deep reference [cms-config.md](../../.opencastle/stack/cms-config.md), keeping API patterns inline — matching the score-5 anchor for a sub-50-line skill.	5 / 5
	Total	18 / 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 that pairs concrete capabilities with an explicit 'Use when' trigger clause and a clearly bounded Strapi niche. The only gap is a few missing natural synonyms in the trigger list.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Builds Strapi content types, extends controllers and services, implements lifecycle hooks, and configures REST/GraphQL APIs' — covering the Strapi backend surface comprehensively, matching the score-5 anchor.	5 / 5
Completeness	Explicitly answers both what (the four backend actions) and when ('Use when creating content types, writing custom controllers, developing Strapi plugins, or querying the API') with concrete trigger phrases, matching the score-5 anchor.	5 / 5
Trigger Term Quality	The 'Use when' clause surfaces natural phrases ('creating content types, writing custom controllers, developing Strapi plugins, querying the API') with good coverage, but omits common synonyms (REST/GraphQL endpoints, lifecycle hooks) that appear only in the what-clause, so it sits at 4 rather than 5.	4 / 5
Distinctiveness Conflict Risk	The Strapi-CMS niche is sharply scoped with distinct triggers (content types, controllers, plugins, REST/GraphQL), so conflict with other skills is minimal, matching the score-5 anchor.	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: f297837

Reviewed: 8 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.