New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Review Verbosity

by pydantic in pydantic/monty

Rewrite excessively verbose comments and docstrings added by this branch, and delete tautologous ones.

OfficialMITAuto-check passedDevelopment

Install Review Verbosity

skills CLI
$ npx skills add pydantic/monty --skill review-verbosity -a claude-code

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

GitHub CLI
$ gh skill install pydantic/monty review-verbosity --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/pydantic/monty.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/review-verbosity .claude/skills/review-verbosity && 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-verbosity
GitHub stars
8.6k
Token cost
~494 tokens
SKILL.md length
232 words
Files
1
Skills in repo
9
Repo updated
First seen
Licence
MIT

At a glance

Rewrite excessively verbose comments and docstrings added by this branch, and delete tautologous ones.

  • Tasks that involve Technical documentation
  • Calls git and make

What it does

Review Verbosity is an agent skill from pydantic/monty, published by the product's own GitHub organization. Rewrite excessively verbose comments and docstrings added by this branch, and delete tautologous ones. Use after writing a feature to tighten up its comments; this skill edits code rather than only reporting.

Its SKILL.md is about 490 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 Development, covering Technical documentation. It works with Python. The repository describes itself as: A minimal, secure Python interpreter written in Rust for use by AI. The licence is MIT.

When your agent uses it

  • Tasks that involve Technical documentation

Example prompts

  • “/review-verbosity”

Requirements

  • Python 3

What it can do on your machine

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

    • git
    • make

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, 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

Review Verbosity loads about 494 tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 232 words of instructions outside code blocks.

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

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 pydantic/monty at commit b8f2955, republished under its MIT licence (© pydantic). 232 words, ~494 tokens.

