Skip to content

Claude Code plugins and skills that fire themselves :)

Install one plugin and the right skill gets Auto-invokedWhat is this?This plugin ships a FLOW.md router the engine fires, so the matching skill runs itself. No slash command to remember.Learn how → as you prompt. Only on Flowy.

What's a Flow?

A big messy pile of skills. A Flow auto-invokes the perfect skill for the moment, based on your intent and context. You just prompt.

we call it a Flow: plugin + auto-invocation, routed by your prompt

your skills

brainstormingtddcode-reviewdebuggingwriting-plansverificationrefactorgit-commitdocsbenchmark
FLOW.md

your Flow

  1. 1brainstorming
  2. 2plan
  3. 3tdd
  4. 4verify

Loads once. Runs for about 40 tokens a prompt. See the cost ↓

How it works.

Load the Flow once. After that it routes you to the perfect skill every time you prompt. About 40 tokens a turn.

Once

The whole Flow loads into context.

One install line. Your agent reads it a single time.

agent context

FLOW.md≈3,000 tokens
then
Every prompt

A hook keeps the Flow in focus.

So you just prompt, and it fires the exact skill you need. No skill names. No searching.

your promptFlow routesthe right skill

↻ every prompt · ≈40 tokens

Why a Flow works

You prompt. It routes you to the perfect skill.

claude-code
/flowy-superpowers:activate
flow active. you just prompt.
ship the rate limiter, then write the rollout note
reading intent: feature + docs
auto-invoked
brainstormingscope it before codetest-driven-devred, green, refactorwriting-plansdraft the rollout note
you named no skill. flowy fired 3.
why is this failing in prod?
reading intent: bug
auto-invoked
systematic-debuggingroot cause, not a guess
you named no skill. flowy fired 1.
what does this file do?
reading intent: question. no skill needed
answered. nothing forced.

The flow that actually works for X, by someone who actually does X.

Every skills directory ends at the install command. Flowy starts there.

Measured, not promised.

~50%of the time, Skills auto-activate at baseline. A coin flip.

Third-party controlled evals, Sonnet 4.5

0 vs 19Skills fired: a real 76-prompt session with no routing, vs the same kind of workload with a Flow active.

One paired observation, our transcripts. Directional.

38% to 100%routing adherence once the agent reads the FLOW.md.

Our banner pilot, n=8 per arm.

Measured in our own sessions. Directional, not a lab. Methodology public →

measured june 2026

See it work

One messy prompt, four problems. The Flow scoped all four before it wrote a line.

claude-code
/flowy-superpowers:activate
flow active. you just prompt.
upstream-link idea, skills sync, validator friction, a LICENSE bug
reading intent: 4 problems, one prompt
auto-invoked
brainstormingscope before code4 explore agentsin parallel
all four scoped. no code yet. you named no skill.

Token cost

Loads once.
Then it's almost free.

You load the Flow once. After that, your agent reads the routing straight from context. About 40 tokens a prompt, not the whole file every turn.

≈30×

fewer tokens over a 50-prompt session.

≈3,070load the Flow once
≈40read from context, per prompt
Re-paste the workflow each turnFlowy (loads once)
≈153,500tokens≈5,070prompt 150

estimated on flowy-superpowers · ≈4 chars/token

Why not just load skills yourself?

You can. Then you are the router, every prompt. Or Flowy auto-invokes the perfect skill for the task, and you just prompt.

By hand
  • you pick or guess the skill
  • you remember to invoke the discipline
  • you re-read the workflow every turn
  • you wire each skill yourself
With Flowy

The AI auto-invokes the perfect skill for your task.

your promptFLOW.mdthe perfect skill
  • auto-routed by intent + context
  • TDD, review, verify enforced by the hook
  • ~40 tokens read from context
  • install the engine once, add any Flow

Submit a Flow.

Got a routing pattern you run every day? Ship it. We review every one. Merged Flows join the library: credit, open source, free.

submit-a-flow.sh
$ git clone https://github.com/MaximoCorrea1/flowy-flows
$ cd flowy-flows && cp -r flow.template flow.your-name
$ # edit FLOW.md + README.md: declare the goal and the steps
$ gh pr create --title "Add flow: your-name"
Make a FlowOr submit via PR on GitHub
Coming soon

A Flow from any skills you’ve got.

Drop your skills repo. A Flow gets built. Install the plugin and your own skills start auto-invoking, by your intent and context.

Your team has its own skills for its own workflow. Build the Flow once. They fire by intent. Save the time, save the mental energy.

01

Drop your skills repo

Any folder of skills. Point Flowy at it.

02

A Flow gets built

Flowy wraps them with a FLOW.md router.

03

Install & auto-invoke

Your own skills, fired by your intent and context.

Stay tuned. One short note the day it ships.

Roadmap: team flows, gated delivery, creator earnings

Don't let your agent go wild. Harness it.

Install the engine once, add any Flow. You just prompt.

Install in Claude Code

claude-code
> /plugin marketplace add flowy-sh/flowy-core
> /plugin install flowy-core
> /plugin install flowy-superpowers
> /flowy-superpowers:activate