# Send adversarial-coach 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": "adversarial-coach",
    "name": "adversarial-coach",
    "source": "tencent",
    "type": "skill",
    "category": "开发工具",
    "sourceUrl": "https://clawhub.ai/killerapp/adversarial-coach",
    "canonicalUrl": "https://clawhub.ai/killerapp/adversarial-coach",
    "targetPlatform": "OpenClaw"
  },
  "install": {
    "downloadUrl": "/downloads/adversarial-coach",
    "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=adversarial-coach",
    "sourcePlatform": "tencent",
    "targetPlatform": "OpenClaw",
    "packageFormat": "ZIP package",
    "primaryDoc": "SKILL.md",
    "includedAssets": [
      "SKILL.md"
    ],
    "downloadMode": "redirect",
    "sourceHealth": {
      "source": "tencent",
      "status": "healthy",
      "reason": "direct_download_ok",
      "recommendedAction": "download",
      "checkedAt": "2026-05-07T17:22:31.273Z",
      "expiresAt": "2026-05-14T17:22:31.273Z",
      "httpStatus": 200,
      "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=afrexai-annual-report",
      "contentType": "application/zip",
      "probeMethod": "head",
      "details": {
        "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=afrexai-annual-report",
        "contentDisposition": "attachment; filename=\"afrexai-annual-report-1.0.0.zip\"",
        "redirectLocation": null,
        "bodySnippet": null
      },
      "scope": "source",
      "summary": "Source download looks usable.",
      "detail": "Yavira can redirect you to the upstream package for this source.",
      "primaryActionLabel": "Download for OpenClaw",
      "primaryActionHref": "/downloads/adversarial-coach"
    },
    "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/adversarial-coach",
    "downloadUrl": "https://openagent3.xyz/downloads/adversarial-coach",
    "agentUrl": "https://openagent3.xyz/skills/adversarial-coach/agent",
    "manifestUrl": "https://openagent3.xyz/skills/adversarial-coach/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/adversarial-coach/agent.md"
  }
}
```
## 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.
## Trust
- Source: tencent
- Verification: Indexed source record
- Publisher: killerapp
- Version: 0.9.0
## Source health
- Status: healthy
- Source download looks usable.
- Yavira can redirect you to the upstream package for this source.
- Health scope: source
- Reason: direct_download_ok
- Checked at: 2026-05-07T17:22:31.273Z
- Expires at: 2026-05-14T17:22:31.273Z
- Recommended action: Download for OpenClaw
## Links
- [Detail page](https://openagent3.xyz/skills/adversarial-coach)
- [Send to Agent page](https://openagent3.xyz/skills/adversarial-coach/agent)
- [JSON manifest](https://openagent3.xyz/skills/adversarial-coach/agent.json)
- [Markdown brief](https://openagent3.xyz/skills/adversarial-coach/agent.md)
- [Download page](https://openagent3.xyz/downloads/adversarial-coach)