Skip to content
For creators · Free · Open source

Ship a plugin that fires itself.

Bring your skills. Add the routing. Flowy auto-invokes the right one as users prompt. Your domain expertise, running on every run.

The deal

What makes it fire

Two things: a few hand-picked skills and a FLOW.md that routes them. Flowy auto-invokes the rest.

you write

your-skillanother-skillFLOW.md

Your skills, and the router that fires them in order.

flowy provides, free

  • Enforcement (the hook)
  • Per-session state
  • Surviving compaction

You never write a hook.

your-flow/
your-flow/
├── FLOW.md        routing decision tree
├── SKILL.md       overview
├── LICENSE        required
└── skills/your-skill/SKILL.md

For creators

Why publish here?

01

Your routing runs for every user

Encode the path once. Every user who installs your plugin gets your exact routing. Your domain expertise, running on every run.

02

Credit goes to you

Your handle on every listing. Domain depth visible. Anonymous by default if you prefer.

Creator monetization is a V2 bet. No date. Watch the repo.

Build process

How it works

Five steps from blueprint to merged listing.

  1. 01

    Install

    Add the Flowy marketplace to Claude Code, install the flowy-core engine, then add a Flow overlay.

    Install
    > /plugin marketplace add flowy-sh/flowy-core
    > /plugin install flowy-core
    > /plugin install flowy-superpowers
    > /flowy-superpowers:activate
  2. 02

    Clone the blueprint

    Grab the format-canonical starter Flow.

    clone.sh
    $ git clone https://github.com/MaximoCorrea1/flowy-flows

    Copy flows/_blueprint/ somewhere OUTSIDE this repo before customizing.

  3. 03

    Customize

    Rename the _blueprint folder and the your-skill-here skill. Replace every <<…>> placeholder with your own phases, conditions, and skills. See a fully-worked example first. Ten files max.

  4. 04

    Validate

    Paste your FLOW.md at flowy.sh/create-a-flow/validate for a quick lint, or load the full bundle for all checks.

  5. 05

    Submit

    Sign in at flowy.sh/me/flows/new to import from GitHub, OR open a PR to MaximoCorrea1/flowy-flows. Both paths land in the same review queue.

Review criteria

What we look for

  • Decision tree present (not prose)
  • Skills bundled, not referenced
  • Problem solved end-to-end
  • Domain credibility evident
  • License declared

Hard stops

What gets rejected

  • Rejected · 01

    FLOW.md that's prose without a decision tree. The agent has nothing to route from.

  • Rejected · 02

    Skills referenced but not bundled in skills/. Your plugin does not ship complete.

  • Rejected · 03

    No LICENSE file. We cannot host content without a license declaration.

Start here

Get the blueprint

The starter plugin. Fork it and go.

Open on GitHub

Questions

FAQ

How long does review take?

Maximo reviews every submission personally. Expect 3 to 7 days for a first pass.

What if my plugin gets rejected?

We send specific feedback. Iterate and resubmit. No limit on attempts.

Can I update my plugin after it's published?

Yes. Submit a new version via the same path and we will update the listing.

Do I have to use my real name?

No. Pick any handle. Anonymous attribution is fine.

What licenses are accepted?

CC-BY-SA-4.0 (default), MIT, CC-BY-4.0, or CC0-1.0.

You bring the plugin. Flowy makes it fire.
Ship it.