Tagline: Stop your AI agent from faking 'done'
I have watched an AI coding agent finish a task, report it as done, and leave behind code that did not actually do what was asked. The report looked confident. The work was not finished. That gap — between a claim of "done" and work that holds up — is what FlowSkill exists to close.
What FlowSkill is
FlowSkill is an open-source gated build harness for AI coding agents. It wraps your agent in a six-gate pipeline. Every stage must pass before work advances — and a kill is a valid outcome. If a stage cannot pass, the work stops there instead of moving on with a polished-looking result.
Two kinds of gate do the checking:
-
A mechanical gate (
flow.sh) — checks that can be run and verified, not just asserted. -
A semantic gate (
SKILL.md) — checks whether the work actually matches what was asked.
Either gate can stop the pipeline. That is the point: a stage that fails should fail loudly, early, rather than surfacing later as a bug someone else has to untangle.
Receipts, not claims
FlowSkill produces receipts: a record of what passed, what failed, and what was killed, so you can inspect the run instead of taking the agent's word for it. You can see the receipts approach on the project site at https://flowskill.io.vn, along with a 75-second demo.
What it works with
Per the launch description, FlowSkill offers one-command install and works with Claude Code, Codex, and Cursor.
What it does not promise
A gate can only check what it is built to check. FlowSkill does not guarantee that gated work is correct in every sense, and it does not replace reading the code, running it yourself, or reviewing what an agent produced. A passing gate means the stage met its checks — nothing more. If you try it and a gate blocks work you believe is fine, that friction is part of the design, and it is worth reporting as an issue so the checks can improve.
FlowSkill is version 1.0.0. The repository is public at https://github.com/manhquydev/flow-skill — you can read the code, the gates, and the receipts format before deciding whether it fits how you work.
Launch day — November 3
FlowSkill launches on Product Hunt on Tuesday, November 3. If you have ever been burned by a confident "done" that was not done, I would like to hear about it: what is the worst "done" your agent ever faked?
You can follow the project on dev.to at @flowskill, and find the launch on Product Hunt on November 3. Feedback — especially cases where a gate got it wrong — is welcome.
Top comments (0)