Download SKILL.mdSave it as .claude/skills/review-verbosity/SKILL.md (or your agent's skills folder).
name
review-verbosity
description
Rewrite excessively verbose comments and docstrings added by this branch, and delete tautologous ones. Use after writing a feature to tighten up its comments; this skill edits code rather than only reporting.

Verbosity review

New comments and docstrings are usually too verbose. Rewrite them concisely. This skill edits — it doesn't just report.

bash
git diff --stat origin/main...HEAD   # which crates changed
git diff origin/main...HEAD

Dispatch one sub-agent per changed area — a crate, or any other group of changed files, so nothing outside crates/ is missed — then review their edits yourself. A single pass over a large diff won't be exhaustive. In every comment the branch touched:

  • Cut it down. Comments and field docstrings rarely over 3 lines, mostly 1; function and struct docstrings <= 5.
  • Delete tautology — restating what the code plainly says earns nothing.
  • Delete narration of the obvious, restated type signatures, how the code came to be, hedging.
  • Keep the motivation — why the code exists and its foot-guns are the valuable part. Don't cut real information to hit a line count.
  • Drop over-long examples. Public items only, <= 8 lines, and every one must run in tests — never ignore.
  • Fix what's out of date. A comment the branch made wrong gets corrected, not left.

Python docstrings are markdown: single backticks, never RST double-backticks.

Only touch what this branch added or changed, unless asked for a wider sweep. Don't change behaviour — if a comment is wrong because the code is wrong, say so rather than rewording it to match. Concision, not terseness: an unfollowable comment is worse than a long one.

bash
make format-rs && make lint-rs
git diff --stat   # format-rs is `cargo +nightly fmt --all` — check it touched only your files

Then report what you cut, by file, in a couple of lines — not a full inventory.

© pydantic, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/review-verbosity of pydantic/monty.

Open the folder on GitHubat commit b8f2955

Compare with similar skills

Review Verbosity 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 Verbosity compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Review Verbosity this skillpydantic/monty8.6k—~494Automated safety check: PassMIT
Adk Sample Creatorgoogle/adk-python22k—~1.3kAutomated safety check: PassApache-2.0
Crafting Effective Readmescumbucadev/cinemaempoa1465 repos~669Automated safety check: PassGPL-3.0
Acquire Codebase Knowledgegithub/awesome-copilot40k1 repos~2.3kAutomated safety check: PassMIT
Docs Conventionsflet-dev/flet17k—~1.6kAutomated safety check: PassApache-2.0
DDNS Provider DevelopmentNewFuture/DDNS4.7k—~558Automated safety check: PassMIT

Similar skills

  • Adk Sample Creator

    google/adk-python

    Official

    Creates a new sample agent in the ADK Python repository — the sample directory, its agent.py, and its README.md — following the conventions the existing samples already use.

    22k GitHub stars~1.3k tokensUpdated today
    DevelopmentAuto-check passed

  • Crafting Effective Readmes

    cumbucadev/cinemaempoa

    A skill your agent uses when writing or improving README files.

    146 GitHub starsUsed in 5 repos~669 tokens
    DevelopmentAuto-check passed

  • Acquire Codebase Knowledge

    github/awesome-copilot

    Official

    Maps an unfamiliar codebase into seven evidence-backed documents in docs/codebase/, using a scan script and templates, for onboarding or architecture write-ups.

    40k GitHub starsUsed in 1 repo~2.3k tokens
    DevelopmentAuto-check passed

  • Docs Conventions

    flet-dev/flet

    A skill your agent uses when writing or reviewing Flet documentation, including Python docstrings (Google style, reST roles, admonitions), Markdown docs (cross-references, images, code examples)…

    17k GitHub stars~1.6k tokensUpdated today
    DevelopmentAuto-check passed

  • DDNS Provider Development

    NewFuture/DDNS

    Adds or changes a DNS provider in the DDNS project while keeping its code, schemas, tests and Chinese and English docs consistent.

    4.7k GitHub stars~558 tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Mkdocs

    jeka-dev/jeka

    MkDocs documentation project reference covering CLI commands, mkdocs.yml configuration, Material theme setup, and plugin integration.

    176 GitHub stars~2k tokensUpdated 2 mo ago
    DevelopmentAuto-check passed

More from pydantic/monty

All 9 skills in this repo

  • Fix PR Comments

    pydantic/monty

    Official

    Read the review comments left by the known agent reviewers on the current PR, resolve and reply.

    8.6k GitHub stars~552 tokensUpdated today
    Auto-check passed

  • Python Playground

    pydantic/monty

    Official

    Run and test Python code in a dedicated playground directory.

    8.6k GitHub stars~424 tokensUpdated today
    Auto-check passed

  • Review General

    pydantic/monty

    Official

    Review the current branch against its merge base for bugs, CPython divergence, sandbox escapes, resource-limit escapes, performance regressions, verbose comments and missing ./limitations/ or docs/…

    8.6k GitHub stars~501 tokensUpdated today
    Auto-check passed

  • Review Security

    pydantic/monty

    Official

    Security review of the current branch against its merge base — sandbox escapes, memory errors, panics and resource-limit bypasses.

    8.6k GitHub stars~852 tokensUpdated today
    Auto-check passed

  • Writing Style

    pydantic/monty

    Official

    How to write prose that reads like human technical documentation rather than LLM output.

    8.6k GitHub stars~3.2k tokensUpdated today
    Auto-check passed

  • Review Usability

    pydantic/monty

    Official

    Check whether the common Python code an LLM would plausibly write still works on this branch, testing real cases in ./playground against CPython.

    8.6k GitHub stars~410 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Review Verbosity

What does Review Verbosity do?

Rewrite excessively verbose comments and docstrings added by this branch, and delete tautologous ones. Review Verbosity is an agent skill from pydantic/monty, published by the product's own GitHub organization. Rewrite excessively verbose comments and docstrings added by this branch, and delete tautologous ones.

When should I use Review Verbosity?

Review Verbosity fits situations like: tasks that involve Technical documentation.

How do I install Review Verbosity in Claude Code?

Run `npx skills add pydantic/monty --skill review-verbosity -a claude-code`. Or copy the skill folder (.agents/skills/review-verbosity in pydantic/monty) into .claude/skills/review-verbosity in your project. Claude Code loads it when a task matches its description.

How do I install Review Verbosity in Codex?

Run `npx skills add pydantic/monty --skill review-verbosity -a codex`. Or copy the skill folder (.agents/skills/review-verbosity in pydantic/monty) into .agents/skills/review-verbosity in your project. Codex loads it when a task matches its description.

Can I use Review Verbosity 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 pydantic/monty --skill review-verbosity -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-verbosity, .gemini/skills/review-verbosity, .github/skills/review-verbosity and .opencode/skills/review-verbosity in your project.

What does Review Verbosity need to run?

Going by SKILL.md and its folder, Review Verbosity needs the command-line tools its instructions call (git and make). Our summary lists: Python 3.

Does Review Verbosity access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Review Verbosity 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 Verbosity use?

Review Verbosity is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Review Verbosity use?

About 494 tokens (SKILL.md is roughly 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 Review Verbosity?

Skills that share tags, products or a category with Review Verbosity: Adk Sample Creator (google/adk-python, 22k stars), Crafting Effective Readmes (cumbucadev/cinemaempoa, 146 stars), Acquire Codebase Knowledge (github/awesome-copilot, 40k stars) and Docs Conventions (flet-dev/flet, 17k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Review Verbosity?

pydantic (a GitHub organization, an official publisher) maintains it in pydantic/monty, which has 8,611 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 9, 2026.

Source: pydantic/monty on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.