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

84%

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

80%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.

An lean, dense reference-style body whose value comes from load-bearing gotchas rather than padding. Its main defect is fragmented workflow sequencing — the Verify section opens mid-sentence and the end-to-end flow for adding a content type is never laid out.

Suggestions

Fix the truncated opening of the Verify section ("the `develop` script, confirm..." is missing its leading verb, e.g. "Run the develop script") so the verification sequence reads unambiguously.

Add a short numbered end-to-end sequence for the most common task (create schema.json, grant permissions, restart, verify with GET) with the existing assertions as explicit checkpoints.

Include one minimal copy-paste controller example in the file-placement section to complement the createCoreController pattern.

Dimension	Reasoning	Score
Conciseness	Every line is a non-obvious gotcha or instruction ("Relations are not returned unless requested", "New endpoints return 403 until permissions are granted"); no concepts Claude already knows are explained and nothing is padded.	5 / 5
Actionability	Concrete file paths, code patterns (createCoreController wrapper), commands (strapi generate plugin), and checkable assertions dominate, but the controller guidance is pattern-level rather than copy-paste and the Verify section is missing its leading verb.	4 / 5
Workflow Clarity	The Verify section supplies validation checkpoints (create a test entry, assert 200 with a data array, assert populated relations), but the main build workflows have no explicit step sequence and the truncated opening "the `develop` script, confirm..." leaves the verification sequence implicit.	3 / 5
Progressive Disclosure	Under 50 lines with no bundle files needed: well-organized sections, one clearly signaled one-level-deep pointer (.opencastle/stack/cms-config.md) plus the official docs URL; nothing inlined that belongs in a separate file.	5 / 5
	Total	17 / 20 Passed

Description

88%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 description: third-person voice, concrete capability list, and an explicit multi-trigger 'Use when' clause. Its only weaknesses are a few missing natural synonyms and one slightly over-broad trigger phrase.

Suggestions

Add common synonyms to the trigger clause such as "headless CMS", "Strapi admin", or "content models" to improve keyword coverage.

Narrow the trailing trigger "querying the API" to "querying the Strapi REST or GraphQL API" to reduce overlap with generic API skills.

Dimension	Reasoning	Score
Specificity	"Builds Strapi content types, extends controllers and services, implements lifecycle hooks, and configures REST/GraphQL APIs" lists four concrete, domain-anchored actions that comprehensively cover what the skill body delivers.	5 / 5
Completeness	The explicit "Use when creating content types, writing custom controllers, developing Strapi plugins, or querying the API" clause answers both what and when with concrete trigger phrases.	5 / 5
Trigger Term Quality	"content types", "custom controllers", "Strapi plugins", "querying the API" are natural user phrases, but common variations such as "headless CMS", "Strapi admin", or "models" are absent.	4 / 5
Distinctiveness Conflict Risk	"Strapi" pins a clear niche with distinct triggers, but the generic trailing trigger "querying the API" creates minor overlap risk with general API/backend skills.	4 / 5
	Total	18 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: monkilabs/opencastle
Path: src/orchestrator/plugins/strapi/SKILL.md
Commit: c0f4566

Reviewed: 1 day 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.