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

Blog Docs Log in Get started

prismic

Prismic integration. Manage Repositories. Use when the user wants to interact with Prismic 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/prismic/SKILL.md

Quality

Content

71%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 real executable commands and a clear connection-state workflow including polling feedback, but it opens with unnecessary concept explanation and keeps all reference material inline with no progressive-disclosure pointers.

Suggestions

Trim the introductory paragraph defining what Prismic/CMS is — Claude already knows this — to improve token efficiency.

Move the proxy flag table and the Prismic Overview concept list into a references file and link to it, so SKILL.md stays a lean overview.

Fix the dangling "skip to Step 2" reference by labeling the actual steps (e.g., Step 1 connect, Step 2 search/run actions) so the workflow sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste commands, but the opening paragraph explaining what Prismic/CMS is and phrases like "This is the fastest way to get a connection" are unnecessary explanation Claude does not need, fitting the "mostly efficient but some unnecessary explanation" anchor.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands across the common cases (install, login, connection ensure, polling, action list/run, request proxy) with real flags and a flag reference table, matching the "fully executable" anchor.	5 / 5
Workflow Clarity	The install → auth → connect → poll → search → run sequence is clear with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a re-poll feedback loop, but the dangling "skip to Step 2" reference (no labeled Step 2) is a minor validation/sequencing gap that keeps it below 5.	4 / 5
Progressive Disclosure	There are no bundle files and no external references at all; the ~155-line file inlines reference-style material (the Prismic Overview concept list, the proxy flag table, action schema fields) that could be split out, so structure exists but progressive disclosure is not used.	3 / 5
	Total	15 / 20 Passed

Description

61%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 on-niche and includes an explicit Use-when trigger, but it is thin on concrete capabilities — only the generic "Manage Repositories" — and lacks keyword variations, leaving it solid but not exemplary.

Suggestions

Replace the generic "Manage Repositories" with 2-3 concrete actions (e.g., query documents, manage Custom Types and Slices, handle Releases) to lift specificity.

Add natural keyword variations and file/concept terms users say (e.g., "Prismic documents", "Slices", "Custom Types", "Releases") to broaden trigger coverage.

Tighten the "what" so it reads as a concrete capability list rather than a single vague verb.

Dimension	Reasoning	Score
Specificity	It names the domain ("Prismic integration") but the only action is the generic "Manage Repositories", which is minimal rather than a list of concrete capabilities; not as bare as a 1 but lacks the 1-2 concrete actions of a 3.	2 / 5
Completeness	Both a "what" ("Prismic integration. Manage Repositories.") and an explicit "when" ("Use when the user wants to interact with Prismic data.") are present; the Use-when clause is explicit so it is not capped at 3, though the "what" is somewhat thin versus a 5.	4 / 5
Trigger Term Quality	"Prismic", "Repositories", and "Prismic data" are relevant keywords a user might say, but coverage is thin with no synonyms or variations, matching the "some relevant keywords but missing common variations" anchor.	3 / 5
Distinctiveness Conflict Risk	Prismic is a specific named CMS and the trigger ("interact with Prismic data") is narrowly scoped, giving it a clear niche with minimal overlap risk against other skills.	5 / 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/prismic/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.