Agent skill

Hads

A skill your agent uses 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…

MITAuto-check passedDevelopment

Install Hads

skills CLI

$ npx skills add wshobson/agents --skill hads -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install wshobson/agents hads --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/wshobson/agents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/documentation-standards/skills/hads .claude/skills/hads && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "hads" agent skill from https://github.com/wshobson/agents/tree/main/plugins/documentation-standards/skills/hads into .claude/skills/hads/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hads", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/wshobson/agents/tree/main/plugins/documentation-standards/skills/hads

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add wshobson/agents --skill hads -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install wshobson/agents hads --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/wshobson/agents.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/documentation-standards/skills/hads .agents/skills/hads && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "hads" agent skill from https://github.com/wshobson/agents/tree/main/plugins/documentation-standards/skills/hads into .agents/skills/hads/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hads", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add wshobson/agents --skill hads -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install wshobson/agents hads --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/wshobson/agents.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/documentation-standards/skills/hads .cursor/skills/hads && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "hads" agent skill from https://github.com/wshobson/agents/tree/main/plugins/documentation-standards/skills/hads into .cursor/skills/hads/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hads", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/wshobson/agents.git --path plugins/documentation-standards/skills/hads

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add wshobson/agents --skill hads -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install wshobson/agents hads --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/wshobson/agents.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/documentation-standards/skills/hads .gemini/skills/hads && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "hads" agent skill from https://github.com/wshobson/agents/tree/main/plugins/documentation-standards/skills/hads into .gemini/skills/hads/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hads", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install wshobson/agents hads

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add wshobson/agents --skill hads -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/wshobson/agents.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/documentation-standards/skills/hads .github/skills/hads && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "hads" agent skill from https://github.com/wshobson/agents/tree/main/plugins/documentation-standards/skills/hads into .github/skills/hads/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hads", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add wshobson/agents --skill hads -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install wshobson/agents hads --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/wshobson/agents.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/documentation-standards/skills/hads .opencode/skills/hads && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "hads" agent skill from https://github.com/wshobson/agents/tree/main/plugins/documentation-standards/skills/hads into .opencode/skills/hads/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hads", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: hads
GitHub stars: 40k
Token cost: ~1.5k tokens
SKILL.md length: 664 words
Files: 1
Skills in repo: 142
Repo updated: Oct 5, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

A skill your agent uses 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…

Works in 9 steps: WHAT IS HADS → BLOCK TYPES → REQUIRED DOCUMENT STRUCTURE → …
Writing technical documentation that needs to be readable by both humans and AI models
SKILL.md covers AI READING INSTRUCTION, 1. WHAT IS HADS, 2. BLOCK TYPES and 3. REQUIRED DOCUMENT STRUCTURE, plus 6 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Hads is an agent skill from wshobson/agents. 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.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Technical documentation. The repository describes itself as: Multi-harness agentic plugin marketplace for Claude Code, Codex, Cursor, OpenCode, GitHub Copilot, Google Antigravity, and Pi. The licence is MIT.

When your agent uses it

Writing technical documentation that needs to be readable by both humans and AI models
Converting existing docs to HADS format
Validating a HADS document
Optimizing documentation for token-efficient AI consumption

Example prompts

“/hads”

Workflow steps

9 steps, taken from the step headings in SKILL.md.

WHAT IS HADS
BLOCK TYPES
REQUIRED DOCUMENT STRUCTURE
HOW CLAUDE READS HADS
HOW CLAUDE GENERATES HADS
VALIDATION RULES
EXAMPLE INTERACTIONS
DESIGN INTENT
QUICK REFERENCE

What it can do on your machine

Read from SKILL.md and the folder at commit 46891e7. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Hads loads about 1.5k tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 664 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~59
When it runs · the whole SKILL.md, loaded when a task matches: ~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from wshobson/agents at commit 46891e7, republished under its MIT licence (© wshobson). 664 words, ~1,517 tokens.

