Ext Ops Panel
Open dashboard
Comparison

claude-flow vs make-it-work

claude-flow is a plugin bundle for AI coding tools published by CookiRui. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). make-it-work is a plugin bundle for AI coding tools published by insideout-ai. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-13. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceclaude-flowmake-it-work
Claude Code: claude-plugins-community Listed
Version: 0f7b424
Forks (GitHub): 0
Stars (GitHub): 6
Not marked · First seen
Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 12
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

claude-flow vs make-it-work
Factclaude-flowmake-it-work
Marketplaces that list it11
Stars (GitHub) (differs)6 (worse)12 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runsInstalls as a plugin bundleInstalls as a plugin bundle
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not published5
LicenceNot statedNot stated
Repository (differs)github.com/cookirui/claude-flowgithub.com/insideout-ai/make-it-work
Changes in the last 7 days00
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

claude-flow

In its own words, on Claude Code: claude-plugins-community:

Structured project cognition + autonomous execution framework for Claude Code. Includes 9 skills (TDD enforcement, 8-layer deep-task engine, persistent DAG scheduler, adversarial code review, bug diagnosis, feature planning, brainstorming), 3 specialized agents (feature-builder, code-reviewer, test-writer), and 5 hooks (file protection, bash validation, lint feedback, session state persistence, context reinjection). Helps Claude Code work on complex, multi-step engineering tasks with structure, verification, and continuity.

make-it-work

In its own words, on Claude Code: claude-plugins-community:

Skills that make Claude actually work in your project. Not just generally, but specifically, the way your codebase is built. Built for engineering teams working on large, complex codebases. Not greenfield side projects. When your codebase has history, domain rules, and legacy decisions baked in, "generally smart" isn't enough. Claude needs to know your project. go-deep maps your codebase from the inside out and builds a layered documentation system so every Claude session starts grounded in your project's real structure, rules, and use cases. Not generic assumptions. close-the-gaps acts as a Product Analyst before development begins: it finds every gap in a ticket (unclear language, missing edge cases, conflicting requirements), walks you through them one by one, and outputs a Gherkin-ready refined spec. The cost of a vague ticket is paid in rework. close-the-gaps makes sure requirements are solid before a single line of code is written.

How to run each

claude-flow As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install claude-flow@claude-community

make-it-work

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: claude-flow · What it can do: make-it-work · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built