CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

antithesis-documentation

Use Antithesis documentation efficiently for product, workflow, and integration questions. Prefer the snouty docs CLI when available, and otherwise request markdown versions of documentation pages directly.

Quality

81%

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

88%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 lean, highly actionable reference-lookup skill with a well-sequenced primary workflow, a concrete fallback path, and an explicit self-review checklist. Its only slack is the product overview prose and the absence of any external reference structure, neither of which materially hurts usability.

DimensionReasoningScore

Conciseness

The body is efficient — exact commands and precise URL transformation rules with worked examples — but the three-paragraph 'Antithesis Overview' explaining what the product is could be trimmed since it is not needed to execute the doc-lookup workflow, matching 'efficient; minor instances of over-explanation'.

4 / 5

Actionability

Fully executable, copy-paste-ready guidance covers the common cases: exact snouty commands ('snouty docs tree --depth 2', 'snouty docs search -l <terms>', 'snouty docs show <path>'), install/recovery steps, and direct fallback rules with concrete URL examples and explicit exceptions.

5 / 5

Workflow Clarity

Clear multi-path sequences with explicit validation checkpoints: a 6-step docs workflow, a missing-CLI recovery flow with version check ('If snouty --version is older than 0.8.0, run snouty update first') and re-run, error-recovery guidance for the cached-docs warning, and a Self-Review checklist validating grounding and citations before completion.

5 / 5

Progressive Disclosure

No bundle files exist and all content is inline under clear, well-organized section headers, which is appropriate placement; however, at ~93 lines it exceeds the under-50-line threshold where inline-only organization merits a 5, and the Overview section is arguably separable, leaving minor organization room.

4 / 5

Total

18

/

20

Passed

Description

65%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 specific, distinctive description with good trigger keywords for a niche product, weakened by the absence of any explicit 'Use when...' trigger clause and a vague lead action ('Use ... efficiently'). Adding explicit trigger guidance and concrete capability verbs would lift it to the top band.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks about Antithesis, its SDKs, testing workflows, setup, or best practices.'

Replace the generic 'Use Antithesis documentation efficiently' with concrete capability actions such as 'Find, read, and cite authoritative Antithesis documentation'.

Include natural trigger synonyms users would actually say, such as 'Antithesis docs', 'SDK', 'testing', and 'setup', to round out keyword coverage.

DimensionReasoningScore

Specificity

The description names the domain (Antithesis documentation) and two concrete actions ('Prefer the snouty docs CLI when available', 'request markdown versions of documentation pages directly'), but the lead action 'Use Antithesis documentation efficiently' is generic and coverage is not comprehensive, matching the 1-2 concrete actions anchor rather than the several specific actions of level 4.

3 / 5

Completeness

It clearly answers 'what' (use Antithesis docs via the snouty CLI, or fetch markdown pages directly) but has no 'Use when...' clause or equivalent explicit trigger guidance — 'for product, workflow, and integration questions' only weakly implies when, matching anchor 3 and triggering the completeness cap.

3 / 5

Trigger Term Quality

Good keyword coverage with 'Antithesis', 'documentation', 'snouty docs CLI', 'product, workflow, and integration questions', and 'markdown' — natural terms a user would say when needing this skill — though common variations like 'SDK', 'testing', 'setup', and 'docs' are absent, keeping it below the comprehensive level 5.

4 / 5

Distinctiveness Conflict Risk

It names the specific product 'Antithesis' and its dedicated CLI 'snouty', creating a clear niche with distinct triggers and minimal conflict risk with any other skill domain.

5 / 5

Total

15

/

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

antithesishq/antithesis-skills

Path

antithesis-documentation/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.