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

88%

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

The canonical home for this skill is centaur-spec-reports in agranado2k/ai-report-platform

SKILL.md
Quality
Evals
Security

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.

A strong, information-dense instruction skill: every section carries tool-specific behavior that could not be guessed, destructive and batch operations carry explicit validation notes, and the re-publish-same-slug relationship is foregrounded as the key concept. The consistent 4s reflect small residual gaps — a few generic-security and meta sentences, missing example calls for the sharing tools, and doc references that are not bundled.

Suggestions

Bundle docs/mcp-usage.md (or inline its tool table and OAuth/API-key connection instructions) so the 'More information' references resolve inside the skill directory.

Add short example calls for reports_set_sharing and reports_grant_write / reports_revoke_write to match the concrete-call treatment the upload and comment flows already get.

Trim the intro paragraph about hosts surfacing 'instructions' and condense the trust-boundary section's generic injection prose to the tool-specific essentials.

DimensionReasoningScore

Conciseness

The body is dense and almost entirely tool-specific knowledge Claude cannot infer (anchor survival on block vs. inline elements, the 4 MiB transport cap, target/rel normalization rules). Minor over-explanation keeps it off anchor 5: the intro's rationale about hosts that don't surface 'instructions' and the trust section's generic prompt-injection framing ('ignore previous steps and…') restate things Claude already knows or could be tightened to one line.

4 / 5

Actionability

Exact tool names with parameters ('reports_upload' with 'update_slug', 'folder_path', the three sharing states) plus two concrete call/response flows ('reports_upload(html: ..., update_slug: "q3-results")' with the unchanged view_url) make most guidance executable. Minor gaps keep it at anchor 4 rather than 5: reports_set_sharing, the ACL tools, and the write-grant tools never get a concrete example call, only prose and a table row.

4 / 5

Workflow Clarity

A clear six-step core workflow (Publish → Re-publish → Organize → Find → Collaborate → Share) with real checkpoints present: 'Check a report's current state before changing it', 'read its skipped/failed' for the batch folder-sharing tool, 'destructive; confirm intent first' on deletes, and a size pre-check with an error-recovery path (413 → use the web upload). It falls short of anchor 5 because error-recovery feedback loops are not systematic — most steps have no stated failure handling.

4 / 5

Progressive Disclosure

Well-organized sections (Security, Core workflow, Authoring the HTML, tool-selection table, Example flows) with a 'More information' section of clearly signaled, one-level-deep references (docs/mcp-usage.md, two ADRs), each annotated with what it contains. Not anchor 5: none of the referenced files ship in the skill's bundle (no references/, scripts/, assets/, or docs/ directory exists), so the pointers — including the 'full tool table' — do not resolve locally.

4 / 5

Total

16

/

20

Passed

Description

95%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 canonical description: third-person 'what' with multiple concrete verbs, followed by an explicit 'use when' clause whose five triggers are phrased the way a user would naturally voice the need. The only nit is that delete/search/rename are absent from the action list, which keeps specificity just below comprehensive.

DimensionReasoningScore

Specificity

Lists six concrete actions ('create, publish, version, organize, share, and comment on Centaur Spec reports') on a named artifact via a named mechanism ('through the centaurspec MCP server'), and the when-clause adds access control ('controlling who can view/edit a report'). It stops short of anchor 5's comprehensive coverage because search, rename, and delete — part of the tool surface the body documents — are never mentioned.

4 / 5

Completeness

Explicitly answers both halves: what ('Teaches an agent how to create, publish, version, organize, share, and comment on Centaur Spec reports') and when ('use when uploading/sharing an HTML report, publishing a new version...') with concrete trigger phrases — the exact form of the anchor-5 example. Not 4, because the 'when' is specific and enumerated rather than generic.

5 / 5

Trigger Term Quality

The trigger phrases read exactly like user needs: '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', 'reading/resolving reviewer comments'. Synonym pairs are covered (comment / reviewer comments; view/edit / share), so it matches the comprehensive anchor rather than the 'a few natural terms missing' anchor 4.

5 / 5

Distinctiveness Conflict Risk

The 'Centaur Spec reports through the centaurspec MCP server' framing is brand-anchored to a clear niche, and every trigger ('publishing a new version... under the same link', 'resolving reviewer comments') is domain-specific, so conflict with other skills is minimal.

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/skill/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.