Two workflows that chain primitives, composed from the skills' own commands - #19
Draft
pablomogamon wants to merge 1 commit into
Draft
Two workflows that chain primitives, composed from the skills' own commands#19pablomogamon wants to merge 1 commit into
pablomogamon wants to merge 1 commit into
Conversation
…mmands price-monitoring (fetch -> extract -> batch): prove the page, prove the structure, estimate before spending, run managed, retry-failed on a schedule. gated-page-extraction (fetch -> browser -> extract): the escalation-only rule end to end - the browser enters only when the cheap step failed with evidence, scripted sessions preferred because they close themselves. Every command line is lifted from the skills (protected-fetch, extract, batch-jobs, interact-browser), so the workflows cannot promise a flag the CLI does not have. Registered in registry/workflows.json; the app's Overview vendors this registry (scripts/sync-agent-catalog.mjs there), so these cards render in the product from this same source. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview's "workflows" were single-tool example prompts typed by hand in the app repo — not workflows, and not faithful to anything the toolkit ships. This adds the real thing on the toolkit side, where it belongs:
--wait-for), prove the structure once (--css … --validate),batch estimatebefore spending,batch create --wait+results,retry-failedon a schedule.browser run script.jsonpreferred because scripted sessions close themselves.Fidelity rule: every command line is lifted verbatim from the skills (
protected-fetch,extract,batch-jobs,interact-browser), so a workflow cannot promise a flag the CLI does not have. Both registered inregistry/workflows.jsonalongsidecompetitor-intelligence, same schema.Why now: the app's Overview stops hand-typing this content — a sync script there (
scripts/sync-agent-catalog.mjs, companion app PR) vendors this registry + the WORKFLOW.md steps and renders them verbatim, so what the product shows and whatzenrows workflow explainsays come from one source.Toolkit suite: 184/184 green.
🤖 Generated with Claude Code