# Pipa Tools

> Use when the user wants a standalone Pipa utility or hosted capability: audio briefs, voice huddles, follow-up reminders, time tracking, or future small Pipa utilities.

- Skill: `lunchpaillola/pipa-tools` (Agent Skill)
- Install (CLI): `npx skillmds@latest add lunchpaillola/pipa-tools`
- Raw SKILL.md: https://api.skillmd.com/api/skills/lunchpaillola/pipa-tools/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: lunchpaillola (https://skillmd.com/u/lunchpaillola)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/lunchpaillola/pipa-tools

---


# Pipa 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 this` is not an audio brief unless audio/listenable/spoken/phone-friendly wording is explicit.
- `talk through` is 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.