CtrlK
BlogDocsLog inGet started
Tessl Logo

verify-openspec-docs

Fact-checks OpenSpec user documentation with a fresh-context subagent that re-runs commands and checks claims against source. Manually triggered; not part of the drafting loop. Use when the user asks to verify, fact-check, or accuracy-check a docs page, section, or set of changed claims.

72

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 tight, highly actionable instruction skill with a clear sequenced workflow and explicit verification feedback loops. The only minor weakness is one rationale sentence that slightly over-explains the fresh-context concept.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, but the opening sentence "The point of a fresh context is that the reviewer hasn't watched the prose get written, so it can't be talked into the author's assumptions" is rationale Claude can largely infer, a minor instance of over-explanation that could be trimmed.

4 / 5

Actionability

It provides a complete, copy-paste-ready reviewer prompt with every placeholder called out ("Fill every placeholder, make every path absolute"), plus concrete numbered scoping and report-handling steps, covering the common case fully.

5 / 5

Workflow Clarity

A clear Scope → Spawn → Handle sequence with explicit validation feedback loops ("If an applied fix changed a factual claim, verify again, scoped to the changed claims" and "Two passes without converging means stop") matches the top anchor for verification-style work.

5 / 5

Progressive Disclosure

Under 50 lines with no need for external references, yet well-organized into three labeled sections; per the simple-skill guidance this earns the top score on well-organized sections alone, and no nested/2+ level references exist.

5 / 5

Total

19

/

20

Passed

Description

87%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 that answers what and when concretely with natural trigger terms and a clear niche. It is just short of the top anchor on specificity and trigger-term breadth because the action list is summarized rather than enumerated and a few natural synonyms are absent.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ("re-runs commands", "checks claims against source", "fresh-context subagent that...checks claims"), but the actions stay at a mechanism-summary level rather than enumerating the full set of checks performed, so it falls just below the comprehensive anchor.

4 / 5

Completeness

It explicitly answers both "what" ("Fact-checks OpenSpec user documentation with a fresh-context subagent that re-runs commands and checks claims against source") and "when" ("Use when the user asks to verify, fact-check, or accuracy-check a docs page, section, or set of changed claims") with concrete trigger phrases.

5 / 5

Trigger Term Quality

"Use when the user asks to verify, fact-check, or accuracy-check a docs page, section, or set of changed claims" gives good natural-term coverage, but it omits common synonyms a user might say (e.g. "check this is right", "audit") and any file/section markers, so it is not fully comprehensive.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche (OpenSpec docs fact-checking via a fresh-context subagent) and the explicit boundary note "Manually triggered; not part of the drafting loop" distinguishes it from the sibling drafting skill, giving minimal conflict risk.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
Fission-AI/OpenSpec
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.