Install
$ agentstack add skill-dioptx-weft-wf-step ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Advance Weft Workflow Step
Transition the current step to a new status.
Arguments
$ARGUMENTS
Parsing
Parse the arguments flexibly. The user may say:
/wf-step complete "planning done"— standard form/wf-step doneor/wf-stepwith no args — treat ascomplete/wf-step skip not needed— skip with reason/wf-step failed, try again— treat asretryif step is failed, orfailif running/wf-step complete 3or/wf-step complete next 3— bulk complete N steps
Map natural language to actions: | User says | Action | |-----------|--------| | done, finished, complete, next | complete | | skip, not needed, pass | skip | | failed, broken, error | fail | | retry, again, redo | retry | | again, loop, iterate, continue loop, not done yet, issues remain | loop-continue | | done looping, exit loop, loop done, clean, all clear | loop-done |
Loop disambiguation: If the current step has a loop_back_to field, prefer loop actions over regular ones. "again" on a loop step means loop-continue, not retry. "done" on a loop step means loop-done, not complete. If the user explicitly says "complete" or "skip", use those literally even on loop steps.
Single step transition
python3 "${CLAUDE_PLUGIN_ROOT}/core/cli.py" step
Bulk transitions
If the user specifies a count (e.g., "complete 3"), loop:
for i in 1 2 3; do
python3 "${CLAUDE_PLUGIN_ROOT}/core/cli.py" step complete "bulk advance"
done
Stop looping if any step fails or the workflow completes.
After transition
- Display the updated workflow checklist.
- If the workflow just completed, congratulate and summarize what was accomplished.
- If a step failed with
blockpolicy, explain options:/wf-step retryor/wf-abort. - If the next step has guards, explain what commands are blocked.
- If the next step has a description in the template, mention what it expects.
After loop-continue
- Show "Loop iteration N/M" with the current count and max.
- List which steps were reset back to pending.
- If the exit condition is defined, remind the user what needs to be true to exit.
After loop-done
- Show "Exited loop after N iterations."
- Show the next step info as normal.
Loop max exceeded
- If loop-continue triggers maxiterations, the step fails per its onfail policy.
- Explain: "Loop hit max iterations (N). Workflow blocked — use
/wf-step retryto reset or/wf-abort."
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: dioptx
- Source: dioptx/weft
- License: MIT
- Homepage: https://github.com/dioptx/weft
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.