Agent skill

Review Prose Fix

by tbhb in tbhb/vale-ai-tells

Reviews what a prose fix did to a document. An agent skill from tbhb/vale-ai-tells.

Apache-2.0Auto-check passedWriting & Content

Install Review Prose Fix

skills CLI
$ npx skills add tbhb/vale-ai-tells --skill review-prose-fix -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install tbhb/vale-ai-tells review-prose-fix --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/tbhb/vale-ai-tells.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/review-prose-fix .claude/skills/review-prose-fix && rm -rf skills-src

Use ~/.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/

Facts

Skill name
review-prose-fix
GitHub stars
117
Token cost
~1.2k tokens
SKILL.md length
674 words
Files
2
Skills in repo
27
Repo updated
First seen
Licence
Apache-2.0

At a glance

Reviews what a prose fix did to a document. An agent skill from tbhb/vale-ai-tells.

  • Writing & Content work in your project
  • SKILL.md covers The repository, Gather the inputs, What to check and Sweep before you write the…, plus 1 more section
  • Calls bash

What it does

Review Prose Fix is an agent skill from tbhb/vale-ai-tells. Reviews what a prose fix did to a document. The fix-prose skill invokes this by name.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `tokens.json`).

It sits in Writing & Content. The repository describes itself as: In today's rapidly evolving landscape, vale-ai-tells is a comprehensive, cutting-edge Vale style package that empowers writers to seamlessly delve into the rich tapestry of AI…. The licence is Apache-2.0.

When your agent uses it

  • Writing & Content work in your project

Example prompts

  • “Use the review-prose-fix skill to review what a prose fix did to a document. An agent skill from tbhb/vale-ai-tells”
  • “/review-prose-fix”

What it can do on your machine

Read from SKILL.md and the folder at commit 4c7abc9. 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:

    • bash

    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

Review Prose Fix loads about 1.2k tokens when it runs. Until then it costs about 26 tokens; SKILL.md has 674 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~26
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

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 tbhb/vale-ai-tells at commit 4c7abc9, republished under its Apache-2.0 licence (© tbhb). 674 words, ~1,156 tokens.

Download SKILL.mdSave it as .claude/skills/review-prose-fix/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
review-prose-fix
description
Reviews what a prose fix did to a document. The fix-prose skill invokes this by name.
license
Apache-2.0
context
fork
agent
Explore
background
false

Review a prose fix

Judge what a copy edit did to a document. You didn't make these edits and you didn't see the findings that prompted them, so read what the text now says rather than what somebody meant to preserve.

The gates already ran. Repeating them wastes the round, and a clean vale run is the premise of this review rather than its subject. Your subject is everything vale can't score.

The repository

$ARGUMENTS

Treat the first word as the repository. A second word, when present, is the target file. Bind them once:

bash
REPO="${ARGUMENTS%% *}"

Gather the inputs

From $REPO, run these before judging anything:

  • bash .claude/skills/fix-prose/scripts/check-suppressions.sh --diff for what changed
  • bash .claude/skills/fix-prose/scripts/check-suppressions.sh --verify for edits outside the target
  • cat the target for the result in one piece

The diff is the review. Where it comes back empty, the fixer changed nothing, and that's a finding unless its report said so.

Where the caller passed the fixer's report, read it too. A claim there that the diff doesn't support is a finding in itself.

What to check

Every finding names the exact text and the correction.

Meaning

The document says what it said before.

  • Flag any claim that changed. A dropped qualifier, an added hedge, or an absolute turned conditional edits the argument while looking like a reword.
  • Flag any number, path, identifier, filename, flag, or proper noun that differs. These are never a style matter.
  • Flag precision traded for a clean run. Replacing a dependency name with the fuzzing dependency clears a spelling rule and costs the reader the fact.
  • Flag a clause or sentence that went missing. Deleting text clears a distributional rule and takes content with it.
Language the linter can't score

