Name: strapi
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

strapi

Strapi integration. Manage data, records, and automate workflows. Use when the user wants to interact with Strapi data.

Quality

66%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/strapi/SKILL.md

Quality

Content

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

The body is action-dense with executable membrane commands and a well-validated connection workflow, but opens with unnecessary background on what Strapi is and carries minor structural loose ends. Tightening the intro and fixing the dangling Step 2 reference would lift it further.

Suggestions

Cut the opening 'Strapi is an open-source headless CMS...' paragraph and the 'Use action names and parameters as needed.' line; Claude already knows what Strapi is.

Resolve the dangling 'skip to Step 2' / '#### 1b.' numbering by either adding an explicit 'Step 2' header or re-labeling steps consistently so the sequence is unambiguous.

Trim or contextualize the bare 'Strapi Overview' bullet list of content types, which currently adds tokens without actionable guidance.

Dimension	Reasoning	Score
Conciseness	The opening paragraph explains what Strapi/headless CMS is ('Strapi is an open-source headless CMS that allows developers to build flexible APIs...'), a concept Claude already knows, and 'Use action names and parameters as needed.' is filler; the command sections are efficient, placing this mostly efficient but with unnecessary explanation.	3 / 5
Actionability	Provides concrete, copy-paste-ready commands throughout (npm install, membrane login, connection ensure, action list/run, request) covering the common cases; only minor gaps remain via placeholders like CONNECTION_ID and actionId, keeping it just below fully-complete level 5.	4 / 5
Workflow Clarity	Clear install→authenticate→connect→poll→search→run sequence with explicit state-validation checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-again feedback loop; a dangling 'skip to Step 2' reference with no matching Step 2 header is a minor validation/organization gap below level 5.	4 / 5
Progressive Disclosure	No bundle files exist, so all content is appropriately inline; sections are well-organized with clear headers (Install, Authentication, Connecting, Searching, Popular actions, Best practices). The inline Strapi Overview list and proxy-options table could be trimmed, but structure is good, fitting just below the ideal one-level-deep reference level.	4 / 5
	Total	15 / 20 Passed

Description

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

The description cleanly states what the skill does and when to use it with a distinct Strapi niche, but relies on fairly generic action verbs and limited trigger variations. It is solid and usable but could be sharpened with more concrete capabilities and richer trigger phrasing.

Suggestions

Replace generic verbs with concrete Strapi capabilities, e.g. 'Create and update content entries, manage content types, generate API and transfer tokens, and trigger webhooks.'

Broaden the trigger clause to cover natural phrasings users actually say, e.g. 'Use when the user wants to manage Strapi content types, entries, roles, or webhooks, or interact with the Strapi REST/GraphQL API.'

Dimension	Reasoning	Score
Specificity	Names the Strapi domain plus a few actions ('Manage data, records, and automate workflows'), but the verbs are generic rather than concrete; not comprehensive, matching the 1-2 concrete actions anchor rather than the several-specific-actions anchor above.	3 / 5
Completeness	Provides both a 'what' ('Strapi integration. Manage data, records, and automate workflows.') and an explicit 'when' ('Use when the user wants to interact with Strapi data.'), but the 'when' could be more specific about content types/entries, so it sits below the concrete-trigger-phrase level 5.	4 / 5
Trigger Term Quality	Includes relevant keywords ('Strapi', 'data', 'records', 'workflows') and a natural trigger phrase, but lacks common variations or synonyms beyond the core product name, fitting the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	'Strapi integration' with a Strapi-specific trigger is a clear niche with distinct triggers and minimal conflict risk against other skills.	5 / 5
	Total	15 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/strapi/SKILL.md
Commit: f484c82

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