Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub Β· Developer Tools
Soulforge
Dispatch multi-step coding workflows to Claude Code CLI or Codex CLI from YAML definitions via a persistent background daemon. Use when: (1) implementing a f...
skill openclawclawhub Free
Dispatch multi-step coding workflows to Claude Code CLI or Codex CLI from YAML definitions via a persistent background daemon. Use when: (1) implementing a f...
β¬ 0 downloads β
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md, references/workflow-format.md
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- 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.
New install
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
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.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.4.1
Provenance
- Publisher
- jamesrp13
- Source page
- View original listing
- Canonical URL
- Open canonical page
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: <repo>/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 <repo>/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 <issue-url>. 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 <issue-url> 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).
Category context
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
2 Docs
- SKILL.md
- references/workflow-format.md