Name: payload-cms
Rating: 56.8 (1 reviews)
Author: membranedev

payload-cms

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

Quality

65%

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/payload-cms/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 a practical, executable guide centered on the Membrane CLI with clear commands and a strong connection state-machine workflow. Its weaknesses are some unnecessary explanatory padding at the top, unlabeled step references ('Step 2', '1b'), and a single-file structure with no offloading of reference material.

Suggestions

Remove the opening paragraph defining Payload CMS and trim marketing phrasing ('so you can focus on the integration logic rather than auth plumbing'); Claude already knows what a headless CMS is.

Fix the step numbering: label the main steps (1, 2, 3...) so the 'Skip to Step 2' and '1b' references resolve, or restructure into one explicit numbered workflow.

Add one fully-worked end-to-end example with substituted values (e.g. listing and running a 'find posts' action) so the commands are unambiguously executable.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands and a lean flags table, but the opening paragraph explains what Payload CMS is (knowledge Claude already has) and lines like 'so you can focus on the integration logic rather than auth plumbing' add padding; not a 4 because these explanatory/marketing passages could be trimmed.	3 / 5
Actionability	Provides copy-paste-ready commands for install, login, connection, action search/run, and proxying, plus a flags table; not a 5 because placeholders like CONNECTION_ID, actionId, and 'QUERY' must be substituted and a fully worked end-to-end example is missing.	4 / 5
Workflow Clarity	The connection setup is a clear state-machine sequence (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) with an explicit polling feedback loop; not a 5 because the global flow is not numbered, 'Step 2' is referenced but never labeled, and '1b' appears without a '1a'.	4 / 5
Progressive Disclosure	A single-file skill (no references/scripts/assets bundle) with well-organized section headers and no nested references; not a 5 because the proxy flags table and 'Popular actions' material could arguably live in separate reference files, leaving minor organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

62%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 a solid, third-person statement that covers both capability and an explicit 'Use when' trigger tied to a specific product. Its main weakness is generic action verbs ('manage data, records, automate workflows') rather than concrete operations, which limits specificity and trigger-term richness.

Suggestions

Replace generic verbs with concrete Payload CMS operations, e.g. 'Create, read, update, and delete collections, manage media uploads, and query globals'.

Expand trigger terms with synonyms users actually say, such as 'Payload collections', 'Payload globals', 'Payload media', or 'Payload REST/local API'.

Tighten the 'when' clause to name concrete triggers, e.g. 'Use when the user wants to query or modify Payload CMS collections, globals, or media.'

Dimension	Reasoning	Score
Specificity	Names the domain (Payload CMS) and lists actions ('Manage data, records, and automate workflows'), but the verbs are generic rather than concrete operations, matching the '1-2 concrete actions but not comprehensive' anchor; not a 4 because the actions lack the specificity of 'extracts text, fills forms, converts pages'.	3 / 5
Completeness	Answers both what ('Payload CMS integration. Manage data, records, and automate workflows.') and when ('Use when the user wants to interact with Payload CMS data.') explicitly; not a 5 because the 'what' is somewhat generic rather than listing concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes the natural product term 'Payload CMS' and 'Payload CMS data' that users would say, but offers no synonyms or variations beyond the product name, fitting 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	'Payload CMS integration' is a clear, specific niche with distinct product-named triggers and minimal conflict risk; not a 5 because the generic 'manage data, records' phrasing leaves slight overlap with other data-management skills.	4 / 5
	Total	14 / 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/payload-cms/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.