Name: contentful
Rating: 51.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

contentful

Contentful integration. Manage Spaces. Use when the user wants to interact with Contentful data.

Quality

56%

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/contentful/SKILL.md

Quality

Content

65%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 highly actionable with copy-paste-ready CLI commands and a useful actions table, and the connection workflow handles multiple states well. It is held back by padding Claude does not need, an absence of validation/verify checkpoints around destructive entry/asset operations, and a monolithic structure with no reference files for the large API surface.

Suggestions

Trim the overview padding ('Contentful is a headless content management system...') and the bare 'Contentful Space / Content Type / Entry / Asset' bullets, which explain concepts Claude already knows.

Add explicit validation/checkpoint steps for destructive and batch operations, e.g. verify an entry is unpublished before delete-entry, and confirm the target ID before batch actions.

Move the full actions table and proxy-flag reference into a separate reference file (e.g. references/actions.md) and link to it from the body, keeping SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	Most of the body is efficient CLI reference material, but it includes explanatory padding Claude does not need ('Contentful is a headless content management system. It allows developers and content creators to manage and deliver content across various digital channels.') and a slightly over-explained 'Overview' bullet list, fitting 'Mostly efficient but includes some unnecessary explanation or could be tightened' rather than the lean 4 anchor.	3 / 5
Actionability	The body gives copy-paste-ready commands for every stage (install, login, headless auth, connection ensure/get with --wait, action list/run with JSON input, request proxy with full flag table) plus a concrete actions table; this matches 'Fully executable; copy-paste ready code or commands; specific examples cover the common cases' exactly.	5 / 5
Workflow Clarity	The connect-to-Contentful flow is sequenced with state handling (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and polling guidance, but it involves destructive/batch-capable operations (delete entry/asset, unpublish) with no validation or verify checkpoint before acting, and the destructive-cap the rubric imposes caps this at 3; not 4 because of those missing checkpoints.	3 / 5
Progressive Disclosure	The body is a single ~160-line monolith with reasonable section headers but no external reference files (references/, scripts/, assets/ are absent), and a large actions table plus full proxy-flag reference that would be cleaner in separate files is inlined; this matches 'Some structure but could be better organized; references present but not clearly signaled; content that should be separate is inline' better than the 4 anchor.	3 / 5
	Total	14 / 20 Passed

Description

48%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 is third-person, names the domain, and includes an explicit 'Use when...' trigger, but it severely understates the skill's actual capability surface (only 'Manage Spaces' is mentioned). It is barely acceptable as a trigger but not compelling because a user asking about entries, assets, or publishing would not recognize this skill from the description alone.

Suggestions

Expand the 'what' to cover the real capability surface, e.g. 'Manage Contentful Spaces, content types, entries, and assets; create, update, publish, and delete entries.'

Add the natural trigger terms users actually say to the 'Use when' clause, e.g. 'Use when the user wants to manage Contentful content — entries, content types, assets, spaces, or publishing.'

Include the file/term synonyms (entries, content types, assets, publish) so the description matches how users phrase these requests.

Dimension	Reasoning	Score
Specificity	The phrase 'Manage Spaces' is a single concrete action in a narrow domain, but it is minimal and ignores the rich action surface (entries, assets, content types, publishing) covered in the body; this matches 'Names the domain but actions are minimal or generic' rather than the more comprehensive anchor at 3.	2 / 5
Completeness	It has a clear 'what' ('Contentful integration. Manage Spaces.') and an explicit 'when' ('Use when the user wants to interact with Contentful data'), but the 'what' is thin and the 'when' is generic; the explicit trigger pushes it above the 3-no-when anchor yet it is not concrete enough for 4, so it sits at the 3 boundary.	3 / 5
Trigger Term Quality	It surfaces 'Contentful' and 'Spaces' as keywords and an explicit 'Use when...' trigger, but omits common natural synonyms users would actually say ('content types', 'entries', 'assets', 'publish') that the body reveals; this fits 'Some relevant keywords but missing common variations or synonyms' better than the 4 anchor.	3 / 5
Distinctiveness Conflict Risk	'Contentful integration' plus a Contentful-specific trigger ('interact with Contentful data') carves a clear niche with minimal overlap risk against non-CMS skills; it is mostly distinct with only minor overlap risk against other CMS/headless-CMS skills, matching the 4 anchor rather than 3 or 5.	4 / 5
	Total	12 / 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/contentful/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.