CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

centaur-spec-reports

Teaches an agent how to create, publish, version, organize, share, and comment on Centaur Spec reports through the centaurspec MCP server; use when uploading/sharing an HTML report, publishing a new version of one under the same link, organizing reports into folders, controlling who can view/edit a report, or reading/resolving reviewer comments.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-crafted, highly actionable skill body: exact tool surface, worked examples, genuine error-handling guidance, and unusual depth on the HTML authoring constraints that would otherwise be learned by failure. The main improvement levers are trimming a few editorial asides, consolidating the scattered validation checkpoints into the workflow steps, and either bundling or removing the dangling docs/ references.

Suggestions

Trim meta-commentary ('This is the single most important relationship in the whole tool surface', the Claude Desktop instructions aside) to tighten conciseness.

Fold the scattered validation checkpoints (reports_get before changes, confirm-intent on deletes, skipped/failed after batch sharing) explicitly into the numbered Core workflow steps so the validate-then-proceed pattern is unmistakable.

Resolve the dangling references: either ship docs/mcp-usage.md and the ADRs inside the bundle (e.g., references/) or drop the 'More information' section, since the paths are unreachable from the skill as packaged.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious, earned tokens (4 MiB cap and HTTP 413 fallback, anchor-id survival rules, sharing vs. ACL vs. write-grant axes) and avoids teaching known concepts, matching 'efficient; minor instances of over-explanation'. It is not 5 because of mildly padded meta-commentary ("This is the single most important relationship in the whole tool surface", the aside about hosts like Claude Desktop not surfacing instructions) that could be trimmed.

4 / 5

Actionability

Guidance is fully executable: exact tool names with parameters (`update_slug`, `folder_path`, `parent_id`, `mode: "allowlist"`, `allowed_emails`), expected response shapes including an unchanged `view_url`, and two worked example flows covering the most common cases. Not 4, because the examples go beyond mostly-executable — they show call, response, and follow-up call, so nothing important is left to inference.

5 / 5

Workflow Clarity

The core workflow is a clear numbered 6-step sequence with real checkpoints: `reports_get` to "check a report's current state before changing it", "confirm intent first" on the destructive delete tools, the 413 → web-upload error-recovery path, and reading `skipped`/`failed` after batch folder sharing. It stops short of 5 because these checkpoints are distributed across sections rather than woven into the workflows as explicit validate-then-proceed steps (e.g., no verify step after upload or comment resolution).

4 / 5

Progressive Disclosure

The body is well-sectioned (security boundary, workflow, HTML authoring, tool table, examples) and the 'More information' section signals one-level-deep references clearly. It is not 5 because the referenced paths (`docs/mcp-usage.md`, `docs/adr/...`) are not part of the skill bundle — no references/ directory exists — so navigation dead-ends; and not 3, since structure and signaling are otherwise good and the content is appropriately placed inline.

4 / 5

Total

17

/

20

Passed

Description

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

A strong description: third-person voice, comprehensive and concrete about capabilities, with an explicit and well-phrased 'use when' trigger clause covering the main use cases. The only minor gap is a few missing natural synonyms in the trigger terms.

DimensionReasoningScore

Specificity

The description enumerates six concrete actions — "create, publish, version, organize, share, and comment on Centaur Spec reports" — naming both the artifact (HTML report) and the mechanism (centaurspec MCP server), which matches the 'multiple specific concrete actions; comprehensive coverage' anchor. It is not the level below (4) because coverage spans the full tool surface with no significant gaps.

5 / 5

Completeness

It explicitly answers 'what' (create, publish, version, organize, share, comment on reports via the MCP server) and 'when' with a concrete "use when..." clause listing five trigger scenarios, matching the top anchor exactly. Not 4, because the 'when' clause is already explicit and specific rather than merely adequate.

5 / 5

Trigger Term Quality

Triggers like "uploading/sharing an HTML report", "publishing a new version of one under the same link", "organizing reports into folders", and "reading/resolving reviewer comments" are natural user phrasings with good coverage. It falls short of 5 because a few plausible synonyms (e.g., 'update a report', 'report link', 'review feedback') are absent, keeping it at 'good keyword coverage; a few natural terms missing'.

4 / 5

Distinctiveness Conflict Risk

"Centaur Spec reports" plus the product-specific triggers (slug-based re-publishing, folder organization, comment resolution) carve out a clear niche with minimal overlap risk against generic reporting or file-sharing skills. It clearly fits the 'clear niche with distinct triggers' anchor rather than the 'minor overlap risk' level below.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

agranado2k/ai-report-platform

Path

apps/mcp/packaging/claude-code-plugin/skills/centaur-spec/SKILL.md

Reviewed

Table of Contents

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.