Menu
Execute a markdown workflow file step by step, emitting a structured trace via `flow workflow report`.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Cut a Flowpad release — bump the version (patch by default; minor/major on request), build the wheel (UI baked in), publish to PyPI, tag + push to GitHub, and validate the install. Then, if the electron/ directory changed since the previous release, trigger the desktop build. Use when asked to deploy/release Flowpad, publish to PyPI, or cut a new version (including a new minor like 0.3.0).
toplog — topic-tracing assistant for debugging. `run` activates the right trace topics for a given issue (in code or tests) so RCA has better traceability; `scan` reconciles the topics referenced in code against the topic catalog; `learn` consolidates post-RCA findings (enrich a topic, add a new one with its trace points, or retire a stale one). Use when debugging a hard failure and you want richer logs before or alongside RCA, when adding or auditing toplog topics, or after proving a root cause to capture the traceability that helped. Also triggers on "turn on tracing for X", "what topics cover Y", "add a toplog topic", or "audit toplog topics".
Root Cause Analyzer — prove the real cause of a failure by finding its
Skill quality lens — review a skill against skill-writing best practices,
Find a product online within a location and price range, verify availability and shipping, and report the findings.
Analyze an agentic execution from its session transcript and produce
| id | d7a727e5-ad32-5bd8-92eb-0c47a38cac4a |
| name | flow |
| description | Execute a markdown workflow file step by step, emitting a structured trace via `flow workflow report`. |
| tags | ["workflow","execution","automation"] |
| allowed-tools | ["Bash","Read"] |
You are executing a markdown workflow file. Read it, execute each step in order, and emit one trace event per step via Bash.
Read on the workflow file so you see line numbers — these are the
anchors you will report against.## Steps. Each top-level bullet is one step;
record its 1-indexed line number.For every step, in order:
flow workflow report --data '{"kind":"step","file":"<ABS_PATH>","line":<N>,"status":"enter"}'
flow workflow report --data '{"kind":"step","file":"<ABS_PATH>","line":<N>,"status":"done","detail":"<short result>"}'
flow workflow report --data '{"kind":"step","file":"<ABS_PATH>","line":<N>,"status":"error","detail":"<short reason>"}'
"status":"skip".--process is optional inside an agentic process — the CLI reads
FLOWPAD_EXECUTION_SCOPE automatically.
If a step invokes another workflow file: emit enter/done for the
calling step using the parent file's path+line, then recurse — Read
the sub-workflow and emit its events with "file" set to the sub-
workflow's absolute path. The (file, line) anchor naturally distinguishes
parent vs. sub-workflow events.
After all steps complete, emit PASSED or FAILED: <short reason> as
your final assistant text.