Writing Style
OpenLAIR/dr-claw
Apply the 21 prose rules from "The Elements of Agent Style" — 12 canonical rules (Strunk, Orwell, Pinker) plus 9 field-observed AI-output patterns.
Review and improve writing style, voice, tone, readability, inclusive language, Arm terminology, heading style, word choice, and AI-sounding prose in Arm Learning Paths and install guides.
Install Writing Style Review
$ npx skills add ArmDeveloperEcosystem/arm-learning-paths --skill writing-style-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ArmDeveloperEcosystem/arm-learning-paths writing-style-review --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ArmDeveloperEcosystem/arm-learning-paths.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/writing-style-review .claude/skills/writing-style-review && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "writing-style-review" agent skill from https://github.com/ArmDeveloperEcosystem/arm-learning-paths/tree/main/.github/skills/writing-style-review into .claude/skills/writing-style-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-style-review", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ArmDeveloperEcosystem/arm-learning-paths/tree/main/.github/skills/writing-style-reviewType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ArmDeveloperEcosystem/arm-learning-paths --skill writing-style-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ArmDeveloperEcosystem/arm-learning-paths writing-style-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ArmDeveloperEcosystem/arm-learning-paths.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/writing-style-review .agents/skills/writing-style-review && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "writing-style-review" agent skill from https://github.com/ArmDeveloperEcosystem/arm-learning-paths/tree/main/.github/skills/writing-style-review into .agents/skills/writing-style-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-style-review", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ArmDeveloperEcosystem/arm-learning-paths --skill writing-style-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ArmDeveloperEcosystem/arm-learning-paths writing-style-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ArmDeveloperEcosystem/arm-learning-paths.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/writing-style-review .cursor/skills/writing-style-review && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "writing-style-review" agent skill from https://github.com/ArmDeveloperEcosystem/arm-learning-paths/tree/main/.github/skills/writing-style-review into .cursor/skills/writing-style-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-style-review", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ArmDeveloperEcosystem/arm-learning-paths.git --path .github/skills/writing-style-review--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ArmDeveloperEcosystem/arm-learning-paths --skill writing-style-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ArmDeveloperEcosystem/arm-learning-paths writing-style-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ArmDeveloperEcosystem/arm-learning-paths.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/writing-style-review .gemini/skills/writing-style-review && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "writing-style-review" agent skill from https://github.com/ArmDeveloperEcosystem/arm-learning-paths/tree/main/.github/skills/writing-style-review into .gemini/skills/writing-style-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-style-review", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ArmDeveloperEcosystem/arm-learning-paths writing-style-reviewInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ArmDeveloperEcosystem/arm-learning-paths --skill writing-style-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ArmDeveloperEcosystem/arm-learning-paths.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/writing-style-review .github/skills/writing-style-review && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "writing-style-review" agent skill from https://github.com/ArmDeveloperEcosystem/arm-learning-paths/tree/main/.github/skills/writing-style-review into .github/skills/writing-style-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-style-review", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ArmDeveloperEcosystem/arm-learning-paths --skill writing-style-review -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ArmDeveloperEcosystem/arm-learning-paths writing-style-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ArmDeveloperEcosystem/arm-learning-paths.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/writing-style-review .opencode/skills/writing-style-review && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "writing-style-review" agent skill from https://github.com/ArmDeveloperEcosystem/arm-learning-paths/tree/main/.github/skills/writing-style-review into .opencode/skills/writing-style-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-style-review", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
writing-style-review- GitHub stars
- 154
- Token cost
- ~1.9k tokens
- SKILL.md length
- 1,055 words
- Files
- 1
- Skills in repo
- 15
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Review and improve writing style, voice, tone, readability, inclusive language, Arm terminology, heading style, word choice, and AI-sounding prose in Arm Learning Paths and install guides.
- Works in 4 steps: Identify the target file, section, or… → Read surrounding context so style edits… → Review the target against the guidelines… → …
- Asked to polish prose
- SKILL.md covers Workflow, Voice and tone, Inclusive language and Sentence structure and…, plus 7 more sections
- Calls aws
What it does
Writing Style Review is an agent skill from ArmDeveloperEcosystem/arm-learning-paths. Review and improve writing style, voice, tone, readability, inclusive language, Arm terminology, heading style, word choice, and AI-sounding prose in Arm Learning Paths and install guides. Use when asked to polish prose, make content less AI-generated, improve clarity, or align with Arm editorial style.
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Writing & Content, covering Brand voice and tone, Plain language and style rules and Curriculum and course design. The repository describes itself as: Arm Learning Paths: a repository of how-to content for software developers.
When your agent uses it
- Asked to polish prose
- Make content less AI-generated
- Improve clarity
- Align with Arm editorial style
Example prompts
- “/writing-style-review”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Identify the target file, section, or selected text.
- Read surrounding context so style edits preserve the author's intent and the technical flow. If you've previously read the page, use…
- Review the target against the guidelines defined in this skill.
- Depending on request type, do the following
What it can do on your machine
Read from SKILL.md and the folder at commit 44a1644. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
aws
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use aws, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Writing Style Review loads about 1.9k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 1,055 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,055 words (~1,878 tokens).
“Use this skill for granular prose, voice, readability, terminology, and style reviews. Keep edits focused and preserve technical meaning.”
- name
- writing-style-review
Files
Just SKILL.md in .github/skills/writing-style-review of ArmDeveloperEcosystem/arm-learning-paths.
Open the folder on GitHubat commit 44a1644
Compare with similar skills
Writing Style Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Writing Style Review this skillArmDeveloperEcosystem/arm-learning-paths | 154 | — | ~1.9k | Automated safety check: Pass | Custom licence | |
| Writing StyleOpenLAIR/dr-claw | 1.2k | — | ~2.4k | Automated safety check: Pass | CC-BY-4.0 | |
| Avoid AI Writingconorbronsdon/avoid-ai-writing | 4.9k | 3 repos | ~8.1k | Automated safety check: Pass | MIT | |
| Natural Japanese Business Writingcoji/natural-japanese | 1.9k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Unslop AI Writing Cleanuptheclaymethod/unslop | 512 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Remove AI Patternspchalasani/claude-code-tools | 2k | — | ~1.4k | Automated safety check: Pass | MIT |
Similar skills
Avoid AI Writing
conorbronsdon/avoid-ai-writing
Audit and rewrite content to remove AI writing patterns ("AI-isms").
Natural Japanese Business Writing
coji/natural-japanese
Writes and edits Japanese business documents so they read clearly and naturally, removes AI-sounding phrasing and can score how AI-like a text reads.
Unslop AI Writing Cleanup
theclaymethod/unslop
Removes AI writing tells from prose through an audit-first flow, routing to a two-pass rewrite, a report-only cleanup, voice teaching or mimicry depending on the sub-command used.
Remove AI Patterns
pchalasani/claude-code-tools
Remove AI-writing patterns ("AI-isms") from text using the avoid-ai-writing catalog (conorbronsdon/avoid-ai-writing).
UX Writing
content-designer/ux-writing-skill
Applies UX writing practice to interface copy such as buttons, errors, forms and onboarding, using four quality standards and accessibility guidance.
More from ArmDeveloperEcosystem/arm-learning-paths
All 15 skills in this repoAudit Images
ArmDeveloperEcosystem/arm-learning-paths
Audit and fix Markdown image alt text in Arm Learning Paths and install guides.
Refactor Learning Path Editorial
ArmDeveloperEcosystem/arm-learning-paths
Audit and refactor an existing Arm Learning Path for editorial structure, front matter, discoverability, writing style, accessibility, images, links, Markdown presentation, and code-sample…
Stale Content Review
ArmDeveloperEcosystem/arm-learning-paths
Scan Arm Learning Paths and install guides for stale-content risk.
Draft Learning Path
ArmDeveloperEcosystem/arm-learning-paths
Toggle draft mode on a Learning Path index.md. An agent skill from ArmDeveloperEcosystem/arm-learning-paths.
Install Guide Structure Review
ArmDeveloperEcosystem/arm-learning-paths
Review Arm install guides for structural soundness, installation-only scope, verification quality, OS-specific sections, troubleshooting, multi-page guide behavior, and version-note placement.
Link Text Review
ArmDeveloperEcosystem/arm-learning-paths
Review and improve accessible Markdown link text in Arm Learning Paths and install guides.
Related
Categories
Questions about Writing Style Review
What does Writing Style Review do?
Review and improve writing style, voice, tone, readability, inclusive language, Arm terminology, heading style, word choice, and AI-sounding prose in Arm Learning Paths and install guides. Writing Style Review is an agent skill from ArmDeveloperEcosystem/arm-learning-paths. Review and improve writing style, voice, tone, readability, inclusive language, Arm terminology, heading style, word choice, and AI-sounding prose in Arm Learning Paths and install guides.
When should I use Writing Style Review?
Writing Style Review fits situations like: asked to polish prose; make content less AI-generated; improve clarity; align with Arm editorial style.
How do I install Writing Style Review in Claude Code?
Run `npx skills add ArmDeveloperEcosystem/arm-learning-paths --skill writing-style-review -a claude-code`. Or copy the skill folder (.github/skills/writing-style-review in ArmDeveloperEcosystem/arm-learning-paths) into .claude/skills/writing-style-review in your project. Claude Code loads it when a task matches its description.
How do I install Writing Style Review in Codex?
Run `npx skills add ArmDeveloperEcosystem/arm-learning-paths --skill writing-style-review -a codex`. Or copy the skill folder (.github/skills/writing-style-review in ArmDeveloperEcosystem/arm-learning-paths) into .agents/skills/writing-style-review in your project. Codex loads it when a task matches its description.
Can I use Writing Style Review in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ArmDeveloperEcosystem/arm-learning-paths --skill writing-style-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/writing-style-review, .gemini/skills/writing-style-review, .github/skills/writing-style-review and .opencode/skills/writing-style-review in your project.
What does Writing Style Review need to run?
Going by SKILL.md and its folder, Writing Style Review needs the command-line tools its instructions call (aws).
Does Writing Style Review access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Writing Style Review safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Writing Style Review use?
Writing Style Review has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Writing Style Review use?
About 1.9k tokens (SKILL.md is roughly 7.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Writing Style Review?
Skills that share tags, products or a category with Writing Style Review: Writing Style (OpenLAIR/dr-claw, 1.2k stars), Avoid AI Writing (conorbronsdon/avoid-ai-writing, 4.9k stars), Natural Japanese Business Writing (coji/natural-japanese, 1.9k stars) and Unslop AI Writing Cleanup (theclaymethod/unslop, 512 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Writing Style Review?
ArmDeveloperEcosystem (a GitHub organization) maintains it in ArmDeveloperEcosystem/arm-learning-paths, which has 154 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 7, 2026.
Source: ArmDeveloperEcosystem/arm-learning-paths on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.