mcpbeat

Review Tool

serpro69/claude-toolbox-before-review-tool

Reviews tool configurations for correctness.

288 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
147
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/serpro69/claude-toolbox --skill review-tool

The instruction itself

6 sections, as written by the author

<!-- codex: tool-name mapping applied. See .codex/scripts/session-start.sh -->

Review Tool

Goal: Validate tool configuration files against the project schema.

Conventions

Follow standard review conventions.

Validation Rules

You MUST check every configuration file for:

  • Required fields present (name, version, entrypoint)
  • No deprecated fields (legacy_mode, compat_shim)
  • Version string matches semver format

Error Handling

When a validation error is found:

  • Record the file path, field name, and violation type
  • Continue checking remaining files — do not stop on first error
  • Group errors by severity: blocking vs. warning

Required Outputs

  • [ ] Validation report written to docs/reports/
  • [ ] Inline summary with pass/fail counts
  • [ ] Blocking errors indexed under kk:review-findings

Workflow

Mandatory order — load rules before validating. Read all configuration schemas before examining any target files.

Phases: load schemas → scan files → classify errors → write report → present summary.

How to use it

Copy the folder

Take serpro69/claude-toolbox-before-review-tool from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.