Download SKILL.mdSave it as .claude/skills/hads/SKILL.md (or your agent's skills folder).

name: hads
description: 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.

HADS Claude Skill

Version 1.0.0 · Human-AI Document Standard · 2026 · HADS 1.0.0

AI READING INSTRUCTION

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.

1. WHAT IS HADS

[SPEC]

HADS = Human-AI Document Standard
Convention for Markdown technical documentation
Four block types: **[SPEC]**, **[NOTE]**, **[BUG]**, **[?]**
Every HADS document requires: H1 title, version declaration, AI manifest
AI manifest appears before first content section, tells AI what to read/skip
File extension: .md — standard Markdown, no tooling required

2. BLOCK TYPES

[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:

Bold, on its own line: **[SPEC]**
Content follows immediately (no blank line between tag and content)
Multiple blocks of different types allowed per section
Titled BUG blocks allowed: **[BUG] Short description**
No nesting of blocks inside blocks

3. REQUIRED DOCUMENT STRUCTURE

[SPEC]

markdown

# Document Title
**Version X.Y.Z** · Author · Date · [metadata]

---

## AI READING INSTRUCTION

Read `[SPEC]` and `[BUG]` blocks for authoritative facts.
Read `[NOTE]` only if additional context is needed.
`[?]` blocks are unverified — treat with lower confidence.

---

## 1. First Section

**[SPEC]**
...

Required elements in order:

H1 title
**Version X.Y.Z** in header (first 20 lines)
AI manifest section before first content section
Content sections (H2), subsections (H3)

4. HOW CLAUDE READS HADS

[SPEC] When encountering a HADS document:

Find and read the AI manifest first
Read all [SPEC] blocks — these are ground truth
Read all [BUG] blocks — always, before generating any code or config
Read [NOTE] blocks only if [SPEC] is insufficient to answer the query
Treat [?] content as hypothesis — note uncertainty in response

Token optimization: for large documents, scan section headings first, then read only [SPEC] and [BUG] blocks in relevant sections.

5. HOW CLAUDE GENERATES HADS

[SPEC] When asked to write documentation in HADS format:

Start with header block (title, version, metadata)
Add AI manifest — always include, never skip
Organize content into numbered H2 sections
For each fact: write as [SPEC] — terse, bullet or table or code
For each "why" or context: write as [NOTE]
For each known failure mode with confirmed fix: write as [BUG]
For each unverified claim: write as [?]
End with changelog section

Content rules for [SPEC]:

Prefer bullet lists over prose
Prefer tables for multi-field facts
Prefer code blocks for syntax, formats, examples
Maximum 2 sentences of prose — if more needed, move to [NOTE]

Content rules for [BUG]:

Always include: symptom, cause, fix
Optional: affected versions, workaround
Title on same line: **[BUG] Short description**

[NOTE] When converting existing documentation to HADS: extract facts into [SPEC], move narrative and history to [NOTE], surface all known issues as [BUG]. Do not duplicate content between block types.

Show full SKILL.md (242 more words)Show less

6. VALIDATION RULES

[SPEC] A valid HADS document must have:

H1 title
**Version X.Y.Z** in first 20 lines
AI manifest before first content section
All block tags bold: **[SPEC]** not [SPEC] not [SPEC]
[BUG] blocks contain at minimum symptom + fix

Validator: (planned — not yet included in this release)

7. EXAMPLE INTERACTIONS

[SPEC]

User: "Write HADS documentation for this REST API" → Generate full HADS document: header, manifest, sections with [SPEC]/[NOTE]/[BUG] blocks

User: "Convert this README to HADS format" → Restructure existing content into HADS blocks, preserve all facts, add manifest

User: "Is this document valid HADS?" → Check: H1 title, version, manifest, block tag formatting, BUG block completeness

User: "Summarize this HADS document" → Read only [SPEC] and [BUG] blocks, return structured summary

User: "What does this API do?" (HADS doc provided) → Read manifest, read [SPEC] blocks in relevant sections, answer directly

8. DESIGN INTENT

[NOTE] HADS exists because AI models increasingly read documentation before humans do. The format optimizes for this reality without sacrificing human readability.

Key insight: the AI manifest is the core innovation. It lets even small (7B) models know what to read and what to skip — without requiring them to reason about document structure. Explicit is better than implicit for model consumption.

When generating HADS, think of [SPEC] as the API surface and [NOTE] as the comments. [BUG] blocks are the most valuable content — they represent hard-won knowledge that saves others from hitting the same wall.

9. QUICK REFERENCE

[SPEC]

Tag       | Bold format    | Reader  | Required content
----------|----------------|---------|------------------
[SPEC]    | **[SPEC]**     | AI      | Facts, terse
[NOTE]    | **[NOTE]**     | Human   | Context, narrative
[BUG]     | **[BUG] ...**  | Both    | Symptom + fix
[?]       | **[?]**        | Both    | Unverified claims

Manifest minimum:

markdown

## AI READING INSTRUCTION
Read `[SPEC]` and `[BUG]` blocks for authoritative facts.
Read `[NOTE]` only if additional context is needed.
`[?]` blocks are unverified.

Files

Just SKILL.md in plugins/documentation-standards/skills/hads of wshobson/agents.

Open the folder on GitHubat commit 46891e7

Compare with similar skills

Hads next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Hads compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Hads this skillwshobson/agents	40k	—	~1.5k	Automated safety check: Pass	MIT	5 days ago
Diagram Designcathrynlavery/diagram-design	47k	1 repos	~7.5k	Automated safety check: Pass	MIT	2 days ago
Simple Englishmoeru-ai/airi	50k	2 repos	~4.6k	Automated safety check: Pass	MIT	today
Doc SyncJetBrains/ideavim	10k	2 repos	~2.6k	Automated safety check: Pass	MIT	today
Mailspring App ScreenshotsFoundry376/Mailspring	18k	—	~1.5k	Automated safety check: Pass	GPL-3.0	today
Draw.io Diagram StudioAgents365-ai/drawio-skill	10k	—	~2.4k	Automated safety check: Notes	MIT	7 days ago

Similar skills

Diagram Design
cathrynlavery/diagram-design
Creates branded diagrams, from architecture, flowchart and sequence to charts and maps, as self-contained HTML with inline SVG, with import from draw.io, Mermaid and Excalidraw.
47k GitHub starsUsed in 1 repo~7.5k tokens
DevelopmentAuto-check passed
Simple English
moeru-ai/airi
Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop.
50k GitHub starsUsed in 2 repos~4.6k tokens
DevelopmentAuto-check passed
Doc Sync
JetBrains/ideavim
Official
Keeps IdeaVim documentation in sync with code changes. An agent skill from JetBrains/ideavim.
10k GitHub starsUsed in 2 repos~2.6k tokens
DevelopmentAuto-check passed
Mailspring App Screenshots
Foundry376/Mailspring
Captures screenshots of the running Mailspring dev app for docs, PRs or visual checks by launching it with a debugging port, driving the UI and clipping to an element.
18k GitHub stars~1.5k tokensUpdated today
DevelopmentAuto-check passed
Draw.io Diagram Studio
Agents365-ai/drawio-skill
Creates and edits editable draw.io diagrams from descriptions, code, infrastructure files, SQL and API schemas, with sync, review, test and export tools.
10k GitHub stars~2.4k tokensUpdated 7 days ago
DevelopmentAuto-check: notes
Dark Architecture Diagram Builder
Cocoon-AI/architecture-diagram-generator
Creates dark-themed system, cloud, security and network architecture diagrams as self-contained HTML files with inline SVG and CSS.
7.4k GitHub starsUsed in 1 repo~2.1k tokens
DevelopmentAuto-check passed

Questions about Hads

What does Hads do?

A skill your agent uses 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…. Hads is an agent skill from wshobson/agents. 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.

When should I use Hads?

Hads fits situations like: writing technical documentation that needs to be readable by both humans and AI models; converting existing docs to HADS format; validating a HADS document; optimizing documentation for token-efficient AI consumption.

How do I install Hads in Claude Code?

Run `npx skills add wshobson/agents --skill hads -a claude-code`. Or copy the skill folder (plugins/documentation-standards/skills/hads in wshobson/agents) into .claude/skills/hads in your project. Claude Code loads it when a task matches its description.

How do I install Hads in Codex?

Run `npx skills add wshobson/agents --skill hads -a codex`. Or copy the skill folder (plugins/documentation-standards/skills/hads in wshobson/agents) into .agents/skills/hads in your project. Codex loads it when a task matches its description.

Can I use Hads in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add wshobson/agents --skill hads -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/hads, .gemini/skills/hads, .github/skills/hads and .opencode/skills/hads in your project.

What does Hads need to run?

SKILL.md names no scripts, command-line tools or credentials: Hads is instructions for the agent only.

Does Hads access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Hads safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Hads use?

Hads is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Hads use?

About 1.5k tokens (SKILL.md is roughly 6.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Hads?

Skills that share tags, products or a category with Hads: Diagram Design (cathrynlavery/diagram-design, 47k stars), Simple English (moeru-ai/airi, 50k stars), Doc Sync (JetBrains/ideavim, 10k stars) and Mailspring App Screenshots (Foundry376/Mailspring, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Hads?

wshobson (a GitHub user) maintains it in wshobson/agents, which has 40,305 GitHub stars. The repository holds 142 skills in this directory. The repository was last updated on October 5, 2026.

Source: wshobson/agents on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Hads

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

HADS Claude Skill

AI READING INSTRUCTION

1. WHAT IS HADS

2. BLOCK TYPES

3. REQUIRED DOCUMENT STRUCTURE

4. HOW CLAUDE READS HADS

5. HOW CLAUDE GENERATES HADS

6. VALIDATION RULES

7. EXAMPLE INTERACTIONS

8. DESIGN INTENT

9. QUICK REFERENCE

Files

Compare with similar skills

Similar skills

More from wshobson/agents

Related

Questions about Hads