pipefy-building
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.
- Installs
- 408
- Last 24h
- +10
- Trending rank
- #8864
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/pipefy/ai-toolkit --skill pipefy-building- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads pipefy-building automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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-impactfor consulting when the ask is impact, ROI, or justification, not build.- plugins/pipefy/README.md — full catalog.
FAQ
What does the pipefy-building skill do?
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.
How do I install pipefy-building?
Run npx skills add https://github.com/pipefy/ai-toolkit --skill pipefy-building in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/pipefy-building/ (personal) or .claude/skills/pipefy-building/ (project).
Which AI agents can use pipefy-building?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is pipefy-building safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains pipefy-building?
It is published by pipefy in pipefy/ai-toolkit. It has 408 recorded installs.
More from pipefy/ai-toolkit
pipefy-observability
pipefy/ai-toolkit
Use this skill when the user wants to check AI agent logs, automation execution logs, org-level usage stats, AI credit consumption, or export automation job history.
pipefy-automations
pipefy/ai-toolkit
Use this skill when the user wants to create, read, update, or delete traditional automations (if/then rules) or AI automations (prompt-driven). For AI agents (conversational), see pipefy-ai-agents.
pipefy-pipes-and-cards
pipefy/ai-toolkit
Use this skill when the user wants to read, create, update, or delete pipes, phases, phase fields, labels, cards, comments, or field conditions. Use the seed-pipe-across-phases workflow when populating empty phases for demos or QA.
pipefy-introspection
pipefy/ai-toolkit
Use this skill when you need to discover GraphQL type shapes, mutation signatures, enum values, or execute arbitrary GraphQL as a fallback. This is the first fallback tier (Tier 2) when dedicated operations fail or don't exist for an operation.
pipefy-portal-setup
pipefy/ai-toolkit
Use this skill when the user wants to list, create, or configure Pipefy portals (main hub, pages, page elements, sub-portals, publish/unpublish). Uses Interfaces and internalapi. Not for pipes/cards.
pipefy-api-fallback
pipefy/ai-toolkit
Use this skill when a toolkit operation fails AND the introspection skill could not resolve the problem. This is the last-resort fallback (Tier 3): call the Pipefy GraphQL API directly using curl or httpx, authenticating with the Service Account (OAuth2) or a Personal Access Token (PAT) available as env var. Follow the 3-tier resolution strategy before reaching this point.
Popular ai & agents skills
google-agents-cli-publish
google/agents-cli
This skill should be used when the user wants to "publish an agent", "publish my ADK agent", "register an agent with Gemini", "publish to Gemini" (formerly Gemini Enterprise), or needs guidance on the agents-cli publish gemini command. Also use when the user wants to "manage agents in Agent Registry", "list/update/delete registered agents", or "register an MCP server". Covers ADK vs A2A registration modes, programmatic and interactive usage, flag reference, auto-detection from deployment metadata, Agent Registry fleet management, and troubleshooting. Part of the agents-cli skills suite. Do NOT use for deployment (use google-agents-cli-deploy).
google-agents-cli-eval
google/agents-cli
This skill should be used when the user wants to "run an evaluation", "evaluate my agent", "evaluate my ADK agent", "write an eval dataset", "analyze eval failures", "compare eval results", "optimize agent", or needs guidance on the Gemini platform eval methodology and the Quality Flywheel. Covers eval metrics, dataset schema, LLM-as-judge scoring, and common failure causes. Applies to any agents-cli project, whatever framework the agent is written in. Do NOT use for agent API code patterns (ADK: use google-agents-cli-adk-code), deployment (use google-agents-cli-deploy), or project scaffolding (use google-agents-cli-scaffold).
skill-creator
anthropics/skills
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
codex-pet
prime-skills/runcomfy-agent-skills
Codex Pet generator on RunComfy. Build a Codex-compatible Codex Pet spritesheet.webp + pet.json from a single reference image, drop it into ${CODEXHOME:-$HOME/.codex}/pets/ / and Codex picks it up as a custom Codex Pet next to the 8 built-ins. This skill produces the exact Codex Pet atlas Codex expects (1536x1872 PNG/WebP, 8 cols x 9 rows, 192x208 cells, 9 animation states — idle, running-right, running-left, waving, jumping, failed, waiting, running, review). Calls OpenAI GPT Image 2 edit ONCE via the local RunComfy CLI as runcomfy run openai/gpt-image-2/edit to produce a canonical Codex Pet pose, then assembles all 9 animation rows programmatically with ImageMagick micro-transforms — no Codex Pro, no $imagegen, no OPENAIAPIKEY required, only RUNCOMFYTOKEN. Triggers on "codex pet", "create codex pet", "make codex pet", "hatch codex pet", "/hatch image", "desktop pet codex", "codex pets", "spritesheet.webp", or any explicit ask to build a custom pet for OpenAI Codex.
full-output-enforcement
leonxlnx/taste-skill
Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.
executing-plans
obra/superpowers
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available