debug-workflow-conversations

debug-workflow-conversations is a skill for Claude Code, Codex from radiantlogicinc/fastworkflow. It costs 176 tokens per session (2,694 once invoked), scanned A, original, Apache-2.0.

A guide for diagnosing fastWorkflow failures from its SQLite conversation log, a local database that records each turn and processing stage. It traces failures from intent routing and parameter extraction through validation and application code.

In plain words
What is it for?
Use it to locate the observability database, read it safely, follow a turn's span trace, and investigate routing, extracted values, lookups, validation, user questions, or application errors.
Why use it?
The final error often does not reveal which stage went wrong. The recorded trace helps identify the failing stage and the corresponding fix.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/radiantlogicinc/fastworkflow/debug-workflow-conversations
Any agent
npx skills add radiantlogicinc/fastworkflow --skill debug-workflow-conversations
Clone the repo
git clone --depth 1 https://github.com/radiantlogicinc/fastworkflow

Made for: Claude Code, Codex.

Per session 176 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,694 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00176 $0.02694
Opus 5 $0.00088 $0.01347
Sonnet 5 $0.00035 $0.00539
Haiku 4.5 $0.00018 $0.00269

Measured 3d ago against content hash a4ca6b015e2b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

debug-workflow-conversations scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

fastworkflow/skills_for_coding_fastworkflows/debug-workflow-conversations/SKILL.md · 189 lines

How it starts

The opening of the file, as written. The whole thing — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Debugging workflows from conversation logs

Every turn a fastWorkflow workflow executes is recorded — the user's message, the agent's plan, every intent-detection attempt with the classifier's confidence, every extracted parameter, every db_lookup correction, every validation verdict, every ask_user exchange, and the final answer. When a task fails, the log tells you which pipeline stage failed, and each stage has a specific fastWorkflow feature that fixes it. This skill is the map from log to fix.

1. Locate the database

One SQLite database per workflow, under the fastWorkflow state root:

from fastworkflow import state_paths
db_path = state_paths.observability_db("<workflow_folder>")
# typically ~/.local/state/fastworkflow/workflows/<workflow-name>/observability.sqlite3

If the file does not exist, the workflow has never run with observability on (the default under fastworkflow run, run_chatbot, and run_fastapi_mcp). Reproduce the failure first — fastworkflow run_chatbot <workflow> is the fastest way; every chat turn lands in this database immediately.

2. Read it — read-only, always

from fastworkflow.observability_store import ReadOnlyObservabilityStore
store = ReadOnlyObservabilityStore(db_path)

Never instantiate ObservabilityStore to inspect a database. That class is the writer: constructing it creates the file if missing, runs schema migration, and write-probes it. ReadOnlyObservabilityStore opens mode=ro connections and cannot mutate anything. Raw SQL is equally fine (the schema is documented in reference.md):

sqlite3 "file:$DB?mode=ro" "SELECT turn_key, status, success, user_message FROM turns ORDER BY turn_key DESC LIMIT 20"

3. Find the failing turn

store.list_turns(status="failed")                 # turn-level failures
store.list_turns(success=False)                   # any command in the turn failed
store.list_turns(command_name="cancel_order")     # turns that executed a command
store.list_turns(context="TodoList")              # substring match on entry context
turn  = store.get_turn(turn_key)                  # full row incl. record_json
spans = store.get_spans(turn_key)                 # the trace, ordered by start_ns

Read the full file on GitHub · 189 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 189 lines · 176 tokens per session scan A a4ca6b015e2b

Subscribe to this mod's changes

debug-workflow-conversations is a skill published in the GitHub repository radiantlogicinc/fastworkflow (52 stars, last pushed 6d ago), licensed Apache-2.0. It adds 176 tokens to every session and 2,694 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens