agentmods.dev

microsoft-writing-style

microsoft-writing-style is a skill for Claude Code, Codex from Neeeophytee/agent-stylebooks. It costs 64 tokens per session (644 once invoked), scanned A, original, MIT.

A writing guide for concise product and technical content, based on Microsoft writing guidance. It is intended for help pages, setup instructions, support content, interface text, errors, and technical explanations.

In plain words
What is it for?
Use it to draft, rewrite, or check product help, setup and support content, user-interface text, error messages, and technical documentation.
Why use it?
It helps readers understand what is happening and take the next step, while preserving exact product behavior, names, commands, versions, and limits.

Skill for Claude CodeCodex

Written for Claude Code and Codex: shipped in a Claude Code plugin, but also agents/openai.yaml present.

Part of the agent-stylebooks plugin — 16 skills shipped together

not rated 78repo +1 2mo ago A scan SkillSpector: pass 64 tokens original MIT

Good fit Use it to draft, rewrite, or check product help, setup and support content, user-interface text, error messages, and technical documentation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/neeeophytee/agent-stylebooks/microsoft-writing-style
View source ↗ Neeeophytee/agent-stylebooks
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add Neeeophytee/agent-stylebooks --skill microsoft-writing-style
Clone the repo
git clone --depth 1 https://github.com/Neeeophytee/agent-stylebooks

Made for: Claude Code, Codex.

Or install agent-stylebooks, the plugin that ships this one along with the rest of its 16 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for microsoft-writing-style

README.md
[![agentmods](https://agentmods.dev/badge/skills/neeeophytee/agent-stylebooks/microsoft-writing-style/github.svg)](https://agentmods.dev/skills/neeeophytee/agent-stylebooks/microsoft-writing-style)
Your own site
<a href="https://agentmods.dev/skills/neeeophytee/agent-stylebooks/microsoft-writing-style"><img src="https://agentmods.dev/badge/skills/neeeophytee/agent-stylebooks/microsoft-writing-style/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for microsoft-writing-style

Your own site · 80×15
<a href="https://agentmods.dev/skills/neeeophytee/agent-stylebooks/microsoft-writing-style"><img src="https://agentmods.dev/badge/skills/neeeophytee/agent-stylebooks/microsoft-writing-style.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 64 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 644 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00064 $0.00644
Opus 5.5 $0.00026 $0.00258
Sonnet 5.5 $0.00013 $0.00129
Haiku 4.5 $0.00006 $0.00064

Measured 2mo ago against content hash 161c4c959101, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

microsoft-writing-style scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/microsoft-writing-style/SKILL.md · 66 lines

How it starts

The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Microsoft writing style

Help the reader act with a warm, practical voice and the fewest words that still make the situation clear.

Protect the facts

  • Preserve product behavior, names, UI labels, commands, code, versions, and limits.
  • Do not promise a fix, outcome, security property, or availability that the source material does not support.
  • Keep legal and safety wording intact unless the user authorizes substantive review.
  • Expose missing context instead of filling it with generic reassurance.

Put first things first

  1. Identify the reader's intent and current state.
  2. Lead with the result, action, or problem they care about.
  3. Add only the context needed to choose or complete the next step.
  4. Break complex comparisons into a list or table with parallel structure.
  5. End with a next action, result, or recovery path rather than a recap.

Use a helpful voice

  • Address the reader as you and use natural contractions when they improve flow.
  • Choose familiar words and direct verbs. Keep technical terms when they are precise, and explain them at first use.
  • Prefer active voice. Name the app, service, or feature when it performs an action.
  • Keep paragraphs short and vary sentence length only where meaning benefits.
  • Use a calm, solution-oriented tone. Be more restrained for security, payment, failure, and data-loss contexts.
  • Write for global readers with literal language and explicit sentence structure.

Write product help and UI content

  • Start procedures with the action and keep commentary outside the step sequence.
  • Use verb-led labels that predict the result.
  • Match visible UI wording and capitalization.
  • For errors, state what did not happen, preserve any reassuring fact that is known, and give a specific recovery action.
  • Make the product take responsibility for product failures. Do not accuse the user.
  • Use fragments only when the interface context supplies the missing grammar.

Avoid

  • formal distance, corporate self-congratulation, and ceremonial introductions
  • unnecessary jargon, abbreviations, noun strings, and abstract framing
  • blaming language such as saying the user failed to perform an action
  • please in routine commands, difficulty judgments, and vague encouragement
  • long parenthetical asides and several clauses joined into one sentence
  • jokes, excitement, or exclamation marks in stressful situations
  • promises that support, security, or recovery will work without evidence

Read the full file on GitHub · 66 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2mo ago First seen · 66 lines · 64 tokens per session scan A 161c4c959101

Subscribe to this mod's changes

microsoft-writing-style is a skill published in the GitHub repository Neeeophytee/agent-stylebooks (78 stars, last pushed 2mo ago), licensed MIT. It adds 64 tokens to every session and 644 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Claude CodeWriting and docsagent-skillscontent-designdocumentationgemini-cliopenai-codex
Related

microsoft-writing-style compared with skills from other repositories

microsoft-writing-style next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
microsoft-writing-styleNeeeophytee/agent-stylebooksSkill782mo agoMITA64Claude Code, Codex
readmethuanvd378/write-me-a-readmeSkill23mo agoMITA103Claude Code, Codex
yapperdzan314/yapperSkill16mo agoMITA54Claude Code, Codex
spec-kitty-charter-doctrinePriivacy-ai/spec-kittySkill1.7k19d agoMITA135Claude Code, Codex
mongodb-query-optimizerfcakyon/claude-codex-settingsSkill1.2kyesterdayApache-2.0A98Claude Code
chisle-auditJayPokale/ChisleSkill74114d agoMITA130Claude Code
crane-shotcafe3310/public-agent-skillsSkill256yesterdayApache-2.0A25Claude Code, Codex