The rule set names a few figurative verbs and misses the category around them.

  • Flag metaphor, idiom, and personification that the edit introduced. Rules don't fight, checks don't bite, and a document doesn't sail anywhere.
  • Flag a sentence that got longer without getting clearer. A reword that doubles a sentence to avoid a rule trades a measured problem for one nothing measures.
  • Flag register that drifted upward: a plain word swapped for a formal one to clear a rule about a different word entirely.
  • Flag anything the document didn't say before. Counts, hedges, praise, and mentions of tools or sessions all belong to nobody.
Show full SKILL.md (286 more words)Show less
The unresolved list
  • Flag a finding reported as unresolvable that a plain reword clears. Say what the reword is.
  • Accept an unresolvable finding that holds up. A rule misfiring on correct text is a real outcome, and demanding a fix for one is how documents get worse.
Silenced checkers

The mechanical check already reports this, so read its output rather than re-deriving it. A linter-config-changed or suppression-comment finding there is automatically CHANGES REQUIRED.

Sweep before you write the verdict

One editing pass produces one class of damage in more than one place at once, because the writer cleared a rule the same way everywhere it fired. Take each finding you have and read the rest of the diff for the same damage. A pronoun the reorder stranded, a clause a reword reattached to the wrong thing, an identifier paraphrased away, a parallel the edit broke on one item and kept on the next. Where the diff holds one, look for the second.

Report every instance. Handing back one at a time costs a fixing round and a review round to say what this verdict could have said, and the writer only sweeps the list you give it.

What to return

Return the verdict block and stop there. Skip the preamble, the summary of the diff, and the praise. Write nothing to disk, and don't edit the document to make it pass. Reporting the finding is the job.

text
VERDICT: PASS

or

text
VERDICT: CHANGES REQUIRED

1. [meaning] <what is wrong>
   text: <the exact offending text>
   fix:  <the specific correction>

2. [language] <what is wrong>
   text: <the exact offending text>
   fix:  <the specific correction>

Tag each finding meaning, language, unresolved, or suppression.

Return PASS when the edit holds up. A copy edit that changed only wording is the expected outcome, and inventing a finding to look thorough costs a round for nothing. Report only what you can point at in the diff.

© tbhb, Apache-2.0. 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 .claude/skills/review-prose-fix of tbhb/vale-ai-tells.

  • SKILL.md
  • tokens.json

Open the folder on GitHubat commit 4c7abc9

Compare with similar skills

Review Prose Fix 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.

Review Prose Fix compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Review Prose Fix this skilltbhb/vale-ai-tells117—~1.2kAutomated safety check: PassApache-2.0
Socialcoreyhaines31/marketingskills54k4 repos~4.5kAutomated safety check: PassMIT
HumanizerAzure-Samples/interview-coach-agent-framework17338 repos~5.8kAutomated safety check: PassMIT
Avoid AI Writingconorbronsdon/avoid-ai-writing4.9k3 repos~8.1kAutomated safety check: PassMIT
JavaScript Concept Fact Checkerleonardomso/33-js-concepts67k1 repos~5kAutomated safety check: PassMIT
User-Facing Text Cleanupguillaumemeyer/watermarks-remover24k—~3.5kAutomated safety check: PassMIT

Similar skills

  • Social

    coreyhaines31/marketingskills

    When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, or Facebook, or wants to do social listening and engagement triage.

    54k GitHub starsUsed in 4 repos~4.5k tokens
    Writing & ContentAuto-check passed
  • Humanizer

    Azure-Samples/interview-coach-agent-framework

    Official

    Remove signs of AI-generated writing from text. An agent skill from Azure-Samples/interview-coach-agent-framework.

    173 GitHub starsUsed in 38 repos~5.8k tokens
    Writing & ContentAuto-check passed
  • Avoid AI Writing

    conorbronsdon/avoid-ai-writing

    Audit and rewrite content to remove AI writing patterns ("AI-isms").

    4.9k GitHub starsUsed in 3 repos~8.1k tokens
    Writing & ContentAuto-check passed
  • JavaScript Concept Fact Checker

    leonardomso/33-js-concepts

    Verifies the technical accuracy of JavaScript concept pages by checking code examples, MDN and ECMAScript claims and external links through a five-phase method.

    67k GitHub starsUsed in 1 repo~5k tokens
    Writing & ContentAuto-check passed
  • User-Facing Text Cleanup

    guillaumemeyer/watermarks-remover

    Audits prose for invisible Unicode characters and rewrites it while keeping facts, citations, code and required disclosures unchanged and the writer's voice intact.

    24k GitHub stars~3.5k tokensUpdated 2 days ago
    Writing & ContentAuto-check passed
  • Install Anti Slop

    trycompai/crm

    Install and configure the anti-slop Oxlint plugin in a local TypeScript or JavaScript repository.

    11k GitHub starsUsed in 1 repo~881 tokens
    Writing & ContentAuto-check passed

