pipefy-building — Claude Code skill: routing Pipefy build asks
A thin router that maps a Pipefy request to the right domain skill — pipes, automations, AI agents, iPaaS, portals.
npx skills add pipefy/ai-toolkit --skill pipefy-building -a claude-codeWhat pipefy-building does
This skill does not teach you how to build. It reads the ask and tells you which skill to open next. Want to design a process? It points to pipefy-process-design. Working on pipes, phases, fields or cards? That is pipefy-pipes-and-cards. Integrating with Slack, Gmail or Sheets goes to pipefy-ipaas. The routing table covers more than a dozen areas: automations, AI agents, portals, members and webhooks, database tables, relations, reports, observability, and first-time toolkit setup.
If you already have a building skill or a detailed build prompt, follow that for how to build. Use this one only to decide which Pipefy domain skill to load. It deliberately avoids re-teaching domain workflows.
Product limits — incompatible automation event and action pairs, the absence of an action that applies a label, verify-after-write, AI consent — live in the domain skills. Follow their contracts once routing is done. Worth installing if you drive Pipefy through an agent and keep forgetting which skill name to reach for.
What it helps with
- pick the right Pipefy domain skill for a given ask
- tell a design request apart from a build request
- find the skill for integrating Pipefy with Slack, Gmail or Sheets
- route portal work or database table work to the correct skill
- keep ROI consulting separate from actual implementation
Example prompts for the agent
- I want to set up a pipe with phases and fields in Pipefy — which skill should I open?
- I need to connect Pipefy to Gmail, point me to the right skill
- help me design this process, not build it
How to install pipefy-building
1Skills CLI (Vercel)
npx skills add pipefy/ai-toolkit --skill pipefy-building -a claude-code2Manually: put the files in place
~/.claude/skills/pipefy-building/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/pipefy-building/
1Skills CLI (Vercel)
npx skills add pipefy/ai-toolkit --skill pipefy-building -a codex2Manually: put the files in place
.agents/skills/pipefy-building/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add pipefy/ai-toolkit --skill pipefy-building -a cursor2Manually: put the files in place
.cursor/skills/pipefy-building/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install pipefy/ai-toolkit pipefy-building2Manually: put the files in place
.github/skills/pipefy-building/SKILL.md1Skills CLI (Vercel)
npx skills add pipefy/ai-toolkit --skill pipefy-building -a gemini-cli2Platform CLI
gemini skills install https://github.com/pipefy/ai-toolkit --path plugins/pipefy/skills/pipefy-buildingManually: put the files in place
.devin/skills/pipefy-building/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add pipefy/ai-toolkit --skill pipefy-building -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about pipefy-building
How do I install pipefy-building in Claude?
Run npx skills add pipefy/ai-toolkit --skill pipefy-building -a claude-code. The skill lands at ~/.claude/skills/pipefy-building/SKILL.md.
What does pipefy-building do?
It maps user intent to the correct Pipefy domain skill and tells you which one to read. It does not describe the workflows themselves.
How is it different from the domain skills?
It only routes. If you already have a building skill or a detailed build prompt, use that for how to build and this one to pick which domain skill to load.
Source text
SKILL.md · Apache-2.0
--- name: pipefy-building description: > Thin router for Pipefy build and configure asks: map user intent to the correct domain skill (pipes, automations, AI agents, iPaaS, portals, etc.). Use when the user wants to create, build, configure, or integrate something in Pipefy and you need to know which skill to open. Do not use this skill as a delivery playbook — if the user already has a building skill or a detailed build prompt, follow that for how to build; use this skill only for which Pipefy domain skill to read. tags: [pipefy, building, routing, orchestration] --- # Pipefy Building (router) Maps **what the user wants** to **which domain skill to read**. It does not teach create/update workflows — open the linked skill for that. If the user already has a building skill or a detailed build prompt/spec, use that for *how to build*; use this skill for *which Pipefy skill to load*. --- ## When the user wants X → read skill Y | User intent (examples) | Read | |------------------------|------| | Design / architecture / "help me structure this process" | `pipefy-process-design` (consulting only) | | Impact / ROI / "is this change worth it?" / justify internally | `pipefy-process-impact` (consulting; do not implement from there) | | Pipes, phases, fields, labels, cards, field conditions | `pipefy-pipes-and-cards` | | Traditional or AI automations (if/then, prompt-driven rules) | `pipefy-automations` | | Conversational AI agents and behaviors | `pipefy-ai-agents` | | External integration / integrate with Slack, Gmail, Sheets, or another app | `pipefy-ipaas` | | Portals, pages, elements, sub-portals | `pipefy-portal-setup` | | Members, email templates, inbox email, webhooks | `pipefy-members-email-webhooks` | | Database tables and records | `pipefy-database-tables` | | Pipe/card relations | `pipefy-relations` | | Reports and exports | `pipefy-reports` | | Logs, usage, credits, job exports | `pipefy-observability` | | First-time toolkit setup | `pipefy-toolkit-setup` | **Do not re-teach domain workflows here — open the linked skill.** --- ## Product limits live in domain skills Hard stops and quirks (phase connections UI-only, email template create/edit UI-only, incompatible automation event×action pairs, no automation action applies a label, verify-after-write, AI consent) are documented in the domain skills above; follow those contracts after routing. ## See also - `pipefy-process-design` — consulting when the ask is design, not build. - `pipefy-process-impact` for consulting when the ask is impact, ROI, or justification, not build. - [plugins/pipefy/README.md](https://github.com/pipefy/ai-toolkit/blob/main/plugins/pipefy/README.md) — full catalog.
© pipefy · Apache-2.0 · pipefy/ai-toolkit
