How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

pipefy-skill-template - Skill

Name: pipefy-skill-template
Author: pipefy

Imported from pipefy/ai-toolkit (.github/skill-template/pipefy-skill-template/SKILL.md). Install upstream with npx skills add pipefy/ai-toolkit --skill pipefy-skill-template. Copyright stays with the author.

[Skill title]

[One or two sentences: what this skill does and when an agent should load it.] [Optional: MCP tool count, e.g. N MCP tools.]

When to use

[User intent / example phrase that should trigger this skill.]
[Another trigger.]

Do not use this skill for:

[Out of scope — point to another skill or approach when relevant.]

Prerequisites

[IDs, roles, or config that must exist first — e.g. pipe_id, org access.]
[Any install path: Hosted MCP, local MCP, CLI — if it matters.]

Tools needed

Tool (MCP)	CLI equivalent	Read-only
`[mcp_tool_name]`	`pipefy [domain] [action]`	Yes/No

Replace bracket placeholders with real MCP tool names from the live server (or docs/parity.md) and shipped CLI commands only. Unknown names fail CI in this repository.

Steps

[Step name] — [what to do and why.]

MCP:

[mcp_tool_name] [arg]=[value]

CLI:

pipefy [domain] [action] --[flag] [value]

[Next step] — ...

Success criteria

[Observable outcome the agent or human can verify.]

Failure modes

Symptom	Likely cause	Recovery
[Error or bad state]	[Cause]	[Fix or fallback skill]

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "pipefy-ai-toolkit-pipefy-skill-template", "kind": "skill", "name": "pipefy-skill-template", "description": "Copy this file when authoring a new Pipefy skill. Replace placeholders, then rename the folder so it matches the frontmatter name.", "publisher": "pipefy", "version": "1.0.0", "capabilities": { "domains": [ "medical" ], "tags": [ "skill-md", "pipefy", "template", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Copy this file when authoring a new Pipefy skill. Replace placeholders, then rename the folder so it matches the frontmatter name." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/pipefy/ai-toolkit", "path": ".github/skill-template/pipefy-skill-template/SKILL.md", "ref": "HEAD", "url": "https://github.com/pipefy/ai-toolkit/blob/HEAD/.github/skill-template/pipefy-skill-template/SKILL.md", "key": "pipefy/ai-toolkit/.github/skill-template/pipefy-skill-template/SKILL.md" } }, "instructions": "# [Skill title]\n\n[One or two sentences: what this skill does and when an agent should load it.]\n[Optional: MCP tool count, e.g. **N MCP tools**.]\n\n---\n\n## When to use\n\n- [User intent / example phrase that should trigger this skill.]\n- [Another trigger.]\n\nDo not use this skill for:\n\n- [Out of scope — point to another skill or approach when relevant.]\n\n## Prerequisites\n\n- [IDs, roles, or config that must exist first — e.g. `pipe_id`, org access.]\n- [Any install path: Hosted MCP, local MCP, CLI — if it matters.]\n\n## Tools needed\n\n| Tool (MCP) | CLI equivalent | Read-only |\n|------------|---------", "cost": { "context_tokens": 354 } }

pipefy-skill-template

About

[Skill title]

When to use

Prerequisites

Tools needed

Steps

Success criteria

Failure modes

See also

Install pipefy-skill-template and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews