About pipa-tools
A routing skill for standalone utilities, directing requests to the appropriate Pipa tool rather than a business lane. It also identifies required inputs and blockers and preserves confirmation gates for actions such as reminders or time-record changes.
Key features
- 01Route requests to dedicated utility skills
- 02Distinguish utilities from business workflows
- 03Identify required inputs and blockers
- 04Require confirmation for external actions
Use cases
- 01Route a request for an audio brief
- 02Choose a skill for a live voice huddle
- 03Direct a one-shot reminder request
- 04Route time-record updates
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/pipa-toolsin Claude Code to confirm it loaded.
Details
From the project READMEPipa Tools
Route standalone utilities without turning them into business lanes.
Tool Routes
- Audio/listenable/phone-friendly brief ->
pipa-audio-brief. - Live voice conversation or huddle ->
pipa-huddle-beta. - One-shot self-email reminder ->
pipa-follow-up-reminders. - Start/stop/switch/backfill/update/archive/summarize time records ->
pipa-time-tracking.
Output Contract
- Selected tool.
- Why this is a utility instead of a business lane.
- Required inputs and blockers.
- Confirmation gate before publishing, reminders, huddles, or time-record changes.
- Source/provenance when connected tools are used.
Boundaries
- Business outcome requests route to the six business lane skills first.
- Tool setup, connectors, automations, and company brain configuration go to
pipa-manage.
Gotchas
brief thisis not an audio brief unless audio/listenable/spoken/phone-friendly wording is explicit.talk throughis not a voice huddle unless live voice wording is explicit.- External writes, published audio pages, reminders, huddles, and time-record changes require the destination skill's confirmation gate.
Comments
Markdown supported