New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Flow Next QA

by gmickel in gmickel/flow-next

Live-app QA pass derived from the spec. An agent skill from gmickel/flow-next.

MITAuto-check: notes

Install Flow Next QA

skills CLI
$ npx skills add gmickel/flow-next --skill flow-next-qa -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install gmickel/flow-next flow-next-qa --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/gmickel/flow-next.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/flow-next/codex/skills/flow-next-qa .claude/skills/flow-next-qa && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
flow-next-qa
GitHub stars
707
Token cost
~1.1k tokens
SKILL.md length
391 words
Files
9 (incl. references)
Skills in repo
43
Repo updated
First seen
Licence
MIT

At a glance

Live-app QA pass derived from the spec. An agent skill from gmickel/flow-next.

  • SKILL.md covers The hard rule, Preamble and Arguments
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Flow Next QA is an agent skill from gmickel/flow-next. Live-app QA pass derived from the spec. Drives the running app, files P0/P1/P2 findings with evidence, emits a YES or NO qaverdict receipt.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including reference files (for example `agents/openai.yaml`, `references/autonomous-commit.md` and `references/autonomy.md`).

The repository describes itself as: Faster than your agent alone. And better. A workflow plugin that takes a bug, idea or ticket to a verified pull request: specs, cross-model review by risk, live QA, receipts in… The licence is MIT.

Example prompts

  • “/flow-next-qa”

Requirements

  • Pre-approved tools (allowed-tools): Read, Bash, Grep, Glob, Write, Edit, Task

What it can do on your machine

Read from SKILL.md and the folder at commit 09e291e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Bash
    • Grep
    • Glob
    • Write
    • Edit
    • Task

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Flow Next QA loads about 1.1k tokens when it runs, and up to ~4k if it reads all its reference files. Until then it costs about 38 tokens; SKILL.md has 391 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~38
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Bash, Grep, Glob, Write, Edit, Task

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from gmickel/flow-next at commit 09e291e, republished under its MIT licence (© gmickel). 391 words, ~1,083 tokens.

Download SKILL.mdSave it as .claude/skills/flow-next-qa/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.
name
flow-next-qa
description
Live-app QA pass derived from the spec. Drives the running app, files P0/P1/P2 findings with evidence, emits a YES or NO qa_verdict receipt.
allowed-tools
Read, Bash, Grep, Glob, Write, Edit, Task
user-invocable
false

/flow-next:qa — live-app real-user QA pass

Drive the running app the way an unforgiving real user would, with scenarios taken from the spec, file P0/P1/P2 findings with captured evidence, and end with a YES/NO ship verdict written as a qa_verdict receipt. The spec is the source of intent: acceptance criteria become scenarios, R-IDs become the coverage table, boundaries say what not to test, decision context says what the app should do.

QA is a cheap first live pass over the finished build. It does not replace CI, staging or manual QA, and it does not fix product code: it files, surfaces and hands off. Findings are advisory; the human reviewer and the land gate decide.

It runs when the user invokes it, or as the optional pipeline.qa stage (off | on | auto, default off) that /flow-next:flow runs after all tasks are done and before make-pr. When setting or reading that key, read gate-selection.md; flowctl.md has the config row. Enable the stage only where /flow-next:prime reports the app is QA-ready (seeded data, a documented dev login, a drivable surface, readable runtime evidence); otherwise every run ends BLOCKED.

Read working-rules.md first unless you already have this run; it holds for every step.

The hard rule

SHIP rests on evidence captured from the running app (screenshots, console output, observed state). A SHIP reached by reading the source or the diff, from narration, or from "the code looks right" has broken this. With no reachable app or no driver, the outcome is BLOCKED, never a pass. Reading source to explain a failure you already captured is fine.

Show full SKILL.md (130 more words)Show less

Preamble

flowctl is bundled, not on PATH. Define it once; later blocks here and in workflow.md use $FLOWCTL:

bash
FLOWCTL="${CODEX_HOME:-$HOME/.codex}/scripts/flowctl"
[ -x "$FLOWCTL" ] || FLOWCTL="<plugin-root>/scripts/flowctl"   # <plugin-root> = the directory two levels above this skill's SKILL.md file (the harness gave you that file's absolute path when the skill loaded); substitute it literally
[ -x "$FLOWCTL" ] || FLOWCTL=".flow/bin/flowctl"

