Name: graphcms
Rating: 61.6 (1 reviews)
Author: membranedev

graphcms

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

Quality

72%

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

Quality

Content

75%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 concrete, copy-paste CLI examples and a clear connection-state workflow with feedback loops. It is held back only by mild verbosity (an introductory GraphCMS explainer) and minor structural duplication.

Suggestions

Cut or move the opening "GraphCMS is a headless content management system..." explainer; Claude already knows what GraphCMS is.

Consolidate the duplicated `action list` invocation so "Popular actions" references rather than re-states the discovery command.

Add a brief validation note for action runs (e.g. check the response `output`/`error` fields before reporting success) to strengthen the workflow's verification checkpoint.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with copy-paste CLI commands, but it opens by explaining what GraphCMS is ("a headless content management system that provides a GraphQL API") and repeats the action-list command, which could be trimmed.	3 / 5
Actionability	Fully executable guidance throughout: concrete membrane CLI commands with flags and --json examples cover login, connection ensure/get, action list/run, and proxy requests, with a clear options table.	5 / 5
Workflow Clarity	A clear install → login → connect → search → run → proxy sequence with explicit state handling (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-again feedback loop, though success verification for action runs relies only on reading the output field.	4 / 5
Progressive Disclosure	A single well-organized file with clear section headers and no nested references; the inlined proxy-flag table is appropriate, but the "Popular actions" section duplicates the action-list command already shown in "Searching for actions".	4 / 5
	Total	16 / 20 Passed

Description

70%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 answers both what and when with a product-anchored trigger, but its action verbs are generic rather than GraphCMS-specific. Tightening the capabilities list with concrete operations would push specificity and completeness higher.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete GraphCMS operations such as querying content, creating/updating records, managing assets, and editing schema.

Add natural trigger synonyms users might say, e.g. "headless CMS", "content", "schema", or "assets", to broaden keyword coverage.

Mirror the skill body's domain entities (Content, Asset, Schema, Webhook) in the description so the "what" matches what the skill actually offers.

Dimension	Reasoning	Score
Specificity	Names the GraphCMS domain plus actions ("Manage data, records, and automate workflows"), but the verbs are generic rather than concrete product-specific operations, leaving coverage incomplete.	3 / 5
Completeness	It states both what the skill does (GraphCMS integration, manage data/records/workflows) and when to use it with a concrete trigger phrase, but the "what" actions are slightly generic, stopping short of the fully comprehensive anchor-5 example.	4 / 5
Trigger Term Quality	The explicit trigger "Use when the user wants to interact with GraphCMS data" plus the "GraphCMS" keyword give good coverage, though a few natural synonyms (content, headless CMS, schema) are missing.	4 / 5
Distinctiveness Conflict Risk	Naming the specific product "GraphCMS" gives it a clear niche with minimal conflict risk, though the generic "manage data, records, automate workflows" phrasing leaves minor overlap with other data-integration skills.	4 / 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/graphcms/SKILL.md
Commit: f484c82

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.