From pino
Save and browse prompts and plans using pino. Use when the user asks to save a prompt/plan, search saved pinos, list pinos, or delete a pino.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pino:pinoThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Pino saves prompts and plans as markdown files in `~/.pino/`.
Pino saves prompts and plans as markdown files in ~/.pino/.
pino push --summary "short title" --prompt "the full prompt text" --plan "optional plan text"
--summary and --prompt are required--plan is optional — include it when there's a structured plan alongside the promptpino list
Returns JSON output.
pino search "keyword"
Returns JSON output.
pino delete <filename>
The filename can be found from pino list or pino search output.
pino
Opens an interactive browser — not useful for Claude, but the user can run it directly.
npx claudepluginhub sonereker/pino --plugin pinoMulti-project Manus-style planning with coordinator pattern. Supports project switching, separate planning/source paths, and cross-machine sync via git. Creates task_plan.md, findings.md, and progress.md.
Persists task plans, findings, and progress as markdown files so work survives context loss and /clear. Use for multi-step projects or tasks requiring 5+ tool calls.