メニュー
Replay a SwooshFlow workflow run to debug non-determinism, tool failures, or audit divergence. Use when a workflow produced unexpected output, when "the same input gave a different result", or when investigating a /why response that points at a flow trace.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | replay-workflow |
| description | Replay a SwooshFlow workflow run to debug non-determinism, tool failures, or audit divergence. Use when a workflow produced unexpected output, when "the same input gave a different result", or when investigating a /why response that points at a flow trace. |
SwooshFlow records a deterministic trace of every workflow execution. Every workflow is replayable; this is engineering rule #4.
humanOnly approval inside a workflow looked wrong; replay shows the exact tool input that was presented.| Engine | Purpose |
|---|---|
WorkflowExecutionEngine | Live runs. Writes the trace. |
WorkflowDryRunEngine | Plans without side effects. Use to preview before approving destructive workflows. |
WorkflowReplayEngine | Replays a recorded trace deterministically. |
All three live in Sources/SwooshFlow/.
swift run swoosh memory list --kind workflow-trace | head -20
/why surface.WorkflowReplayEngine:
Tests/SwooshFlowTests/WorkflowReplayTests.swift for the canonical pattern.swoosh subcommand — write the replay test instead, that's the supported entry point today.Date() in their Output. Replace with explicit at: parameter.Set ordering — collections must be [String] sorted, not Set<String>, for any output that crosses the boundary.Sources/SwooshFlow/WorkflowReplayRun.swift — the type holding a replay-in-progress.Sources/SwooshFlow/WorkflowExecutionTypes.swift — the trace event schema./why) — these two together are the agent's accountability story.Multi-file checklist for adding a new SwooshPermission case. Use when adding a permission, exposing a new capability that needs firewall gating, or wiring a new Scout source / tool family / API surface that requires its own grant. Encodes the enum + profile grants + docs + tool wiring + test path so nothing is forgotten.
Interact with Jupiter Lend Protocol. Read-only SDK (@jup-ag/lend-read) for querying liquidity pools, lending markets (jlTokens), and vaults. Write SDK (@jup-ag/lend) for lending (deposit/withdraw) and vault operations (deposit collateral, borrow, repay, manage positions).
Migration guide from Jupiter Metis (v1) or Ultra to Swap API v2. Use when migrating existing Jupiter swap integrations, updating base URLs, or transitioning from quote+swap-instructions to the unified build endpoint.
Use when a user mentions Jupiter token verification, VRFD eligibility, paying 1000 JUP to verify a token, submitting a verification request, or updating metadata via the Jupiter express verification flow.
Use Bags for Solana token launch planning, agent authentication, launch intent creation, and launch transaction creation through the official Bags API.
Use Flap for BNB Chain token trading, wallet and bot integrations, token-launcher flows, VaultPortal launches, deployed contract references, and Blink-style surfaces.