Jonathon's AI Wiki

Agent Stylebooks — Editorial Systems as Installable Skills

5 min read

Source: raw/reddit-1vsnojk.md (r/hermesagent, u/ShilpaMitra, “Showcase” flair, 14 pts / 3 comments, 2026-08-19). Repo state independently verified via the GitHub API on 2026-08-19.

Repo: Neeeophytee/agent-stylebooks | Stars: 28 | Language: Python | License: MIT

Agent Stylebooks packages 16 real organizational style guides as installable agent skills, on the premise that “write better,” “sound human,” and “be concise” are not writing systems — they are preferences the model drifts away from. Instead of a vague instruction, you invoke a named editorial system that an actual organization spent years building.

Key Takeaways

  • The argument is that vagueness is the bug. Telling an agent to “make this clearer” gives it nothing to conform to, so it reverts to its default voice. A named stylebook gives it a specific target with published rules. This is the same diagnosis the wiki records in Claudish-to-English — that prose instructions do not stick — approached from the instruction side rather than the display side.
  • Style is selected per artifact, not per project. The source’s worked example: the topic is Kubernetes throughout, but $kubernetes-docs handles a deployment tutorial, $govuk handles a public-facing eligibility page, and $apple-interface-writing handles the buttons and error strings in a cluster-management UI. Same subject, three different writing problems.
  • The hard constraint is the interesting design decision: changing style must not change facts, commands, versions, legal meaning, or technical behavior. A style transform that can silently alter a version number or a legal disclaimer is worse than no transform, and the collection is explicit about that boundary.
  • Skills install once and are invoked on demand rather than pasted into every prompt — the progressive-disclosure pattern from Agent Skills, applied to writing style.
  • It ships provenance rather than scraped prompts. The repo carries PROVENANCE.md, NOTICE.md, and a STYLE-MATRIX.md; the author’s claim is that the skills encode principles with sourcing, not copied style-guide text.
  • Agent-agnostic by construction. The repo carries .claude-plugin, .codex-plugin, and .agents directories plus COMPATIBILITY.md — Claude Code, Codex, and Hermes are all targeted, despite the post appearing in r/hermesagent.
  • Verified repo state (GitHub API, 2026-08-19): MIT licensed, 28 stars, not archived, created 2026-08-18, pushed the day of writing. Ships LICENSE, CHANGELOG.md, CONTRIBUTING.md, INSTALL.md, EXAMPLES.md, CATALOG.md, and scripts/validate_repo.py.
  • The repo’s own description is already stale. It says “11 installable editorial systems”; the skills/ directory contains 16, matching the post exactly. The post is the accurate count.

The 16 stylebooks

SkillBuilt for
google-developer-docsAPI docs, tutorials, setup guides
github-docsProduct workflows and troubleshooting
gitlab-docsConcise engineering/product documentation
kubernetes-docsVersion-sensitive infrastructure docs
mdn-web-docsWeb technology explanations and references
red-hat-docsEnterprise procedures and runbooks
microsoft-writing-styleProduct help and support copy
apple-interface-writingButtons, alerts, UI copy
mailchimp-contentHuman customer communication
govukPublic-service and eligibility content
18f-contentAccessible digital public services
cdc-clear-communicationPublic-health communication
nhs-health-contentPatient-facing health information
sec-plain-englishFinancial/investor disclosures
w3c-technical-reportsSpecifications and standards
nasa-technical-writingEngineering and technical reports

Implementation

  • Tool/Service: Neeeophytee/agent-stylebooks (MIT).
  • Setup: 
    npx skills add Neeeophytee/agent-stylebooks --list          # inspect the catalog first
npx skills add Neeeophytee/agent-stylebooks --skill google-developer-docs
npx skills add Neeeophytee/agent-stylebooks                 # install the whole collection
  • Cost: Free, open source.
  • Integration notes: Once installed, the instruction stays short — “Use $google-developer-docs to turn these verified implementation notes into a setup guide.” Installing all 16 puts 16 entries in the skill catalog, which is a standing context cost even when unused; install selectively unless you genuinely switch registers often.

Try It

  • Pick the two registers you actually write in and install only those. The catalog cost is real; the collection is a menu, not a bundle to swallow.
  • Test the fact-preservation boundary deliberately. Hand a stylebook a passage containing a version number, a shell command, and a legal qualifier, and check all three survive. That constraint is the collection’s core claim and the thing most worth falsifying.
  • Use it where the register genuinely differs from the topic — the Kubernetes-vs-GOV.UK case above is the real unlock, not general “better writing.”
  • Watch the repo before depending on it. One day old at time of writing.

Open Questions

  • No maintainer history. Created 2026-08-18, 28 stars, single author. It has license, docs, and a validation script — good hygiene — but none of the durability signals the wiki’s bar normally wants. Treat as promising, not established.
  • Are the skills evaluated, or asserted? validate_repo.py validates repo structure; nothing in the source establishes that a stylebook’s output actually matches the house style it names.
  • Does the fact-preservation constraint hold under adversarial input? Stated as a rule in the skill text, which is an instruction, not an enforcement mechanism.
  • How does this interact with output styles? A stylebook skill and a Claude Code output style both shape prose but load differently and carry different authority (see Steering Claude Code). Their interaction is undocumented.
  • Licensing of the underlying guides. PROVENANCE.md and NOTICE.md exist and the author says principles were encoded rather than text scraped; this was not independently checked here.

Graph View

Backlinks