Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →wshobson/hads
Use when writing technical documentation that needs to be readable by both humans and AI models, converting existing docs to HADS format, validating a HADS document, or optimizing documentation for token-efficient AI consumption.
Passed 20 of 20 test cases with the skill, and 8 of 20 without it.
and 21 more in the full report
13 fixed9 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
In technical documentation standards, what acronym expansion does HADS represent, and what is its standard file extension?
| Checked | Without skill | With skill |
|---|---|---|
| The output specifies Human-AI Document Standard as the full name. | Missed | Passed |
| The output specifies .md as the file extension. | Missed | Passed |
The instructions your model reads when the skill loads.
Version 1.0.0 · Human-AI Document Standard · 2026 · HADS 1.0.0
This skill teaches Claude how to read, generate, and validate HADS documents.
Read all [SPEC] blocks before responding to any HADS-related request.
Read [NOTE] blocks if you need context on intent or edge cases.
[SPEC]
**[SPEC]**, **[NOTE]**, **[BUG]**, **[?]**.md — standard Markdown, no tooling required[SPEC]
**[SPEC]** Authoritative fact. Terse. Bullet lists, tables, code. AI reads always.
**[NOTE]** Human context, history, examples. AI may skip.
**[BUG]** Verified failure + fix. Required fields: symptom, cause, fix. Always read.
**[?]** Unverified / inferred. Lower confidence. Always flagged.
Block tag rules:
**[SPEC]****[BUG] Short description**test cases passed, vs 8 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.