agentleFS
mementomori-comementomori-co/maker-mastery/.claude/skills/agent-review/SKILL.md

agent-review

Skill2 starsChanged 26 days agoMITView on GitHub

Use when hooks, settings, agent files, skills or MCP configuration must be reviewed in a fresh context against the Claude Code and MCP docs for security and compliance. Runs the mcp-agent-engineer in a fresh context and writes a ranked findings file to work\reports\reviews\<date>-<slug>.md.

11 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use commit.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • SentrySkill

    commit

    Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    After any change to .claude\settings.json, tools\hooks\, .claude\agents\, .claude\skills\ or .mcp.json, or before a new MCP server is …

    line 12
  2. Very specific:

    Read the files. Run the shipped checks with .venv\Scripts\python.exe: the tests under tools\tests\ that cover the reviewed files (for …

    line 16
  3. Distinctive:

    Write the review: closed / open / new findings, severity, fix, evidence.

    line 17

“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Overview

Input: $ARGUMENTS, as <slug> | <paths>. Output: work\reports\reviews\YYYY-MM-DD-<slug>.md with findings ranked by severity, each with a docs quote or a test result and a concrete fix. No installs, no settings changes.

When to use

After any change to .claude\settings.json, tools\hooks\, .claude\agents\, .claude\skills\ or .mcp.json, or before a new MCP server is proposed. Not for building a new MCP tool (use /mcp-new-tool).

Steps

  1. Fetch the relevant docs this run (https://docs.anthropic.com/en/docs/claude-code/hooks, https://docs.anthropic.com/en/docs/claude-code/settings, https://docs.anthropic.com/en/docs/claude-code/sub-agents, https://docs.anthropic.com/en/docs/claude-code/skills, https://docs.anthropic.com/en/docs/claude-code/mcp, https://modelcontextprotocol.io/specification/latest; curl fallback on HTTP 402/403) and quote the lines you rely on.
  2. Read the files. Run the shipped checks with .venv\Scripts\python.exe: the tests under tools\tests\ that cover the reviewed files (for example the guard-hook tests) and tools\check_skill.py on any skill. Add targeted probes (crafted hook inputs on stdin) without modifying anything.
  3. Write the review: closed / open / new findings, severity, fix, evidence. Secrets never appear in the file.
  4. Return the path and the open-finding count.

Common rationalizations

RationalizationReality
"The hook fired once, it works."A guard hook that passed its first run can still be bypassed by another tool name, path form or quoting. Probe the edge cases.
"I'll just fix it while I'm here."Reviewer and fixer are different contexts. Report; the lead fixes.

Red flags

  • A finding without a docs quote or a test result.
  • Any edit to settings or hooks during the review.

Verification

  • Review file written; findings ranked with fixes.
  • Tests run and results quoted.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.