Skip to content

feat(browser): ret-et-flow debug/fix skill - #3

Merged
simo787c merged 2 commits into
mainfrom
feat/agentbase-browser-ret-et-flow
Jul 27, 2026
Merged

feat(browser): ret-et-flow debug/fix skill#3
simo787c merged 2 commits into
mainfrom
feat/agentbase-browser-ret-et-flow

Conversation

@simo787c

Copy link
Copy Markdown
Contributor

What

PR 3 of 4 for agentbase-browser. Adds ret-et-flow — the skill for fixing an existing flow that returns wrong, empty, or errored output. Mirrors the MCP's revise_flow prompt.

Stacked on #2 (base = feat/agentbase-browser-byg-et-flow) — merge #1 then #2 first.

The skill

skills/ret-et-flow/SKILL.md — the loop is reproduce on a real failing input → localise the exact node:handle with get_execution → make the smallest change → re-run on the same input. Don't rebuild from scratch; don't broaden the flow.

Its value over a generic debugging agent is a symptom → cause → fix table of the AgentBase-specific traps drawn from guidance.py and flow-agent/src/prompts.ts:

  • Empty output / "Intet indhold angivet" after a Hvis/ellers → config missing true_output/false_output → set both, route both branches to one shared field.
  • Raw {placeholder} in output → conditional branches merged into one template → each branch writes the finished text into one shared field.
  • dataurl-vs-text error → a file wired straight into a text input → insert Dokument-OCR, never a python-code type-adapter.
  • Only the first item processed → a list fed to a single-item node → wrap in Løkke Start/Slut.
  • Loop-control not working → Løkke Afbryd/Spring over sitting outside the loop → move it inside.
  • Model returns free text where a system needs fields → missing response_schema.

It names no tool schemas — get_node_type and guide://flow-building stay the live source, so tool-schema drift can't reach it.

Testing

RED/GREEN on an empty-if-else-output scenario. Both baseline and skilled agents debugged rather than rebuilt, but the skill made the agent lead with the exact known root cause and its precise structural fix instead of a diffuse list of guesses.

🤖 Generated with Claude Code

https://claude.ai/code/session_01SYvwyQEa9xsKzsQTwpBuhp

simo787c and others added 2 commits July 27, 2026 10:53
The build-from-scratch skill for agentbase-browser — the intake front half
the MCP's guidance.py (mechanics canon) deliberately lacks.

- skills/byg-et-flow/SKILL.md — interview → confirm the plan in chat → build
  → run on a real sample → iterate. Enforces a five-point intake bar before
  building (process+rules, variants, a real sample input, output+audience,
  Human-in-the-Loop placement) and the chat-checkpoint discipline (the canvas
  is invisible in another tab). Hands off to the MCP mechanics: read
  guide://flow-building, confirm handles with get_node_type, lay the whole
  graph in one set_flow rather than clobber-prone incremental edits.
- skills/byg-et-flow/references/flow-eksempler.md — four Danish flow shapes
  distilled from guidance.py EXAMPLES + docs relationships.md (document →
  structured data → spreadsheet; sort a document pile; loop over a list;
  conditional branching), each pointing at the live example:// resource and
  get_node_type for exact handles, so tool-schema drift can't reach the skill.

RED/GREEN tested: without the skill a fresh agent gathered only a partial
intake (missed variants and the approval step); with it, the full five-point
intake plus confirm-in-chat/run-on-sample loop.

Co-Authored-By: Claude <noreply@anthropic.com> via Dash <dash@syv.ai>
Claude-Session: https://claude.ai/code/session_01SYvwyQEa9xsKzsQTwpBuhp
The debug skill for agentbase-browser — reproduce, localise, smallest fix,
re-run. Mirrors the MCP's revise_flow prompt and folds in the concrete
failure catalogue from guidance.py + flow-agent/src/prompts.ts.

- skills/ret-et-flow/SKILL.md — the fault-finding loop (reproduce on a real
  failing input → localise the exact node:handle with get_execution → make the
  smallest change → re-run on the same input) plus a symptom→cause→fix table of
  the AgentBase-specific traps a generic agent won't know: empty output after a
  Hvis/ellers (config missing true_output/false_output → set both, route both
  branches to one shared field); raw {placeholder} (conditional branches merged
  into one template); dataurl→text needs Dokument-OCR not a code node; a list
  fed to a single-item node needs a Løkke; loop-control nodes must sit inside
  the loop; missing response_schema. Names no tool schemas — get_node_type and
  guide://flow-building stay the live source, so drift can't reach it.

RED/GREEN tested on an empty-if-else-output scenario: both baseline and
skilled agents debugged rather than rebuilt, but the skill made the agent lead
with the exact known root cause and its precise structural fix instead of a
diffuse list of guesses.

Co-Authored-By: Claude <noreply@anthropic.com> via Dash <dash@syv.ai>
Claude-Session: https://claude.ai/code/session_01SYvwyQEa9xsKzsQTwpBuhp
@simo787c
simo787c marked this pull request as ready for review July 27, 2026 09:45
@simo787c
simo787c changed the base branch from feat/agentbase-browser-byg-et-flow to main July 27, 2026 09:45
@simo787c
simo787c merged commit b8506aa into main Jul 27, 2026
@simo787c
simo787c deleted the feat/agentbase-browser-ret-et-flow branch July 27, 2026 09:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant