pipa-skills

Use when the user wants Pipa to turn messy service-business demand into defined work: discovery, scope, requirements, proposals, acceptance checks, decisions, client/project onboarding, and setup for delivery.

Use when the user wants Pipa to coordinate active service delivery: status, blockers, risks, owners, handoffs, dependencies, triage, weekly client updates, QA, and next actions.

Use when the user wants Pipa to help a service business get paid: invoices, payments, billable time, budgets, margin, change-control money impact, and payment follow-through.

Use when the user wants Pipa to help a small service business get work: content, inbound, leads, pipeline, opportunities, referrals, outreach, market signals, and next opportunity actions.

Use when the user wants Pipa to improve how the service business runs: retrospectives, lessons, SOPs, templates, reusable processes, archive readiness, closeout learning, and operational improvements.

Use when the user wants Pipa to maintain client trust: follow-ups, check-ins, client health, retention, renewals, referrals, testimonials, stakeholder care, and relationship-sensitive next actions.

Use when the user wants to operate Pipa itself: onboard Pipa into their business, update business profile/preferences, manage company brain or memory, connect tools, configure automations/triggers/loops, or audit what Pipa knows and can access.

Use when the user invokes Pipa and needs routing across service-business operations, Pipa setup/management, or Pipa tools. Routes to business lanes: get work, define work, deliver work, get paid, keep clients, improve operations; to Manage Pipa for setup, tools, automations, memory, and preferences; or to Pipa Tools for audio briefs, huddles, reminders, time tracking, and Composio-backed utilities.

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

Use the Composio MCP with Pipa to discover and operate external app tools safely.

Create and cancel simple one-shot email follow-up reminders through Pipa. Use this when the user wants Pipa to email them a specific reminder at a future time, such as “email me tomorrow at 9 to follow up,” “remind me by email next Friday,” or “send me a reminder in two hours.” Also use it to cancel a previously scheduled Pipa Follow-Up reminder. Do not use for generic follow-up work, recurring reminders, Gmail scheduled send, drafting emails, reply detection, inbox monitoring, Slack/SMS reminders, or reminders to other people.

Use when the user wants to talk through work with Pipa or their current agent in a live voice huddle: Pipa Huddle, Pipa voice session, talk this through, walking work session, plan this by voice, voice call with my agent, or discuss this out loud. Starts a voice huddle with agent context and optional handoff. Do not use for audio brief generation, generic TTS, video meetings, Zoom/Meet bots, or realtime voice coding/permission approval.

Track work time through Pipa generic agent utility records. Use when user asks to start, stop, switch, inspect, backfill, update, archive, or summarize time entries.

Use when the user wants a listenable brief for work produced by AI agents, coding tools, or document workflows: agent sessions, code changes, pull requests, plans, specs, research reports, documentation pages, blog posts, URLs, local files, or pasted markdown. Also use for casual requests like give me the brief, audio brief, listenable walkthrough, phone-friendly review, or static review page for understanding work artifacts without reading everything line by line. Do not use for generic TTS or podcast creation from scratch.

Handle event-triggered automations for Pipa. Use this whenever the user wants Pipa to run a workflow when an external event happens, such as a GitHub PR opening, a Linear issue being created, a Slack channel changing, a new ticket arriving, or asks to list, inspect, or delete existing event triggers. This skill owns trigger proposal, confirmation, and gateway trigger-subscription API calls.