More from tbhb/vale-ai-tells

All 27 skills in this repo
  • Analyze Session

    tbhb/vale-ai-tells

    Query a Claude Code transcript without reading it into context, then write the retrospective to disk so it remains available after the session ends.

    117 GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed
  • Codex Analyze Session

    tbhb/vale-ai-tells

    Query a Codex transcript without reading it into context, then write the retrospective to disk so it remains available after the session ends.

    117 GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed
  • Codex Fix PR

    tbhb/vale-ai-tells

    Diagnose failing pull request checks, reproduce them locally, make focused fixes, commit them through codex-commit, and refresh the published description when needed.

    117 GitHub stars~575 tokensUpdated yesterday
    Auto-check passed
  • Codex Merge PR

    tbhb/vale-ai-tells

    Squash merge a pull request. An agent skill from tbhb/vale-ai-tells.

    117 GitHub stars~3k tokensUpdated yesterday
    Auto-check passed
  • Codex PR

    tbhb/vale-ai-tells

    Open or update a pull request for the current branch with an independently drafted and reviewed PRAGENTDESC.md.

    117 GitHub stars~846 tokensUpdated yesterday
    Auto-check passed
  • Codex Rebase

    tbhb/vale-ai-tells

    Replay the current branch onto its base and establish that the result is sound.

    117 GitHub stars~2k tokensUpdated yesterday
    Auto-check passed

Questions about Review Prose Fix

What does Review Prose Fix do?

Reviews what a prose fix did to a document. An agent skill from tbhb/vale-ai-tells. Review Prose Fix is an agent skill from tbhb/vale-ai-tells. Reviews what a prose fix did to a document.

When should I use Review Prose Fix?

Review Prose Fix fits situations like: writing & Content work in your project.

How do I install Review Prose Fix in Claude Code?

Run `npx skills add tbhb/vale-ai-tells --skill review-prose-fix -a claude-code`. Or copy the skill folder (.claude/skills/review-prose-fix in tbhb/vale-ai-tells) into .claude/skills/review-prose-fix in your project. Claude Code loads it when a task matches its description.

How do I install Review Prose Fix in Codex?

Run `npx skills add tbhb/vale-ai-tells --skill review-prose-fix -a codex`. Or copy the skill folder (.claude/skills/review-prose-fix in tbhb/vale-ai-tells) into .agents/skills/review-prose-fix in your project. Codex loads it when a task matches its description.

Can I use Review Prose Fix 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 tbhb/vale-ai-tells --skill review-prose-fix -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/review-prose-fix, .gemini/skills/review-prose-fix, .github/skills/review-prose-fix and .opencode/skills/review-prose-fix in your project.

What does Review Prose Fix need to run?

Going by SKILL.md and its folder, Review Prose Fix needs the command-line tools its instructions call (bash).

Does Review Prose Fix 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 Review Prose Fix 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 Review Prose Fix use?

Review Prose Fix is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Review Prose Fix use?

About 1.2k tokens (SKILL.md is roughly 4.6k 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 Review Prose Fix?

Skills that share tags, products or a category with Review Prose Fix: Social (coreyhaines31/marketingskills, 54k stars), Humanizer (Azure-Samples/interview-coach-agent-framework, 173 stars), Avoid AI Writing (conorbronsdon/avoid-ai-writing, 4.9k stars) and JavaScript Concept Fact Checker (leonardomso/33-js-concepts, 67k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Review Prose Fix?

tbhb (a GitHub user) maintains it in tbhb/vale-ai-tells, which has 117 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on October 9, 2026.

Source: tbhb/vale-ai-tells on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.