coding-agent
Delegate coding tasks to Codex, Claude Code, or Pi agents via background host sessions. Use when: (1) building or creating new features or apps, (2) reviewing PRs (spawn in temp dir), (3) refactoring large codebases, (4) iterative coding that needs file exploration. NOT for: simple one-liner fixes (just edit), reading code (use read tool), thread-bound ACP harness requests in chat (for example spawn or run Codex or Claude Code in a Discord thread; use sessions_spawn with runtime:"acp"), or any work in ~/clawd workspace (never spawn agents here). Requires OpenClaw host tools with exec_command plus write_stdin.
89
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly defines its purpose, trigger conditions, and boundaries. The numbered use-cases and explicit exclusions make it highly actionable for skill selection. The description is specific, well-structured, and distinctive enough to avoid conflicts with related coding skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: building/creating features or apps, reviewing PRs (with detail about temp dir), refactoring large codebases, iterative coding with file exploration. Also specifies what NOT to use it for, and names required tools (OpenClaw host tools with exec_command plus write_stdin). | 3 / 3 |
Completeness | Clearly answers both 'what' (delegate coding tasks to Codex/Claude Code/Pi agents via background host sessions) and 'when' with an explicit 'Use when:' clause listing four numbered scenarios, plus a 'NOT for:' section clarifying boundaries. Exceptionally thorough. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'coding tasks', 'Codex', 'Claude Code', 'Pi agents', 'building', 'creating new features', 'apps', 'reviewing PRs', 'refactoring', 'large codebases', 'iterative coding'. Also includes negative triggers to prevent misuse. Good coverage of terms a user would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: delegating to specific agent types (Codex, Claude Code, Pi) via background host sessions. The explicit 'NOT for' section with boundary conditions (simple fixes, reading code, ACP harness requests, ~/clawd workspace) strongly reduces conflict risk with other coding-related skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, highly actionable skill with excellent executable examples covering multiple coding agents and workflows. Its main weaknesses are moderate verbosity (repeated PTY warnings, explanatory asides, a 'Learnings' section that rehashes earlier content) and a monolithic structure that could benefit from splitting detailed workflows into referenced files. The time-sensitive 'Jan 2026' learnings and Pi PR reference are minor concerns.
Suggestions
Reduce PTY repetition: state the tty:true requirement once prominently at the top and remove the ~10 inline reminders like '# remember PTY!' and '# with PTY!'
Move the 'Learnings (Jan 2026)' section content into the relevant sections above rather than repeating it, or remove it entirely since it duplicates earlier guidance
Consider splitting agent-specific sections (Codex CLI, Claude Code, Pi, OpenCode) and advanced workflows (batch PR reviews, parallel worktrees) into referenced files to improve progressive disclosure
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary explanations (e.g., 'Why git init?' and 'Why workdir matters' are things Claude can infer, the 'Learnings' section repeats earlier content, and the humorous asides like 'read your soul docs' add tokens without value). The PTY warning is repeated excessively throughout. | 2 / 3 |
Actionability | Excellent actionability with fully executable, copy-paste-ready commands for every agent type and scenario. Concrete examples cover one-shot tasks, background sessions, PR reviews, parallel workflows, and monitoring — all with specific flags and parameters. | 3 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced (e.g., the parallel issue fixing section has numbered steps from worktree creation through monitoring to cleanup). The background session pattern clearly shows start → monitor → interact → kill lifecycle. Progress update guidelines provide explicit checkpoints for user communication. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and sections, but it's a long monolithic file (~200 lines) with no references to external files for detailed content like the full parameter reference, agent-specific guides, or PR review workflows. The batch PR review and parallel worktree sections could be split out. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 9 / 11 Passed | |
- Repository
- trpc-group/trpc-agent-go
- Commit
0c1ec2b
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.