coding-agent

Delegate coding tasks to Codex, Claude Code, or Pi agents via background process. Use when: (1) building/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), or any work in ~/clawd workspace (never spawn agents here). Requires a bash tool that supports pty:true.

Quality

88%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Critical

Do not install without reviewing

Quality

Content

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 concrete examples and clear multi-step workflows for delegating coding tasks to various agents. Its main weaknesses are moderate verbosity (humorous asides, explanations of concepts Claude knows like PTY, redundant tool parameter documentation) and a monolithic structure that could benefit from splitting reference material into separate files. The time-sensitive 'Learnings (Jan 2026)' section and specific PR numbers add some fragility.

Suggestions

Remove or drastically shorten the bash tool parameters and process tool actions tables — Claude knows its own tool interface; focus only on non-obvious parameters like pty:true.

Extract the per-agent reference sections (Codex flags, Claude Code, OpenCode, Pi) into a separate AGENTS.md reference file and link to it from the main skill.

Cut the humorous asides ('like your soul.md 😅', the space lobster haiku, 'Sass works') and explanatory text about what PTY is — these waste tokens without adding actionable guidance.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient with good code examples, but includes unnecessary content: explaining what PTY is, the emoji-heavy tone, the joke about space lobsters, the 'Sass works' learning, and the humorous asides ('like your soul.md 😅') waste tokens. The bash tool parameter table and process tool actions table document tool capabilities Claude likely already knows.	2 / 3
Actionability	Excellent actionability throughout — every section provides copy-paste-ready bash commands with correct flags, concrete examples for one-shot tasks, background monitoring, PR reviews, parallel workflows, and git worktree patterns. The examples are specific and executable.	3 / 3
Workflow Clarity	Multi-step workflows are clearly sequenced with numbered steps (e.g., the parallel issue fixing section: create worktrees → launch agents → monitor → create PRs → cleanup). Monitoring/polling serves as validation checkpoints, and the rules section provides clear constraints. The progress updates section adds a feedback loop for user communication.	3 / 3
Progressive Disclosure	The content is well-structured with clear section headers and logical grouping, but it's a long monolithic file (~200+ lines) with no references to external files. The bash tool parameters table, process tool actions table, and detailed per-agent sections could be split into separate reference files. No bundle files exist to offload content to.	2 / 3
	Total	10 / 12 Passed

Description

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 communicates what the skill does (delegates coding tasks to specific agents via background processes), when to use it (four explicit scenarios), and when NOT to use it (three anti-patterns). The description is concise yet comprehensive, uses natural trigger terms, and occupies a distinct niche that minimizes conflict with other skills.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: building/creating new features or apps, reviewing PRs, refactoring large codebases, iterative coding with file exploration. Also specifies anti-patterns (simple one-liner fixes, reading code) and technical requirements (bash tool with pty:true).	3 / 3
Completeness	Clearly answers both 'what' (delegate coding tasks to agents via background process) and 'when' with an explicit 'Use when:' clause listing four trigger scenarios, plus a 'NOT for:' section clarifying when not to use it. This is exemplary completeness.	3 / 3
Trigger Term Quality	Includes strong natural trigger terms users would say: 'coding tasks', 'Codex', 'Claude Code', 'agents', 'building', 'creating', 'new features', 'apps', 'reviewing PRs', 'refactoring', 'codebases', 'spawn'. The mention of specific agent names (Codex, Claude Code, Pi) adds excellent keyword coverage.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive — focuses specifically on delegating to background coding agents (Codex, Claude Code, Pi), which is a clear niche. The explicit 'NOT for' section further reduces conflict risk by distinguishing it from simple editing or code reading skills.	3 / 3
	Total	12 / 12 Passed

Validation

81%

Warnings & errors only

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: attilaczudor/Test
Commit: b4fc4af

Reviewed: 2 months ago

Table of Contents

Discovery Implementation Validation

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.