Writing for Agents Skill for Muse
Write docs agents actually follow — skills, AGENTS.md, CLAUDE.md
- What
- Write docs agents actually follow — skills, AGENTS.md, CLAUDE.md
- Cost
- Free
- Needs
- none — this is a writing reference. Useful if you write skills, AGENTS.md/CLAUDE.md files, or agent-facing docs.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
A craft reference for writing any document an agent consumes — a skill, an AGENTS.md/CLAUDE.md, or a doc reached by a pointer. It teaches context pointers (the wording, not the target, decides when material loads; front-load the leading word, one trigger per branch), the two loads every document spends (context load on the agent's window vs cognitive load on the human), the information-hierarchy ladder (in-file steps, in-file reference, disclosed reference behind a pointer) with progressive disclosure and co-location, steps that end on completion criteria (clarity and demand, defending against premature completion), when to split by sequence or invocation, leading words that recruit the model's pretrained concepts, and a pruning discipline (single source of truth, no-ops, sediment). A companion `SKILL-MECHANICS.md` covers frontmatter and invocation mechanics for skills. Discovered via skills.sh. skills.sh Trust Hub check: passed. Honest note: this is a writing reference, not a tool — no scripts, no automation; it changes how you write, not what you run. Fetch `SKILL-MECHANICS.md` with the SKILL.md. Skill Harbor never reviews the code, review it yourself before use.
Curated by Skill Harbor — free, open-source skill (MIT) by @mattpocock.
Version:
Quick answer
Writing for Agents Skill for Muse is a free Muse skill that teaches how to write documentation agents can use. It covers context pointers, two loads, an information-hierarchy ladder, progressive disclosure, completion criteria, split rules, treating writing as interface design. It is a reference guide, not a tool, structuring knowledge so an agent finds the right detail in time.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 18, 2026📌 Pinned version: commit 49dd158Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: none — this is a writing reference. Useful if you write skills, AGENTS.md/CLAUDE.md files, or agent-facing docs. Install "Writing for Agents Skill for Muse" for me. A craft reference for writing documents agents actually follow: context pointers, context vs cognitive load, the information-hierarchy ladder with progressive disclosure, steps with completion criteria, when to split documents, leading words, and pruning — plus a SKILL-MECHANICS.md companion for skill frontmatter and invocation. Repository: https://raw.githubusercontent.com/mattpocock/skills/49dd158d1076134a641b33efb035946536778336/skills/productivity/writing-for-agents/SKILL.md Pinned version: install the code at commit 49dd158d1076134a641b33efb035946536778336 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files: SKILL-MECHANICS.md) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "writing-for-agents". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. have the document I want to improve handy). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 49dd158 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 18, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.