Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

Get Started Free →

Documentation Review Skill · microck | DecimalAI

documentationby microck

Documentation Review Skill

microck/docs-review

Source microck/ordinary-claude-skills ↗License NOASSERTION

Review documentation changes for compliance with the Metabase writing style guide.

SkillScore95Maintained

Automatic

Doc Ops pack

Last verified 8/21/2026

What it changes

Passed 20 of 21 test cases with the skill, and 13 of 21 without it.

Without skill64%

With skill95%

Checks it passed that the model alone missed

The review flags 'users' as a term to replace.
The review suggests replacing 'users' with 'people'.
The submission specifies using the COMMENT review event type.

and 6 more in the full report

7 fixed14 passed either way1 still failing0 broke

Pass-rate lift: +32 pp
Tokens: +73%
Agent turns: 0%
Response time: -34%

Model gemini-3.6-flashMeasured 8/21/2026v121 of 22 cases passed with skill · 21 comparable

Tokens, turns and time describe resource use, not a dollar price.

Use this skill

Save it into your project's skills folder. Claude Code picks it up in its next session.

curl -fsSL --create-dirs -o .claude/skills/microck-docs-review/SKILL.md https://app.decimal.ai/s/microck-docs-review/SKILL.md

Want it pinned and updatable? pip install "decimalai>=0.15", then decimalai skills add microck-docs-review, and start Claude Code with claude --plugin-dir "$(git rev-parse --show-toplevel)/.agents"

1 · One-time — install the CLI (docs ↗)

pip install "decimalai>=0.15"

2 · Get the skill — writes .agents/skills/microck-docs-review/ and pins it in .decimal/skills.lock

decimalai skills add microck-docs-review

No CLI? Get the same file — curl · raw file

curl -fsSL --create-dirs -o .claude/skills/microck-docs-review/SKILL.md https://app.decimal.ai/s/microck-docs-review/SKILL.md

Raw file: /s/microck-docs-review/SKILL.md ↗ · machine-readable summary at /s/microck-docs-review.json ↗

Safety checks: 3 of 3 passed

Code scan CleanIntent PassedContent Clean

See it in action

One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.

1 of 7

Prompt

When finalizing a pending GitHub pull request review for documentation, which event type should be passed to the submit tool, and what value should be provided for the review body text parameter?

What was checked, without and with the skill
Checked	Without skill	With skill
The submission specifies using the COMMENT review event type.	Missed	Passed
The submission specifies omitting the review summary body parameter.	Missed	Passed

case-11 · gemini-3.6-flash · 8/21/2026 · answers are capped and redacted

What's inside

The instructions your model reads when the skill loads.

SKILL.md162 linessingle file

Documentation Review Skill

@./../_shared/metabase-style-guide.md

Review mode detection

IMPORTANT: Before starting the review, determine which mode to use:

PR review mode: If the mcp__github__create_pending_pull_request_review tool is available, you are reviewing a GitHub PR
- Use the pending review workflow to post all issues as one cohesive review
- Follow the workflow steps in "PR review mode format" below
Local review mode: If the MCP tool is NOT available, output issues in the conversation
- Format all issues in a numbered markdown list (as described in "Feedback format" below)

Review process

Detect review mode - Check if mcp__github__create_pending_pull_request_review is available
Read the changes through once to understand intent
Check all issues that violate style guide or significantly impact readability
Only flag issues worth mentioning - if it won't make a material difference to the reader, skip it
REQUIRED: Number ALL feedback sequentially - Start from Issue 1 and increment for each issue found

Review checklist

Run through the diff looking for these issues:

Tone and voice:

Formal/corporate language ("utilize" not "use", "offerings", etc.)
"Users" instead of "people" or "companies"
Excessive exclamation points or overly peppy tone
Telling readers something is cool instead of showing them

Structure and clarity:

Important information buried instead of leading
Verbose text that adds little value
Paragraphs without clear purpose
Vague headings that don't convey the point

Track record

Benchmark

20 / 21

test cases passed, vs 13 / 21 without

Adoption

Users: 1
Times used: 13

Safety and source details

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v4 — 8/3/2026

View 15 scanner checks

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

microck / ordinary-claude-skills

skills_all/docs-review/SKILL.md

View on GitHub ↗

License NOASSERTIONImported 8/3/2026Version v1

Other skills for the same job

Published skills whose descriptions closely match this one, with their headline benchmark lift.

More skills from the same source and nearby in the registry, with their headline benchmark lift.

Ready to supercharge your AI agents?

See it in action

What's inside

Documentation Review Skill

Review mode detection

Review process

Review checklist

Track record

Benchmark

Adoption

SkillSafety

Source

Other skills for the same job

Related skills