
writing-guidelines
#4 in Documentation for DevelopersReview docs/prose for Writing Guidelines compliance.
Overview
Review docs/prose for Writing Guidelines compliance. Use when asked to "review my docs", "check writing style", "audit prose", "review docs voice and tone", or "check this page against the writing handbook".From the project's GitHub description
Our editorial assessment of writing-guidelines is still in review. Facts below come from the repository and our catalogue.
Good for
Technical specifications
Each attribute is labelled with where it came from.
- Software type
- Agent / Skillevidence
- Agent ecosystem
- Skillevidence
- Interface
- No direct user interfaceevidence
- Runtime
- Agent runtimeevidence
- Interaction model
- Agent-operatedevidence
- Deployment model
- Local installationevidence
- License
- Not verified. GitHub could not identify this licence; check the repository before adopting.
Install
A skill is a set of instructions your agent loads. Install it into the agent you use; there is nothing to host.
$ npx skills add https://github.com/vercel-labs/agent-skills --skill writing-guidelines- Listing
- skills.shInstall counts come from skills.sh.
Alternatives
Also in Documentation for Developers
Same category, not necessarily equivalent.
microsoft-docs
Query official Microsoft documentation to find concepts, tutorials, and code examples across Azure, .NET, Agent Framework, Aspire, VS Code, GitHub, and more.
microsoft-code-reference
Look up Microsoft API references, find working code samples, and verify SDK code is correct.
Reviews
Community ratings are kept separate from Beav Scout rankings.
No reviews yet. Community reviews and comments are opening soon; you'll be able to rate writing-guidelines once signed in.