CtrlK
BlogDocsLog inGet started
Tessl Logo

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 or parallel coding with managed worktree isolation when subagents are available, (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, or any work in ~/clawd workspace (never spawn agents here). Requires OpenClaw host tools with exec_command plus write_stdin.

63

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./openclaw/skills/coding-agent/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable content with strong executable examples, weighed down by repetition, a dated Learnings recap, and the absence of validation checkpoints or bundle files for content that would benefit from separation.

Suggestions

Add an explicit validation/verification step after batch or destructive operations (e.g., 'After --yolo runs, diff and run tests before reporting done') to lift workflow_clarity past the cap.

Consolidate the PTY guidance into one section and remove the 'Learnings (Jan 2026)' recap that repeats already-stated points, to reduce token weight.

Split per-agent CLI details and the dated learnings into reference files (e.g. references/agents.md, references/learnings.md) so SKILL.md stays a lean overview.

DimensionReasoningScore

Conciseness

Mostly efficient with tables and copy-paste blocks, but the PTY point is repeated across multiple sections, the 'Learnings (Jan 2026)' block restates already-covered material, and jokey asides add tokens that could be trimmed.

3 / 5

Actionability

Fully executable guidance: concrete exec_command invocations with real flags, parameter/session-tool tables, and copy-paste bash blocks covering one-shot, background, PR review, and parallel cases.

5 / 5

Workflow Clarity

Sequences (start -> monitor -> input -> kill) are present, but batch/destructive operations (parallel PR review, --yolo, kill_session) lack explicit validation or verification checkpoints, so the workflow_clarity cap of 3 applies.

3 / 5

Progressive Disclosure

No bundle files exist, so ~280 lines covering four agents, PR review, parallel worktrees, rules, and a learnings archive are all inlined; clear section headers provide structure, but per-agent detail and the dated Learnings section read like content that belongs in separate files.

3 / 5

Total

14

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-structured description that answers what, when, and when-not with concrete trigger phrases and clear conflict boundaries. Minor room to sharpen the 'what' beyond the umbrella verb 'delegate'.

DimensionReasoningScore

Specificity

Names concrete targets (Codex, Claude Code, Pi) and the mechanism (background host sessions, exec_command, write_stdin) with four use categories, but the core operation is abstracted under the single verb 'delegate', leaving minor gaps versus comprehensive coverage.

4 / 5

Completeness

Explicitly answers both what ('Delegate coding tasks to Codex, Claude Code, or Pi agents via background host sessions') and when ('Use when: (1)... (4)...' plus a 'NOT for' exclusion list) with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ('building or creating new features or apps', 'reviewing PRs', 'refactoring large codebases', 'iterative coding'), with good coverage though a few synonyms and extension-style triggers are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche (coding agents via OpenClaw host sessions) with explicit 'NOT for' boundaries (one-liners, reading code, ~/clawd workspace) that sharply reduce conflict with adjacent skills.

5 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
trpc-group/trpc-agent-go
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.