Adk Sample Creator
google/adk-python
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.
Reviews the accuracy and writing quality of documentation. An agent skill from mrinalwadhwa/fluent.
Install Review Documentation
$ npx skills add mrinalwadhwa/fluent --skill review-documentation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mrinalwadhwa/fluent review-documentation --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/mrinalwadhwa/fluent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/review-documentation .claude/skills/review-documentation && 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 "review-documentation" agent skill from https://github.com/mrinalwadhwa/fluent/tree/main/skills/review-documentation into .claude/skills/review-documentation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-documentation", 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/mrinalwadhwa/fluent/tree/main/skills/review-documentationType 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 mrinalwadhwa/fluent --skill review-documentation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mrinalwadhwa/fluent review-documentation --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mrinalwadhwa/fluent.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/review-documentation .agents/skills/review-documentation && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "review-documentation" agent skill from https://github.com/mrinalwadhwa/fluent/tree/main/skills/review-documentation into .agents/skills/review-documentation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-documentation", 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 mrinalwadhwa/fluent --skill review-documentation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mrinalwadhwa/fluent review-documentation --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mrinalwadhwa/fluent.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/review-documentation .cursor/skills/review-documentation && 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 "review-documentation" agent skill from https://github.com/mrinalwadhwa/fluent/tree/main/skills/review-documentation into .cursor/skills/review-documentation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-documentation", 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/mrinalwadhwa/fluent.git --path skills/review-documentation--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 mrinalwadhwa/fluent --skill review-documentation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mrinalwadhwa/fluent review-documentation --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mrinalwadhwa/fluent.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/review-documentation .gemini/skills/review-documentation && 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 "review-documentation" agent skill from https://github.com/mrinalwadhwa/fluent/tree/main/skills/review-documentation into .gemini/skills/review-documentation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-documentation", 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 mrinalwadhwa/fluent review-documentationInstalls 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 mrinalwadhwa/fluent --skill review-documentation -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mrinalwadhwa/fluent.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/review-documentation .github/skills/review-documentation && 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 "review-documentation" agent skill from https://github.com/mrinalwadhwa/fluent/tree/main/skills/review-documentation into .github/skills/review-documentation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-documentation", 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 mrinalwadhwa/fluent --skill review-documentation -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mrinalwadhwa/fluent review-documentation --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mrinalwadhwa/fluent.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/review-documentation .opencode/skills/review-documentation && 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 "review-documentation" agent skill from https://github.com/mrinalwadhwa/fluent/tree/main/skills/review-documentation into .opencode/skills/review-documentation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-documentation", 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
review-documentation- GitHub stars
- 111
- Token cost
- ~666 tokens
- SKILL.md length
- 340 words
- Files
- 2 (incl. references)
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Reviews the accuracy and writing quality of documentation. An agent skill from mrinalwadhwa/fluent.
- Works in 7 steps: Read the code under review to understand… → Read references/documentation.md for… → For each in-scope documentation file → …
- Reviewing doc changes in a diff
- SKILL.md covers Purpose, Scope and Method
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Review Documentation is an agent skill from mrinalwadhwa/fluent. Reviews the accuracy and writing quality of documentation. Use when reviewing doc changes in a diff, checking a new or edited page, or auditing the documentation of a codebase.
Its SKILL.md is about 670 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/documentation.md`).
It sits in Development, covering Technical documentation. The repository describes itself as: Fluent is a self-improving software factory. It autonomously turns your team's vision, ideas, bug reports, user feedback, production logs, and agent traces into working software. The licence is Apache-2.0.
When your agent uses it
- Reviewing doc changes in a diff
- Auditing the documentation of a codebase
Example prompts
- “Use the review-documentation skill to review the accuracy and writing quality of documentation. An agent skill from mrinalwadhwa/fluent”
- “/review-documentation”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Read the code under review to understand what needs documenting.
- Read references/documentation.md for writing-quality standards.
- For each in-scope documentation file
- Check the codebase for undocumented capabilities at every level — function docstrings, file-header comments, module READMEs…
- Check the documentation set as a whole for vocabulary drift — the same concept named differently across pages, or a doc term that…
- Check the candidate's commit messages over the provided commit range against the project's stated commit-message conventions in AGENTS.md…
- For each improvement, decide if it blocks shipping. Inaccurate paths, commands, or workflows that would break a reader's task typically…
What it can do on your machine
Read from SKILL.md and the folder at commit 6875b40. 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
Review Documentation loads about 666 tokens when it runs, and up to ~675 if it reads all its reference files. Until then it costs about 49 tokens; SKILL.md has 340 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 mrinalwadhwa/fluent at commit 6875b40, republished under its Apache-2.0 licence (© mrinalwadhwa). 340 words, ~666 tokens.
Download SKILL.mdSave it as
.claude/skills/review-documentation/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- review-documentation
- description
- Reviews the accuracy and writing quality of documentation. Use when reviewing doc changes in a diff, checking a new or edited page, or auditing the documentation of a codebase.
Purpose
Decide whether the code under review has documentation at every level — function docstrings, file-header comments, module READMEs, codebase-level docs, and user-facing pages. Identify code that lacks documentation, and existing docs that are inaccurate, unclear, or poorly organized.
Scope
The invoking layer decides what's in scope. For a diff-scoped review, that's the code and documentation changed in the diff. For a full-codebase audit, that's the entire codebase and its documentation. Check the documentation for accuracy, writing quality, and vocabulary consistency, and check the code for documentation that should exist but doesn't.
Method
Read the code under review to understand what needs documenting.
Read
references/documentation.mdfor writing-quality standards.For each in-scope documentation file:
- Read it alongside the code it describes.
- Check accuracy against the code.
- Evaluate writing quality against the standards.
- Identify improvements.
Check the codebase for undocumented capabilities at every level — function docstrings, file-header comments, module READMEs, codebase-level architecture and contributing docs, and user-facing documentation. Skip when the code speaks for itself; not every function needs a docstring.
Check the documentation set as a whole for vocabulary drift — the same concept named differently across pages, or a doc term that conflicts with what the code, tests, or user-facing surface calls it.
Check the candidate's commit messages over the provided commit range against the project's stated commit-message conventions in
AGENTS.mdorCLAUDE.md. Treat commit-message presentation as advice when a convention concerns subject length or style, body presence, body-line length or wrapping, body formatting, or literal\ntext. Do not emit a finding or failing verdict solely for presentation advice. Continue to flag invalid history, identity, encoding, or attribution, including prohibitedCo-Authored-Bytrailers. If the project states no commit conventions, skip this step — do not impose conventions the project did not state.For each improvement, decide if it blocks shipping. Inaccurate paths, commands, or workflows that would break a reader's task typically block. Vague phrasing, minor AI tells, and small clarity nits typically don't.
The invoking layer may add checks in addition to those above.
© mrinalwadhwa, 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 (references) in skills/review-documentation of mrinalwadhwa/fluent.
- SKILL.md
- references/documentation.md
Open the folder on GitHubat commit 6875b40
Compare with similar skills
Review Documentation 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 |
|---|---|---|---|---|---|---|
| Review Documentation this skillmrinalwadhwa/fluent | 111 | — | ~666 | Automated safety check: Pass | Apache-2.0 | |
| Adk Sample Creatorgoogle/adk-python | 22k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Doc-Code Sync Checkfancyboi999/open-tag | 203 | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Typescript Styletjx666/vscode-mcp | 105 | — | ~961 | Automated safety check: Pass | Custom licence | |
| Docs UpdateJayFarei/opentraces | 100 | — | ~4.6k | Automated safety check: Pass | Custom licence | |
| Interactive Implementation Plannerjumppad-labs/jumppad | 263 | — | ~5.6k | Automated safety check: Warn | MPL-2.0 |
Similar skills
- Official
Doc-Code Sync Check
fancyboi999/open-tag
Reconciles documentation with code at the end of a change or as a periodic audit, following a repo rule that code changes and doc changes land in one commit.
Typescript Style
tjx666/vscode-mcp
TypeScript code style and repo conventions for VSCode MCP — inference vs explicit types, ESM import suffixes, zod schema contracts, async VSCode/Node APIs, JSON-safe IPC results, JSDoc for public…
Docs Update
JayFarei/opentraces
Synchronize all documentation surfaces after code changes. An agent skill from JayFarei/opentraces.
Interactive Implementation Planner
jumppad-labs/jumppad
Builds detailed implementation plans through interactive questions, parallel research agents and template files for context, research, plan and tasks, from an issue or a plan name.
Documentation
extra-org/extra
Keep the repository's documentation accurate, honest, and synchronized with the code.
More from mrinalwadhwa/fluent
Review Skills
mrinalwadhwa/fluent
Reviews Agent Skills. An agent skill from mrinalwadhwa/fluent.
Review Architecture
mrinalwadhwa/fluent
Reviews the structural quality of code. An agent skill from mrinalwadhwa/fluent.
Review Behaviors
mrinalwadhwa/fluent
Reviews the quality and coherence of behavior statements. An agent skill from mrinalwadhwa/fluent.
Review Tests
mrinalwadhwa/fluent
Reviews test quality and coverage. An agent skill from mrinalwadhwa/fluent.
Related
Categories
Questions about Review Documentation
What does Review Documentation do?
Reviews the accuracy and writing quality of documentation. An agent skill from mrinalwadhwa/fluent. Review Documentation is an agent skill from mrinalwadhwa/fluent. Reviews the accuracy and writing quality of documentation.
When should I use Review Documentation?
Review Documentation fits situations like: reviewing doc changes in a diff; auditing the documentation of a codebase.
How do I install Review Documentation in Claude Code?
Run `npx skills add mrinalwadhwa/fluent --skill review-documentation -a claude-code`. Or copy the skill folder (skills/review-documentation in mrinalwadhwa/fluent) into .claude/skills/review-documentation in your project. Claude Code loads it when a task matches its description.
How do I install Review Documentation in Codex?
Run `npx skills add mrinalwadhwa/fluent --skill review-documentation -a codex`. Or copy the skill folder (skills/review-documentation in mrinalwadhwa/fluent) into .agents/skills/review-documentation in your project. Codex loads it when a task matches its description.
Can I use Review Documentation 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 mrinalwadhwa/fluent --skill review-documentation -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-documentation, .gemini/skills/review-documentation, .github/skills/review-documentation and .opencode/skills/review-documentation in your project.
What does Review Documentation need to run?
SKILL.md names no scripts, command-line tools or credentials: Review Documentation is instructions for the agent only.
Does Review Documentation 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 Documentation 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 Documentation use?
Review Documentation is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Review Documentation use?
About 666 tokens (SKILL.md is roughly 2.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 9 tokens, read only when the agent opens those files.
What are the alternatives to Review Documentation?
Skills that share tags, products or a category with Review Documentation: Adk Sample Creator (google/adk-python, 22k stars), Doc-Code Sync Check (fancyboi999/open-tag, 203 stars), Typescript Style (tjx666/vscode-mcp, 105 stars) and Docs Update (JayFarei/opentraces, 100 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Review Documentation?
mrinalwadhwa (a GitHub user) maintains it in mrinalwadhwa/fluent, which has 111 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 6, 2026.
Source: mrinalwadhwa/fluent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.