agentleFS
dgrissen2dgrissen2/persona-review-kit/skills/persona-registry/SKILL.md

persona-registry

Skill0 starsChanged 3 months agoMITView on GitHub

Resolve shared review personas from the persona-review-kit library. Use when a review skill needs to list, resolve, or apply persona lenses across Claude, Codex, or project-local contexts.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    After installation (install.sh), the kit's persona library lives at:

    line 11

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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

Persona Registry

Shared resolver for persona avatar files. Review skills should consume personas through scripts/persona_registry.py instead of hardcoding persona IDs.

After installation (install.sh), the kit's persona library lives at:

~/.config/persona-review-kit/personas/

Discovery Order

The resolver uses first-match-wins alias resolution, highest priority first:

  1. PERSONA_PATHS (explicit override; os.pathsep-separated files, dirs, or globs)
  2. Additional --persona-dir files, dirs, or globs
  3. ~/.config/persona-review-kit/personas/**/*.md — the installed kit library (top default source)
  4. Project-local ./.claude/personas/, ./personas/, ./docs/personas/
  5. ~/.claude/personas/**/*.md — your personal global Claude folder

Precedence contract: because resolution is first-match-wins, the installed kit library (3) wins over a project-local persona (4) of the same id. This is a deliberate choice for a global-install kit — the curated library is the source of truth unless you explicitly override it via PERSONA_PATHS or --persona-dir.

CLI

python scripts/persona_registry.py --list
python scripts/persona_registry.py --resolve quant,pm,/path/custom.md

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.