Skip to content

docs(skills): steer build-workflow away from legacy blocks #13

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
waleedlatif1 merged 1 commit into from
Oct 29, 2026
Merged

docs(skills): steer build-workflow away from legacy blocks #13

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion skills/build-workflow/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -142,8 +142,11 @@ are regenerated; do not recreate that flow with a sequence of graph edits.
`sim --output json blocks get <blockId>`.
- Use the returned block id, operation ids, input ids, modes, conditions, credential fields, and
outputs exactly. Never invent them from a display name or underlying tool id.
- Remembered block ids are often the legacy version (`table` instead of `table_v2`, `router`
instead of `router_v2`). A block whose `blocks get` detail carries `sunset` only keeps existing
workflows running: never add one or switch a block to one; build with its `sunset.replacedBy`.
- Preserve an existing block's saved type/version when editing; an unversioned catalog lookup can
resolve a newer definition.
resolve a newer definition. If it carries `sunset`, name its `replacedBy` to the user.
- Inspect `tools list` or `tools get` only when the block response points to a tool and its parameter
or output contract is needed.
- Resolve credentials and resource identifiers before writing them into a graph. Do not embed raw
Expand Down
Loading