ClawHub

Duel Loop

v1.0.0

彻底断绝主代理长期对话中累积的偏见与情绪对产出的裹挟，确保每次产出忠实于需求本身，不再随对话越长越偏离预期。你只负责提需求和最终验收。传统单agent反复调prompt、人工审核输出的工作流，在这里被架构级消解了。角色隔离的双子代理对抗架构：执行和QA子代理运行在完全架空的环境中，看不到主代理的会话上下文、用户画...

⭐ 0· 44·0 current·0 all-time
by@dexzopiclone
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The skill implements a dispatch → review → accept loop for producing and QA'ing documents. It requests no binaries, env vars, or installs, and the files it reads/writes (templates and drafts/*) are consistent with the stated purpose.
ℹ
Instruction Scope
SKILL.md limits what is passed to subagents (only task-related fragments, TASK_BRIEF ≤ 200 chars) and describes isolated runtimes. This stays within the described scope. Note: the main agent still holds full session context and is responsible for extracting/redacting fragments — that creates a normal risk surface where sensitive data could be injected into drafts if the main agent extracts it.
✓
Install Mechanism
Instruction-only skill with no install spec and no code files. No downloads or external packages; lowest install risk.
✓
Credentials
No environment variables, credentials, or config paths are requested. The declared requirements are proportional to a purely orchestration/QA prompt template skill.
✓
Persistence & Privilege
always is false and the skill relies on runtime subagents (sessions_spawn) which is consistent with its orchestration role. Autonomous invocation is allowed by platform default but is not combined with other elevated privileges here.
Assessment
The design is coherent, but review these operational risks before installing: - Drafts are written to workspace/drafts/<name>-vN.md; ensure that workspace file permissions, retention, and backups meet your privacy requirements (sensitive content may be stored there). - The main agent has full conversation context and is responsible for extracting the TASK_BRIEF: ensure prompts/automation explicitly redact or truncate sensitive data before injecting into subagent prompts. - Test the workflow with non-sensitive examples to verify that the extraction and isolation behave as documented (subagents should not receive extraneous context). - Audit and lock the templates/qa-review-prompt.md file (or review it frequently) to prevent tampering that could change QA behavior. If you need stronger guarantees (no disk persistence, automatic redaction, or encrypted storage), request modifications to the skill to implement them before using with sensitive data.

Like a lobster shell, security has layers — review code before you run it.

latestvk97acx2ypg013rbnmqeb3ejcks84sv82

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments