Proofread Markdown Agent Skill
Proofreads Markdown files against Google guidelines.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/flutter/website --skill proofread-markdownWhat comes with it
3 733 bytes besides the instructionThe instruction itself
9 sections, as written by the authorProofreading Markdown
Overview
Help us transform technical text into clear, concise,
and machine-readable Markdown. We follow the
Google Developer Documentation Style Guide.
Workflow
1. Check line length
- [ ] Wrap lines semantically and keep them generally under 80 characters using
scripts/wrap_lines.dart
- [ ] Never touch the front matter.
Do not modify the content between the first two --- lines at the top of the file.
- [ ] Verify that the file was wrapped correctly,
preserving headings and code blocks
2. Fix voice and tone
- [ ] Use active voice.
- [ ] Use present tense.
- [ ] Use second person ("you"). No "we" or "I".
3. Check word choice
- [ ] Replace forbidden terms: "e.g.", "i.e.", "etc.", "should", "would",
"could", "via", "may".
- [ ] Use Oxford comma and American spelling.
4. Check style of headings
- [ ] Use Sentence case for headings.
- If you change a heading, add an id after the heading like this:
"## Configure the project {: #project-configuration }"
- [ ] Put a blank line after all headings.
5. Check style of lists
- [ ] Numbered lists MUST use
1.for every item to allow easy reordering. - [ ] How-to sections must have active voice in headings.
- No: "## Project Configuration"
- Yes: "## Configure the project"
6. Use less words in sections with steps
- [ ] Ask the user if they would like the steps to be more concise.
If yes, update the steps to be brief. Keep it short, simple, and
accurate.
Other skills for the same job
different authors, same section of the catalogue
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementing any feature or bugfix, before writing implementation code
Use when you have a spec or requirements for a multi-step task, before touching code
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
| Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
Official Opentrons Protocol API for OT-2 and Flex robots. Use when writing protocols specifically for Opentrons hardware with full access to Protocol API v2 features. Best for production Opentrons protocols, official API compatibility. For multi-vendor automation or broader equipment control use pylabrobot.
How to use it
Take flutter/proofread-markdown from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.