RyanAlberts

Tool Policy — Testing skill for Claude Code

Testing community

Write your company's rules for an agent's tool calls, test them on past traces, and run them on every change.

How to install Tool Policy

Installs to ~/.claude/skills/ryanalberts-pmstack-tool-policy/SKILL.md

Terminal
mkdir -p ~/.claude/skills/ryanalberts-pmstack-tool-policy && curl -fsSL https://raw.githubusercontent.com/RyanAlberts/pmstack/HEAD/commands/tool-policy.md -o ~/.claude/skills/ryanalberts-pmstack-tool-policy/SKILL.md

Restart Claude Code, or start a new session, for it to be picked up.

What Tool Policy does


description: Write your company's rules for an agent's tool calls, test them on past traces, and run them on every change argument-hint: "[trace file or project.json]"

Use the Skill tool to run the `pmstack-tool-policy` skill from the pmstack plugin with these arguments: $ARGUMENTS. If the skill is not available, tell the user to run /plugin install pmstack@pmstack.

Alternatives in Testing

  • Pua — Use when the user invokes /pua or asks for PUA mode, try-harder/retry help, change-approach coaching, completi 19.5k ★
  • Claude Codepro — by Max Ritter - Professional development environment for Claude Code with spec-driven workflow, TDD enforcemen 1.6k ★
  • Test TDD — Run when user calls /test-tdd 957 ★

Full documentation available on GitHub

View Source Repository