Menu
Convert any technical document (README, API docs, spec, wiki page) into valid HADS format. Triggers on "convert to HADS", "HADS this", "make this HADS-compatible", or any request to optimize a document for AI consumption.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Edits any writing so it sounds specific, human, and not AI-polished. Use when the user asks to remove AI writing tells, make text less generic/SaaS-y/corporate/LinkedIn, preserve personal voice, rewrite copy, review wording, or make writing more dry, direct, warm, blunt, or natural.
Reviews recent Pi conversation/session logs to find repeated friction, ambiguity loops, expensive reasoning, user corrections, and missing skills, MCP servers, scripts, or workflow guardrails. Use for daily or weekly retrospectives, "review our conversations", "what skills are missing", "tighten the loop", "thinking token spend", or "make the harness smarter".
Manage Google Workspace via the gws CLI — Drive, Gmail, Sheets, Docs, Slides, People, Chat, Meet, Forms, and cross-service workflows. Use when asked to send email, read/write spreadsheets, upload files to Drive, manage contacts, create presentations, send Chat messages, create docs, or any Google Workspace operation. Also triggers on "gws", "Google Drive", "Google Sheets", "Gmail", "Google Docs", "Google Slides", "Google Chat", "Google Meet", "Google Forms", "check my inbox", "upload to Drive", "read spreadsheet", "send an email", "create a doc", "send a chat message", "create a presentation".
Embody this digital identity. Read SOUL.md first, then STYLE.md, then examples/. Become the person—opinions, voice, worldview.
Design engineering principles for making interfaces feel polished. Use when building UI components, reviewing frontend code, implementing animations, hover states, shadows, borders, typography, micro-interactions, enter/exit animations, or any visual detail work. Triggers on UI polish, design details, "make it feel better", "feels off", stagger animations, border radius, optical alignment, font smoothing, tabular numbers, image outlines, box shadows.
Orchestrate cmux terminal panes — split terminals, run parallel processes, read output from other panes, and use the built-in browser. Use when working inside cmux and you need to run a dev server, watch tests, spawn sub-agents, or preview web pages.
| name | hads-convert |
| description | Convert any technical document (README, API docs, spec, wiki page) into valid HADS format. Triggers on "convert to HADS", "HADS this", "make this HADS-compatible", or any request to optimize a document for AI consumption. |
Version 1.0.0 · hads-skills · 2026
Read [SPEC] blocks for conversion rules.
Read [BUG] blocks before writing any output.
[NOTE] blocks explain intent — read if a rule is unclear.
[SPEC] Activate when user:
[NOTE] Tokens are spent once at conversion. Every future AI read of the output is cheaper. This is the core value proposition — convert once, save on every subsequent call.
[SPEC] Accept any of:
If input is ambiguous, ask: "File path, paste, or URL?"
[SPEC] Classify every piece of content before writing:
| Source content | Output block |
|---|---|
| Fact, requirement, spec, API contract | **[SPEC]** |
| History, rationale, example, narrative | **[NOTE]** |
| Known bug, failure mode, gotcha, workaround | **[BUG] Title** |
| Unverified, assumed, inferred, "probably" | **[?]** |
Rules:
[SPEC] content: bullet lists or tables, max 2 sentences prose[BUG] blocks must contain: symptom, cause, fix (all three)[NOTE]
When in doubt between [SPEC] and [NOTE]: if a developer must know it to use the thing correctly, it's [SPEC]. If it explains why, it's [NOTE].
[SPEC] Write output in this exact order:
# [Original title or inferred title]
**Version [preserved or 1.0.0]** · [Author if known] · [Date: today] · HADS 1.0.0
---
## 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. [Section]
**[SPEC]**
...
[SPEC]
[original-name].hads.md (keep original intact)filename.hads.md"[SPEC] After writing, report:
[SPEC], Y [NOTE], Z [BUG], W [?][?] blocks explicitly — user must verify these[BUG] Silent data loss on dense prose
[SPEC] bullets, losing nuance[NOTE] intact, only extract verifiable facts into [SPEC]