{"$schema":"https://schemas.agentskills.io/discovery/0.2.0/schema.json","skills":[{"name":"flow-cli","type":"skill-md","description":"Drive the Flow public API from the terminal via the `flow` CLI (`@flow/cli`). Use when the user wants to script Flow — managing agents, runs, cases, queues, files, skills, connections, Process Mapping processes, Insights dashboards, or hitting an arbitrary endpoint via `flow api` — instead of clicking through the Flow web UI or hand-crafting `curl` calls.","url":"/.well-known/agent-skills/flow-cli/SKILL.md","digest":"sha256:0182243c007214f2c126bf0864b6cc1969e34b37d63dcd321f5ddd83a0d4f301"},{"name":"flow-sop-writer","type":"skill-md","description":"Draft, rewrite, or critique a Flow Agent AOP. Use when the user wants to improve an existing AOP or write a new one from a brief. Returns the AOP as a single complete markdown document in the canonical GOAL / STEPS / NOTES shape.","url":"/.well-known/agent-skills/flow-sop-writer/SKILL.md","digest":"sha256:99054bf47f5013710f1c256f1bc6f3e84e95f4552165fa8527b5d39e91ba6bdf"},{"name":"flow-job-debugger","type":"skill-md","description":"Investigate why a Flow Run failed or produced the wrong outcome. Use when the user shares a failed Run, asks \"why did this Run fail\", or wants to fix a recurring failure on an Agent. Reads the Run's transcript and the Build that was active for it via the Flow public API, names the root cause from a fixed failure-mode taxonomy, and proposes one concrete fix — handing off to flow-sop-writer for any AOP rewrite.","url":"/.well-known/agent-skills/flow-job-debugger/SKILL.md","digest":"sha256:1e5b33628cfa431266690add8527d4820479bab7997024a9f382ac761950b7cc"},{"name":"flow-connection-doctor","type":"skill-md","description":"Diagnose and health-check the Connections and credentials a Flow Agent relies on. Use when the user asks whether a Connection is set up or available, why an Agent is blocked on authentication, what a Connection can do, or wants a proactive check across an Agent or a folder of Agents. Reads each Build's Connections and their live state via the Flow public API, names the problem, and proposes one concrete fix — handing off to flow-job-debugger when the evidence lives in a single failing Run.","url":"/.well-known/agent-skills/flow-connection-doctor/SKILL.md","digest":"sha256:4e0b5bd0c515f8c5c6d7f246b45cd2efa6364278df7c38b460f7f4083cfd54d3"},{"name":"flow-improve-agent","type":"skill-md","description":"Run the guided, end-to-end loop that makes one Flow Agent better. Use when the user wants to \"improve this Agent\", \"make my Agent better\", \"help me tune this Agent\", \"this Agent isn't good enough\", \"fix this Agent based on its Runs\", or asks you to take an Agent from where it is to a concrete, applied improvement — not just a read-only audit. You drive the conversation: pin the Agent, survey its whole setup (AOP, Connections, Skills, triggers, memory, recent Runs), agree on what to base the improvement on (the user's feedback or the evidence in the Runs), propose a Run range and confirm it, get the grounded findings from the flow-workflow-debugger / flow-job-debugger skills, propose concrete changes, and — on the user's yes — apply them (AOP via flow-sop-writer as a new Build, config with your tools). The boundary against flow-workflow-debugger: that skill is the read-only audit; this skill is the interactive loop that ends in an applied change and calls flow-workflow-debugger to do the analysis.","url":"/.well-known/agent-skills/flow-improve-agent/SKILL.md","digest":"sha256:6dd77910e3725b9f36d884374919f95d5d69bf4b6c58fbe0dcd1eee930e6b234"},{"name":"flow-improve-queue","type":"skill-md","description":"Run the guided, end-to-end loop that makes one Flow Queue — and the producer→consumer workflow around it — better. Use when the user wants to \"improve this Queue\", \"this Queue keeps backing up, fix it\", or take a Queue to a concrete, applied improvement — not just a read-only audit. You drive the conversation: pin the Queue, survey its whole shape (producers and consumers, backlog and case state, both Agents' AOPs at the seam, triggers and concurrency, the Runs flowing through), agree what to base the improvement on (the user's feedback or the evidence in the Runs/backlog), propose a Run/case range and confirm it, get grounded findings from the flow-workflow-debugger / flow-job-debugger skills, propose concrete changes, and — on the user's yes — apply them (AOPs via flow-sop-writer as new Builds, topology and triggers with your tools). The boundary vs flow-workflow-debugger: that skill is the read-only audit; this is the interactive loop that ends in an applied change. For a single standalone Agent, use flow-improve-agent instead.","url":"/.well-known/agent-skills/flow-improve-queue/SKILL.md","digest":"sha256:e4129842ab672c152f3589c61c26c7963e9380fc314abe61b11725a75bbc4dbf"},{"name":"flow-workflow-debugger","type":"skill-md","description":"Audit a Flow Agent — or a multi-Agent workflow connected by a Queue — across many Runs to find systemic inefficiencies and quality issues, then recommend concrete AOP and architecture changes. Use when the user asks to \"analyze this workflow\", \"audit my Agent\", \"why is this Agent slow / inconsistent / low quality across runs\", \"why does my queue keep backing up\", or wants a health check over an Agent's recent Runs — as opposed to debugging one failed Run (that's flow-job-debugger). Reads recent Runs, eval scores, the producer/consumer queue topology, and the AOPs those Runs actually ran against via the Flow public API — leading with the queue topology and backlog and sizing the run sample to the question; hands off to flow-sop-writer for any AOP rewrite.","url":"/.well-known/agent-skills/flow-workflow-debugger/SKILL.md","digest":"sha256:a01eba14389b6da12334b12857b06d18d2e788fb079323592d0e88ecbf5c5758"}]}