This skill runs inline on the host (not forked) so it can ask the user for undocumented facts.

Arguments

The first non-flag token is the spec id. --target <url>, --receipt <path> and --base <ref> take a value (as --flag value or --flag=value). mode:autonomous turns on autonomous mode.

bash
SPEC_ID=""; PREV=""
# No positional parameters: the host rewrites them inside skill code blocks.
# Quote the pasted arguments once so a URL's `&` or `;` stays data.
RAW_ARGS="$ARGUMENTS"
for ARG in $RAW_ARGS; do
  case "$PREV" in
    --target)  QA_TARGET_URL="$ARG"; PREV=""; continue ;;
    --receipt) QA_RECEIPT_OVERRIDE="$ARG"; PREV=""; continue ;;
    --base)    QA_BASE_REF="$ARG"; PREV=""; continue ;;
  esac
  case "$ARG" in
    --target|--receipt|--base) PREV="$ARG" ;;
    --target=*)  QA_TARGET_URL="${ARG#--target=}" ;;
    --receipt=*) QA_RECEIPT_OVERRIDE="${ARG#--receipt=}" ;;
    --base=*)    QA_BASE_REF="${ARG#--base=}" ;;
    mode:autonomous) QA_AUTONOMOUS=1 ;;
    -*) echo "Unknown flag: $ARG (ignored)" >&2 ;;
    *)  [[ -z "$SPEC_ID" ]] && SPEC_ID="$ARG" ;;
  esac
done
[[ -n "$PREV" ]] && echo "Flag $PREV given without a value (ignored)" >&2
[[ "${FLOW_AUTONOMOUS:-}" == "1" ]] && QA_AUTONOMOUS=1
NO_PROMPT=0
[[ "${QA_AUTONOMOUS:-}" == "1" || "${AUTONOMOUS:-}" == "1" ]] && NO_PROMPT=1
export QA_TARGET_URL QA_RECEIPT_OVERRIDE QA_BASE_REF QA_AUTONOMOUS NO_PROMPT

Autonomous mode (NO_PROMPT=1; flow --auto dispatches with mode:autonomous) asks nothing. Each fact the interactive run would ask for is resolved from the spec, config or environment; when it cannot be, the run writes a BLOCKED receipt and exits cleanly. The one exception is an unresolvable spec id, which is an error (non-zero exit, message on stderr).

Now follow workflow.md: discover, derive, prepare, execute, file, verdict.

© gmickel, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 8 other files (references) in plugins/flow-next/codex/skills/flow-next-qa of gmickel/flow-next.

  • SKILL.md
  • agents/openai.yaml
  • references/autonomous-commit.md
  • references/autonomy.md
  • references/bug-filing.md
  • references/drift-notes.md
  • references/prepare-surface.md
  • references/spec-from-branch.md
  • workflow.md

Open the folder on GitHubat commit 09e291e

Compare with similar skills

Flow Next QA next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Flow Next QA compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Flow Next QA this skillgmickel/flow-next707—~1.1kAutomated safety check: NotesMIT
Feishu Driveopenclaw/openclaw392k—~375Automated safety check: PassMIT
Longbridge Derivativessickn33/agentic-awesome-skills47k1 repos~1.1kAutomated safety check: PassMIT
Math Derivation Auditortradecatlabs/vibe-coding-cn17k—~429Automated safety check: PassMIT
Crypto Derivatives StrategiesHKUDS/Vibe-Trading35k—~2.4kAutomated safety check: PassMIT
Electron Drive Skillsickn33/agentic-awesome-skills47k1 repos~2.5kAutomated safety check: PassMIT

