Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Developer Tools
adversarial-coach
Adversarial implementation review based on Block's g3 dialectical autocoding research. Use when validating implementation completeness against requirements with fresh objectivity.
skill openclawclawhub Free
Adversarial implementation review based on Block's g3 dialectical autocoding research. Use when validating implementation completeness against requirements with fresh objectivity.
โฌ 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
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
- 0.9.0
Provenance
- Publisher
- killerapp
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Usage
/coach [requirements-file] /coach - Infer requirements from context /coach requirements.md - Validate against specific file
Coach-Player Loop
You orchestrate this dialectical loop between implementing agent (player) and reviewer (coach): You (player) implement features /coach invokes adversarial review with independent evaluation of compliance to requirements Coach returns: IMPLEMENTATION_APPROVED or specific fixes Address feedback, loop until approved
Step 1: Identify Requirements
Check (in order): Specified requirements file or issue/ticket mentioned requirements.md, REQUIREMENTS.md, SPEC.md, TODO.md Conversation context; ask user if nothing found
Step 2: Adversarial Review
Review with fresh objectivity - discard prior knowledge, don't rationalize shortcuts. Check CategoryItemsRequirementsEach item: implemented or missing with specific gapCompilationCompiles? Tests pass? Runs?Common GapsAuth on endpoints, token refresh endpoint, HTTPS, bcrypt for passwords, error handling, input validationFunctionalTest actual flows (not just compilation), verify edge cases workTest CoverageAuth error cases (401/403), token expiry, invalid inputs, rate limits
Step 3: Return Verdict
- If approved (>95% complete):
- IMPLEMENTATION_APPROVED
- [Requirement 1]: Verified
- [Requirement 2]: Verified
- Compilation: Success
- Tests: All passing
- If fixes needed:
- REQUIREMENTS COMPLIANCE:
- [Requirement]: Implemented
- [Requirement]: Missing - [specific gap]
- IMMEDIATE ACTIONS NEEDED:
- 1. [Specific fix with file/line if known]
- 2. [Specific fix]
Key Principles
Rigorous but fair: Catch real gaps (security, logic, data flow), not style preferences Functionality over aesthetics; always flag security issues (auth, crypto, validation) Concise: Bullets, not essays; specific issues, not vague concerns No file contents or verbose analysis in output Fresh context is your superpower: Review as if you've never seen this code; validate against requirements, not intentions
Magic Signal
IMPLEMENTATION_APPROVED = termination signal Only use when: all requirements met, code compiles/runs, tests pass, no significant gaps. If in doubt, don't approve.
Minimal Example
- User: /coach SPEC.md
- Claude:
- REQUIREMENTS COMPLIANCE:
- User registration endpoint (bcrypt hashing)
- Login with JWT tokens
- Logout endpoint - not implemented
- Token refresh - missing /auth/refresh endpoint
- IMMEDIATE ACTIONS NEEDED:
- 1. Add POST /auth/logout endpoint
- 2. Add POST /auth/refresh for token renewal
- 3. Add tests for 401 on expired tokens
- ---
- User: [fixes] /coach SPEC.md
- Claude:
- IMPLEMENTATION_APPROVED
- All auth endpoints verified (register, login, logout, refresh)
- 18 tests passing including auth error cases
Research
Paper: Adversarial Cooperation in Code Synthesis Implementation: g3 Key insight: Discard implementing agent's self-report; perform independent evaluation against requirements.
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
1 Docs
- SKILL.md