flow
Skill13 starsChanged 3 days agoMITView on GitHub
Use Flow to inspect project planning stages, execute scoped cards, and verify evidence-backed gates.
34 other projects use a version of this.
Adopted by
Most recently taken up by
- retospect/precis-mcptheir own version, first seen Nov 15, 2026
- marco-bertelli/filotheir own version, first seen Nov 15, 2026
- matthewdonsemail-lab/logtheir own version, first seen Nov 15, 2026
- cofin/flowtheir own version, first seen Nov 15, 2026
- hejdujir/docker-claude-codetheir own version, first seen Nov 11, 2026
- baodhg/FLOWtheir own version, first seen Nov 8, 2026
Used with
Projects with it also use grill, implement and 5 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
renatorozasSkillgrill
Adversarial code review. Don't let me ship until the changes pass your scrutiny.
Also in 3 projects that use this
Hugging FaceSkillimplement
Make tests pass. Invoke after /write-tests produces failing tests.
Also in 5 projects that use this
SentrySkillreview
Fixture review skill.
Also in 6 projects that use this
AnthropicSkillstatus
Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.
Also in 3 projects that use this
BlockSkillplan
Draft a TDD, PRD, or lightweight plan in the conversation without committing it.
Also in 3 projects that use this
AWSSkillship
Finalize dev work on an issue branch — update docs, push, and open a PR.
Also in 3 projects that use this
Other versions34 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 34
- react/react★ 253ksame name
- facebook/react★ 253ksame name
- software-mansion/react-native-audio-api★ 856same name
- simota/agent-skills★ 99same name
- panayiotism/claude-harness★ 79same name
- matthewdonsemail-lab/log★ 63same name
- rainday/smart-blog-skills★ 35same name
- cofin/flow★ 20same name
- basezh/agent-skills-on-base★ 15same name
- retospect/precis-mcp★ 11same name
24 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/flow/law/CLAUDE.mdCLAUDE.md
- flowSkill
- harnessSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 28 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Read the canonical skill (skills/flow/SKILL.md from project root) before acting.
- Very specific: line 13
Follow the canonical skill dispatch, active card allowed files, gates, and evidence requirements.
“Common” is measured: kept by at least 6 in 10 of the 28 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Flow project skill pointer
For project Codex/Gemini discovery, this pointer lives in .agents/skills/flow/SKILL.md.
This target is only for repositories with the canonical Flow bundle checked into project-root skills/flow; global installs and .claude/skills/flow alone do not satisfy this prerequisite.
Read the canonical skill (skills/flow/SKILL.md from project root) before acting; it remains the source of truth. Do not copy its instructions here or treat this pointer as an additional runtime.
Set <skill-dir> to that canonical bundle directory (skills/flow). From the project root, invoke bash <skill-dir>/runner/flow.sh <command> (macOS / Linux / Windows Git Bash) or <skill-dir>\runner\flow.cmd <command> (Windows PowerShell or cmd, including inside Codex; bare bash may resolve to WSL and cannot read C:/ paths) using the hosting agent or operator; Flow does not own the runtime.
Follow the canonical skill dispatch, active card allowed files, gates, and evidence requirements. Keep Claude discovery in its separate .claude/skills path.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