Similar skills

  • Feishu Drive

    openclaw/openclaw

    Feishu cloud-storage and comment workflows. An agent skill from openclaw/openclaw.

    392k GitHub stars~375 tokensUpdated yesterday
    Productivity & AutomationAuto-check passed

  • Longbridge Derivatives

    sickn33/agentic-awesome-skills

    Curated upstream guidance for Longbridge Derivatives; use when the workflow matches the user goal.

    47k GitHub starsUsed in 1 repo~1.1k tokens
    Business, Finance & HRAuto-check passed

  • Math Derivation Auditor

    tradecatlabs/vibe-coding-cn

    Constructs honest, checkable derivation chains for formulas and theory notes, and keeps approximations and numerical hints from passing as rigorous proof.

    17k GitHub stars~429 tokensUpdated yesterday
    Research & ScienceAuto-check passed

  • Crypto Derivatives Strategies

    HKUDS/Vibe-Trading

    Covers three crypto-derivatives approaches: perpetual funding-rate arbitrage, futures term-structure trading in contango and backwardation, and options volatility and Greeks analysis.

    35k GitHub stars~2.4k tokensUpdated yesterday
    Business, Finance & HRAuto-check passed

  • Electron Drive Skill

    sickn33/agentic-awesome-skills

    Launch the project's Electron app on a scratch profile and drive it: click, type, screenshot, run renderer or main-process code, read logs.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Testing & QAAuto-check passed

  • Gws Drive Upload

    googleworkspace/cli

    Google Drive: Upload a file with automatic metadata. An agent skill from googleworkspace/cli.

    31k GitHub starsUsed in 1 repo~322 tokens
    Documents & OfficeAuto-check passed

More from gmickel/flow-next

All 43 skills in this repo

  • Flow Next Resolve PR

    gmickel/flow-next

    Resolve PR review feedback. An agent skill from gmickel/flow-next.

    707 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Flow Next Resolve PR

    gmickel/flow-next

    Resolve PR review feedback — fetch unresolved threads, triage, dispatch per-thread resolver agents, validate, commit, reply + resolve via GraphQL.

    707 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Flow Next

    gmickel/flow-next

    Manage .flow/ tasks and specs. An agent skill from gmickel/flow-next.

    707 GitHub stars~1.6k tokensUpdated yesterday
    Auto-check passed

  • Flow Next Audit

    gmickel/flow-next

    Audit .flow/memory/ entries against the current codebase and decide Keep / Update / Consolidate / Replace / Delete / Harden per entry.

    707 GitHub stars~3.1k tokensUpdated yesterday
    Auto-check: notes

  • Flow Next Capture

    gmickel/flow-next

    Save the current conversation as a source-tagged flow-next spec, then offer review or editing.

    707 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check: notes

  • Flow Next Chart

    gmickel/flow-next

    Decision-map discovery for one oversized unclear idea before capture.

    707 GitHub stars~2.7k tokensUpdated yesterday
    Auto-check: notes

Questions about Flow Next QA

What does Flow Next QA do?

Live-app QA pass derived from the spec. An agent skill from gmickel/flow-next. Flow Next QA is an agent skill from gmickel/flow-next. Live-app QA pass derived from the spec.

How do I install Flow Next QA in Claude Code?

Run `npx skills add gmickel/flow-next --skill flow-next-qa -a claude-code`. Or copy the skill folder (plugins/flow-next/codex/skills/flow-next-qa in gmickel/flow-next) into .claude/skills/flow-next-qa in your project. Claude Code loads it when a task matches its description.

How do I install Flow Next QA in Codex?

Run `npx skills add gmickel/flow-next --skill flow-next-qa -a codex`. Or copy the skill folder (plugins/flow-next/codex/skills/flow-next-qa in gmickel/flow-next) into .agents/skills/flow-next-qa in your project. Codex loads it when a task matches its description.

Can I use Flow Next QA in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add gmickel/flow-next --skill flow-next-qa -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/flow-next-qa, .gemini/skills/flow-next-qa, .github/skills/flow-next-qa and .opencode/skills/flow-next-qa in your project.

What does Flow Next QA need to run?

SKILL.md names no scripts, command-line tools or credentials: Flow Next QA is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Bash, Grep, Glob, Write, Edit, Task.

Does Flow Next QA access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Flow Next QA safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Flow Next QA use?

Flow Next QA is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Flow Next QA use?

About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.9k tokens, read only when the agent opens those files.

What are the alternatives to Flow Next QA?

Skills that share tags, products or a category with Flow Next QA: Feishu Drive (openclaw/openclaw, 392k stars), Longbridge Derivatives (sickn33/agentic-awesome-skills, 47k stars), Math Derivation Auditor (tradecatlabs/vibe-coding-cn, 17k stars) and Crypto Derivatives Strategies (HKUDS/Vibe-Trading, 35k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Flow Next QA?

gmickel (a GitHub user) maintains it in gmickel/flow-next, which has 707 GitHub stars. The repository holds 43 skills in this directory. The repository was last updated on October 7, 2026.

Source: gmickel/flow-next on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.