Loading...
Loading...
Found 4 Skills
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.
Map developer intent and natural language to the correct Ledger Device Management Kit (DMK) components, operations, and API methods. Use when a developer's request is phrased informally, incompletely, or in terms of outcomes rather than API methods, when the intent is ambiguous and needs mapping to a specific DMK component or operation, or when a developer asks 'how do I...', 'what's the difference between...', or describes a symptom rather than an API.
Top-level map of the skill fleet, for "which skill does this need?" when the answer is not obvious. Invoke when a task's ownership is UNCLEAR or it spans MULTIPLE domains. It routes intent → the right router / skill / recipe and names how to invoke each. When the primary goal already names a domain, enter that domain router or member directly instead. Curates the ADOPTED surface only; the full installed roster lives in the skill manifest.
Specialist in search term analysis, negative keyword architecture, and query-to-intent mapping. Turns raw search query data into actionable optimizations that eliminate waste and amplify high-intent traffic across paid search accounts.