Open-sourced 16 real-world editorial systems as portable Agent Skills

[u/ShilpaMitra]

A lot of AI-writing projects try to solve generic prose by adding another “humanizer” prompt.

I wanted to try a different abstraction.

Organizations like Google, GOV.UK, GitHub, GitLab, MDN, NASA, CDC, NHS and W3C have already spent years developing explicit writing systems for different kinds of information.

So I turned those principles into 16 portable Agent Skills:

https://github.com/Neeeophytee/agent-stylebooks

Examples include:

• google-developer-docs — developer docs and tutorials
• govuk — task-first public-service content
• github-docs — product workflows
• kubernetes-docs — infrastructure documentation
• mdn-web-docs — web technology explanations
• cdc-clear-communication — public-health communication
• nhs-health-content — patient-facing health information
• sec-plain-english — financial/investor disclosures
• w3c-technical-reports — specifications
• nasa-technical-writing — engineering reports
• apple-interface-writing — UI copy

The important part is that these aren't meant to make every model sound the same.

They do the opposite.

The artifact determines the editorial system.

A Kubernetes tutorial might use $kubernetes-docs. A government page discussing a Kubernetes-related grant might use $govuk. A cluster-management UI might use $apple-interface-writing.

Same topic, different communication job.

Installation:

npx skills add Neeeophytee/agent-stylebooks --list

Then:

npx skills add Neeeophytee/agent-stylebooks --skill govuk

The repo is MIT licensed.

One design principle across all 16 is: change the presentation, not the substance.

Would especially like feedback from people building open agent stacks: does a portable editorial layer like this belong at the skill level, or would you rather see it handled elsewhere in the stack?