# Send Soulforge to your agent Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually. ## Fast path - Download the package from Yavira. - Extract it into a folder your agent can access. - Paste one of the prompts below and point your agent at the extracted folder. ## Suggested prompts ### New install ```text I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete. ``` ### Upgrade existing ```text I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run. ``` ## Machine-readable fields ```json { "schemaVersion": "1.0", "item": { "slug": "soulforge", "name": "Soulforge", "source": "tencent", "type": "skill", "category": "开发工具", "sourceUrl": "https://clawhub.ai/jamesrp13/soulforge", "canonicalUrl": "https://clawhub.ai/jamesrp13/soulforge", "targetPlatform": "OpenClaw" }, "install": { "downloadUrl": "/downloads/soulforge", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=soulforge", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "packageFormat": "ZIP package", "primaryDoc": "SKILL.md", "includedAssets": [ "SKILL.md", "references/workflow-format.md" ], "downloadMode": "redirect", "sourceHealth": { "source": "tencent", "slug": "soulforge", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-05-09T07:52:13.754Z", "expiresAt": "2026-05-16T07:52:13.754Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=soulforge", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=soulforge", "contentDisposition": "attachment; filename=\"soulforge-2.0.1.zip\"", "redirectLocation": null, "bodySnippet": null, "slug": "soulforge" }, "scope": "item", "summary": "Item download looks usable.", "detail": "Yavira can redirect you to the upstream package for this item.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/soulforge" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] } }, "links": { "detailUrl": "https://openagent3.xyz/skills/soulforge", "downloadUrl": "https://openagent3.xyz/downloads/soulforge", "agentUrl": "https://openagent3.xyz/skills/soulforge/agent", "manifestUrl": "https://openagent3.xyz/skills/soulforge/agent.json", "briefUrl": "https://openagent3.xyz/skills/soulforge/agent.md" } } ``` ## Documentation ### Soulforge (Effective Use Guide) This is not a full engine reference. This is the operating playbook for getting high-quality autonomous coding outcomes with Soulforge. ### Core Operating Model Use Soulforge when you want: plan → implement → verify/test → PR → review/fix loops with minimal babysitting. Preferred workflows: feature-dev for end-to-end feature delivery bugfix for diagnose-first, surgical fixes review-loop for tightening an existing PR until clean ### Golden Rules (Most Important) Never run from repo main checkout. Soulforge now enforces this guardrail. Always isolate work in worktrees. Default base: /worktrees/ Keep tasks tightly scoped. Specific issue, explicit acceptance criteria, explicit DO-NOT list. Treat review findings with discipline. FIX in-scope issues. Mark genuine extras as SEPARATE. Use callback-exec only. HTTP callback mode is removed. ### Workdir / Worktree safety If --workdir is omitted, Soulforge can auto-provision a worktree under /worktrees/.... Main checkout is blocked (including bare+worktree edge cases). Dirty worktrees are rejected for run start. Out-of-base workdirs are blocked unless explicitly overridden. ### Checkpoint model approve/reject is gone. Use structured completion via soulforge complete .... Pause checkpoints are type: pause. ### Callback model Use --callback-exec. Template vars include: {{run_id}}, {{step_id}}, {{step_status}}, {{status}}, {{task}} {{callback_message}} (step-level, preferred) {{prompt}} remains for backward compatibility in pause scenarios ### Feature build soulforge run feature-dev "Implement . Constraints: max 2 stories. DO NOT refactor unrelated modules." \\ --workdir /abs/path/to/repo/worktrees/feat-xyz \\ --callback-exec 'openclaw agent --session-key "agent:cpto:slack:channel:c0af7b05h28" --message "Soulforge {{run_id}} {{step_id}} {{step_status}}" --deliver' ### Bugfix soulforge run bugfix "Fix with failing test first; minimal patch only." \\ --workdir /abs/path/to/repo/worktrees/fix-xyz \\ --callback-exec 'openclaw agent --session-key "agent:cpto:slack:channel:c0af7b05h28" --message "Soulforge {{run_id}} {{step_id}} {{step_status}}" --deliver' ### Review-only tightening on an existing PR soulforge run review-loop "Review PR #123 and fix only in-scope findings." \\ --workdir /abs/path/to/repo/worktrees/pr-123 \\ --var pr_number=123 \\ --callback-exec 'openclaw agent --session-key "agent:cpto:slack:channel:c0af7b05h28" --message "Soulforge {{run_id}} {{step_id}} {{step_status}}" --deliver' ### 1) Give a tight task contract Include: target issue/PR URL explicit in-scope list explicit out-of-scope list objective success criteria ### 2) Keep iteration loops short If a PR loops repeatedly: create/update .soulforge-progress.md in worktree with exact outstanding fixes run review-loop constrained to remaining findings ### 3) Handle gates like an operator, not a coder At review gate: move in-scope defects to FIX separate unrelated ideas into follow-up issues avoid “while we’re here” drift ### 4) Expect long fix steps; optimize signal Long fix steps are normal for real refactors. Your job is quality control at gates, not interrupting active runs. ### Practical Triage Heuristic When code-review returns findings: High/Medium tied to original issue: FIX now Low tied to original issue correctness: usually FIX now Anything outside scope: SEPARATE ### Anti-Patterns (Avoid) Running multiple workflows in the same checkout Allowing scope creep in repeated review-fix loops Merging with known Highs because “tests pass” Treating this skill as generic Soulforge docs instead of an execution playbook ### Minimal Status Workflow for Operator Start run Wait for review gate Triage with strict scope discipline Repeat until pass Merge Pull main + build + npm link + daemon restart (when local runtime should track latest) ### Notes If loops hit max_loops, spawn a fresh constrained review-loop run with a scope lock file. For long-running initiatives, keep a brief run ledger in the channel (run id → PR → status). ## Trust - Source: tencent - Verification: Indexed source record - Publisher: jamesrp13 - Version: 1.4.1 ## Source health - Status: healthy - Item download looks usable. - Yavira can redirect you to the upstream package for this item. - Health scope: item - Reason: direct_download_ok - Checked at: 2026-05-09T07:52:13.754Z - Expires at: 2026-05-16T07:52:13.754Z - Recommended action: Download for OpenClaw ## Links - [Detail page](https://openagent3.xyz/skills/soulforge) - [Send to Agent page](https://openagent3.xyz/skills/soulforge/agent) - [JSON manifest](https://openagent3.xyz/skills/soulforge/agent.json) - [Markdown brief](https://openagent3.xyz/skills/soulforge/agent.md) - [Download page](https://openagent3.xyz/downloads/soulforge)