Workflow · Brew 2 · Bloom

Get a repo, skill or plugin found

Make a repo, skill or plugin show up for what it does: fix how it is described and listed, publish it, then check every listing matches what is live.

The steps, in order.

  1. Step 1

    Findable Sets up discovery for a GitHub repo, skill, plugin or MCP server so it gets found by what it does, not only by its name. It audits where you rank today, works out the queries strangers type, then drafts the About text, topics, README opening, release notes, site page and directory plan — real numbers only, and nothing public changes without your go-ahead. unversioned · shown working 24 Oct 2026

  2. Step 2

    Publish Pipeline Turns a pile of skill repos into a published site: a committed manifest decides what is public, discovery opens a pull request, and a green merge deploys generated pages, both discovery indexes, a sitemap and a verified build. unversioned

  3. Step 3

    Upstream Check Finds local commits that never reached GitHub, pushes only clean fast-forwards after a secret screen, then checks that the site index, the homepage, the marketplace and the READMEs agree with the repos that actually ship a SKILL.md. unversioned · shown working 24 Oct 2026

findable-polish and upstream-polish add the rewrite.

Install the whole workflow.

npx skills add arm-pz/findable --skill findable  # step 1
npx skills add arm-pz/publish-pipeline           # step 2
npx skills add arm-pz/upstream-check             # step 3

In Claude Code you can take every skill at once instead: /plugin marketplace add arm-pz/caffeinity-skills, then /plugin install caffeinity@caffeinity-skills. Not sure this is the right workflow? Install caffeinity-routing and describe the outcome; it picks one.

Other workflows.

Need this fitted to your team's own tools and rules? We build custom skills.