Whitepaper Bare Section Prose Filler
FlorianBruniaux/claude-code-ultimate-guide
Adds two to four sentences of intro prose before each bare heading in the French and English whitepapers, splitting the work across nine parallel agents.
Proofreads English technical writing for typos, grammar slips, punctuation, terminology consistency, jargon, and structure; returns an itemized Original → Suggestion → Reason list without rewriting…
Install Tech Writing Proofread
$ npx skills add aiskillstore/marketplace --skill tech-writing-proofread -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install aiskillstore/marketplace tech-writing-proofread --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/aiskillstore/marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/alapha888/tech-writing-proofread .claude/skills/tech-writing-proofread && 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 "tech-writing-proofread" agent skill from https://github.com/aiskillstore/marketplace/tree/main/skills/alapha888/tech-writing-proofread into .claude/skills/tech-writing-proofread/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tech-writing-proofread", 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/aiskillstore/marketplace/tree/main/skills/alapha888/tech-writing-proofreadType 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 aiskillstore/marketplace --skill tech-writing-proofread -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install aiskillstore/marketplace tech-writing-proofread --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aiskillstore/marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/alapha888/tech-writing-proofread .agents/skills/tech-writing-proofread && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "tech-writing-proofread" agent skill from https://github.com/aiskillstore/marketplace/tree/main/skills/alapha888/tech-writing-proofread into .agents/skills/tech-writing-proofread/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tech-writing-proofread", 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 aiskillstore/marketplace --skill tech-writing-proofread -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install aiskillstore/marketplace tech-writing-proofread --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aiskillstore/marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/alapha888/tech-writing-proofread .cursor/skills/tech-writing-proofread && 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 "tech-writing-proofread" agent skill from https://github.com/aiskillstore/marketplace/tree/main/skills/alapha888/tech-writing-proofread into .cursor/skills/tech-writing-proofread/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tech-writing-proofread", 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/aiskillstore/marketplace.git --path skills/alapha888/tech-writing-proofread--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 aiskillstore/marketplace --skill tech-writing-proofread -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install aiskillstore/marketplace tech-writing-proofread --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aiskillstore/marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/alapha888/tech-writing-proofread .gemini/skills/tech-writing-proofread && 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 "tech-writing-proofread" agent skill from https://github.com/aiskillstore/marketplace/tree/main/skills/alapha888/tech-writing-proofread into .gemini/skills/tech-writing-proofread/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tech-writing-proofread", 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 aiskillstore/marketplace tech-writing-proofreadInstalls 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 aiskillstore/marketplace --skill tech-writing-proofread -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/aiskillstore/marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/alapha888/tech-writing-proofread .github/skills/tech-writing-proofread && 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 "tech-writing-proofread" agent skill from https://github.com/aiskillstore/marketplace/tree/main/skills/alapha888/tech-writing-proofread into .github/skills/tech-writing-proofread/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tech-writing-proofread", 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 aiskillstore/marketplace --skill tech-writing-proofread -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install aiskillstore/marketplace tech-writing-proofread --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aiskillstore/marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/alapha888/tech-writing-proofread .opencode/skills/tech-writing-proofread && 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 "tech-writing-proofread" agent skill from https://github.com/aiskillstore/marketplace/tree/main/skills/alapha888/tech-writing-proofread into .opencode/skills/tech-writing-proofread/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tech-writing-proofread", 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
tech-writing-proofread- GitHub stars
- 430
- Used in
- 2 other repos
- Token cost
- ~1k tokens
- SKILL.md length
- 436 words
- Files
- 2
- Skills in repo
- 1,085
- Repo updated
- First seen
- Licence
- MIT
At a glance
Proofreads English technical writing for typos, grammar slips, punctuation, terminology consistency, jargon, and structure; returns an itemized Original → Suggestion → Reason list without rewriting…
- Works in 5 steps: Read for tone first: Read the whole… → Build a terminology list: Scan for key… → Check paragraph by paragraph, but only… → …
- The user asks to proofread
- SKILL.md covers Workflow, Rules, Minimal example and Anti-patterns
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Tech Writing Proofread is an agent skill from aiskillstore/marketplace. Proofreads English technical writing for typos, grammar slips, punctuation, terminology consistency, jargon, and structure; returns an itemized Original → Suggestion → Reason list without rewriting the whole document. Use when the user asks to proofread, polish, or review an English technical doc, README, or blog draft.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `skill-report.json`).
It sits in Writing & Content, covering Copy editing and proofreading and Technical writing. The repository describes itself as: Security-audited skills for Claude, Codex & Claude Code. One-click install, quality verified. The licence is MIT.
When your agent uses it
- The user asks to proofread
- Review an English technical doc
Example prompts
- “Use the tech-writing-proofread skill to proofread English technical writing for typos, grammar slips, punctuation, terminology consistency, jargon…”
- “/tech-writing-proofread”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Read for tone first: Read the whole document and identify its type (tutorial / API reference / blog post / README). Tutorials tolerate a…
- Build a terminology list: Scan for key terms (e.g. "callback" vs "callback function", "sign in" vs "log in") and check whether one concept…
- Check paragraph by paragraph, but only for these six categories — do not drift into "is this paragraph well written"
- Output the checklist: list items as "Original → Suggestion → Reason", with line numbers or short quotes. Mark uncertain items [verify]…
- Close with statistics: N items total, of which typos x, grammar y, terminology z, style w — so the author sees the distribution at a glance.
What it can do on your machine
Read from SKILL.md and the folder at commit 4ac52da. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Tech Writing Proofread loads about 1k tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 436 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
The full file from aiskillstore/marketplace at commit 4ac52da, republished under its MIT licence (© aiskillstore). 436 words, ~1,042 tokens.
Download SKILL.mdSave it as
.claude/skills/tech-writing-proofread/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- tech-writing-proofread
- description
- Proofreads English technical writing for typos, grammar slips, punctuation, terminology consistency, jargon, and structure; returns an itemized Original → Suggestion → Reason list without rewriting the whole document. Use when the user asks to proofread, polish, or review an English technical doc, README, or blog draft.
- license
- MIT
Technical Writing Proofreading
Take an English technical document from "understandable" to "publishable." Proofread only — never rewrite content. Flag suspected factual errors; do not silently fix them.
Workflow
- Read for tone first: Read the whole document and identify its type (tutorial / API reference / blog post / README). Tutorials tolerate a conversational voice; API references must be precise.
- Build a terminology list: Scan for key terms (e.g. "callback" vs "callback function", "sign in" vs "log in") and check whether one concept is named several ways. Standardize on the most frequent form and note it in the checklist.
- Check paragraph by paragraph, but only for these six categories — do not drift into "is this paragraph well written":
- Typos and spelling: transposed letters, doubled words ("the the"), commonly confused pairs ("affect/effect", "its/it's", "complement/compliment").
- Grammar: subject-verb agreement, verb tense consistency within a procedure, dangling modifiers, missing articles before singular countable nouns.
- Punctuation: consistent serial (Oxford) comma usage; hyphens in compound adjectives ("command-line tool"); no double spaces after periods; consistent use of em dashes vs parentheses.
- Inline code and proper nouns: inline code, commands, file names, and paths in backticks; proper nouns in their official casing (
GitHub, notgithub;JavaScript, notJavascript). - Sentence style: prefer active voice ("The system calls the function" over "The function is called by the system"); cut filler ("basically", "simply", "just", "very"); one idea per sentence.
- Structure: headings in parallel form; lists use parallel items; steps in a procedure are imperative and numbered; acronyms are expanded on first use.
- Output the checklist: list items as "Original → Suggestion → Reason", with line numbers or short quotes. Mark uncertain items
[verify]instead of forcing a change. - Close with statistics: N items total, of which typos x, grammar y, terminology z, style w — so the author sees the distribution at a glance.
Show full SKILL.md (136 more words)Show less
Rules
- Fix language, not facts. A suspected factual error becomes
[verify] This contradicts the usual definition — please confirm, never a silent "correction." - Do not rewrite whole paragraphs. Even a wordy paragraph gets only specific, fixable sentences flagged; keep the author's voice.
- One pass only. Do not keep "polishing another round" — the deliverable is a "no-defects" checklist, not a perfect text.
Minimal example
Input snippet:
This function will be called by the system after the data is ready, you can use it to basically handle the registration of the callback, the timeout is 5 s, examples on github can be referenced.Output checklist:
1. [Style] "will be called by the system" → "the system calls" (passive → active)
2. [Style] "basically handle" → "handle" (cut filler word)
3. [Terminology] "callback" — if written elsewhere as "callback function", unify on one form (most frequent wins)
4. [Grammar] run-on sentence: split after "ready." into two sentences
5. [Proper noun] "github" → "GitHub" (official casing)
Statistics: 5 items — style 2, terminology 1, grammar 1, proper noun 1.Anti-patterns
- ❌ Turning proofreading into rewriting: tearing a paragraph down so the author's voice and structure are lost.
- ❌ Hallucinated "corrections": changing an uncertain technical statement as if it were a typo, introducing a factual error.
- ❌ Typos-only checks: inconsistent terminology and sloppy structure are the real defects in technical docs.
- ❌ Endless iteration: the user says "polish it once more" and it never ends — the deliverable is the checklist, not a perfect text.
© aiskillstore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in skills/alapha888/tech-writing-proofread of aiskillstore/marketplace.
- SKILL.md
- skill-report.json
Open the folder on GitHubat commit 4ac52da
Used in 2 other repositories
We found 6 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in aiskillstore/marketplace, which our catalogue first saw on October 7, 2026.
- sickn33/agentic-awesome-skillsskills/tech-writing-proofreadplugins/agentic-awesome-skills/skills/tech-writing-proofread+1 more
- lingxling/awesome-skills-cnantigravity-awesome-skills/skills/tech-writing-proofreadantigravity-awesome-skills/plugins/agentic-awesome-skills/skills/tech-writing-proofread+1 more
Compare with similar skills
Tech Writing Proofread 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 |
|---|---|---|---|---|---|---|
| Tech Writing Proofread this skillaiskillstore/marketplace | 430 | 2 repos | ~1k | Automated safety check: Pass | MIT | |
| Whitepaper Bare Section Prose FillerFlorianBruniaux/claude-code-ultimate-guide | 6.1k | — | ~1.5k | Automated safety check: Pass | CC-BY-SA-4.0 | |
| Academic Prose De-AI Editorheise3/academic-deai | 209 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Chinese Technical Writingleter/zh-tech-writing | 332 | — | ~656 | Automated safety check: Pass | MIT | |
| Chinese Documentation Style GuidejnMetaCode/superpowers-zh | 8.3k | — | ~1.6k | Automated safety check: Pass | MIT | |
| evlog Content Writingevloghq/evlog | 1.9k | — | ~2.9k | Automated safety check: Pass | MIT |
Similar skills
Academic Prose De-AI Editor
heise3/academic-deai
Edits Chinese or English scholarly writing for natural phrasing and removes AI-sounding templated structure, while keeping claims, citations and author voice intact.
Chinese Technical Writing
leter/zh-tech-writing
Sets writing rules for Chinese technical docs: short plain sentences, consistent typography and a checklist for removing AI-sounding filler.
Chinese Documentation Style Guide
jnMetaCode/superpowers-zh
Reference rules for typesetting Chinese technical documents: spacing around English and digits, punctuation, term handling, bilingual API docs and README layout.
evlog Content Writing
evloghq/evlog
Rules for writing and reviewing evlog docs, blog posts, READMEs, skills and AGENTS.md files, with separate review and rewrite roles, a house voice and a catalog of AI-sounding tells.
Declauding
oaustegard/claude-skills
Rewrites model-sounding prose into plain technical writing and checks that every claim survives, for PR text, docs, commit messages and similar drafts.
More from aiskillstore/marketplace
All 1,085 skills in this repoCode Stats
aiskillstore/marketplace
Analyze codebase with tokei (fast line counts by language) and difft (semantic AST-aware diffs).
Data Processing
aiskillstore/marketplace
Process JSON with jq and YAML/TOML with yq. An agent skill from aiskillstore/marketplace.
Doc Scanner
aiskillstore/marketplace
Scans for project documentation files (AGENTS.md, CLAUDE.md, GEMINI.md, COPILOT.md, CURSOR.md, WARP.md, and 15+ other formats) and synthesizes guidance.
File Search
aiskillstore/marketplace
Modern file and content search using fd, ripgrep (rg), and fzf.
Find Replace
aiskillstore/marketplace
Modern find-and-replace using sd (simpler than sed) and batch replacement patterns.
Investigating Codebases
aiskillstore/marketplace
Automatically activated when user asks how something works, wants to understand unfamiliar code, needs to explore a new codebase, or asks questions like "where is X implemented?", "how does Y…
Related
Categories
Questions about Tech Writing Proofread
What does Tech Writing Proofread do?
Proofreads English technical writing for typos, grammar slips, punctuation, terminology consistency, jargon, and structure; returns an itemized Original → Suggestion → Reason list without rewriting…. Tech Writing Proofread is an agent skill from aiskillstore/marketplace. Proofreads English technical writing for typos, grammar slips, punctuation, terminology consistency, jargon, and structure; returns an itemized Original → Suggestion → Reason list without rewriting the whole document.
When should I use Tech Writing Proofread?
Tech Writing Proofread fits situations like: the user asks to proofread; review an English technical doc.
How do I install Tech Writing Proofread in Claude Code?
Run `npx skills add aiskillstore/marketplace --skill tech-writing-proofread -a claude-code`. Or copy the skill folder (skills/alapha888/tech-writing-proofread in aiskillstore/marketplace) into .claude/skills/tech-writing-proofread in your project. Claude Code loads it when a task matches its description.
How do I install Tech Writing Proofread in Codex?
Run `npx skills add aiskillstore/marketplace --skill tech-writing-proofread -a codex`. Or copy the skill folder (skills/alapha888/tech-writing-proofread in aiskillstore/marketplace) into .agents/skills/tech-writing-proofread in your project. Codex loads it when a task matches its description.
Can I use Tech Writing Proofread 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 aiskillstore/marketplace --skill tech-writing-proofread -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tech-writing-proofread, .gemini/skills/tech-writing-proofread, .github/skills/tech-writing-proofread and .opencode/skills/tech-writing-proofread in your project.
What does Tech Writing Proofread need to run?
SKILL.md names no scripts, command-line tools or credentials: Tech Writing Proofread is instructions for the agent only.
Does Tech Writing Proofread 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 Tech Writing Proofread 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 Tech Writing Proofread use?
Tech Writing Proofread is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Tech Writing Proofread use?
About 1k tokens (SKILL.md is roughly 4.2k 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 Tech Writing Proofread?
Skills that share tags, products or a category with Tech Writing Proofread: Whitepaper Bare Section Prose Filler (FlorianBruniaux/claude-code-ultimate-guide, 6.1k stars), Academic Prose De-AI Editor (heise3/academic-deai, 209 stars), Chinese Technical Writing (leter/zh-tech-writing, 332 stars) and Chinese Documentation Style Guide (jnMetaCode/superpowers-zh, 8.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Tech Writing Proofread?
aiskillstore (a GitHub organization) maintains it in aiskillstore/marketplace, which has 430 GitHub stars. The repository holds 1,085 skills in this directory. The repository was last updated on October 7, 2026.
Source: aiskillstore/marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.