rpi — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited rpi (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Unified entry point for the brainstorm-plan-evaluate-implement workflow.
brainstorm (optional) → plan → evaluate → implement
↓ ↓
Uses research Uses research| Keyword | Syntax | What it does |
|---|---|---|
brainstorm | brainstorm <topic> | Explore approaches for an idea (optional — skip for simple changes) |
plan | plan <description or .thoughts doc path> | Create a TDD-structured implementation plan |
evaluate | evaluate <description> | Evaluate an artifact across multiple quality dimensions with scoring and upgrade paths |
handoff | handoff [description of next session] | Summarize the current conversation into a handoff doc for another agent |
pickup | pickup [path to handoff] | Resume work from a handoff document |
implement all | implement all [plan path] | Implement all phases from a plan |
implement phase N | implement phase N [plan path] | Implement a specific phase from a plan |
write | write | Save the most recent output to .thoughts/ |
Any keyword can accept a path to an existing .thoughts/ document as context:
plan .thoughts/brainstorms/2026-04-25-my-idea.md — plan from an existing brainstormevaluate .thoughts/plans/2026-04-25-my-plan.md — evaluate a planimplement all .thoughts/plans/2026-04-25-my-plan.md — implement from a specific planpickup .thoughts/handoffs/2026-05-24-auth-refactor.md — resume from a specific handoffFor implement with no explicit path, find the most recent .thoughts/plans/*.md file and confirm with the user before proceeding. If no plan files exist, tell the user and suggest running rpi plan first.
Parse the first word of the input as the keyword. For implement, parse all or phase N.
| Keyword | Reference |
|---|---|
brainstorm | brainstorming |
plan | planning |
evaluate | evaluating |
implement | implementing |
handoff | handoff |
pickup | handoff |
write | writing-documentation |
Research files (researching-codebase, researching-web) are internal to brainstorm and plan — not standalone keywords.
Document conventions across all workflows follow writing-documentation.
Most workflows save nothing automatically. Run rpi write when ready to persist. The implement workflow prompts you at completion — for all others, use write explicitly. The handoff workflow is the exception: it writes immediately.
See writing-documentation for naming and auto-detection conventions.
If invoked with no keyword or an unrecognized keyword, show the keyword reference table above and ask the user what they'd like to do.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.