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.

Install with Tessl CLI

npx tessl i github:attilaczudor/Test --skill coding-agent

What are skills?

Review — 77%

Does it follow best practices?

If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:

npx tessl skill review --optimize ./path/to/skill

Learn more

Validation — 9 / 11 Passed

Validation for skill structure

SKILL.md

Review

Evals

Discovery

N/A

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

Something went wrong

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 highly actionable skill with excellent workflow clarity and concrete, executable examples for spawning and managing coding agents. The main weaknesses are moderate verbosity (anecdotes, explanations of concepts Claude knows, emoji commentary) and a monolithic structure that could benefit from splitting agent-specific details into separate files. The PTY emphasis and safety rules are well-placed and critical.

Suggestions

Remove the 'Learnings (Jan 2026)' section - the haiku anecdote and 'git repo required' explanation add tokens without actionable value

Move agent-specific sections (Codex CLI, Claude Code, OpenCode, Pi) to separate reference files and keep only quick-start examples in SKILL.md

Trim explanatory comments like 'Why git init?' and 'Why workdir matters' - Claude understands these concepts

Dimension	Reasoning	Score
Conciseness	Generally efficient with good code examples, but includes some unnecessary content like the 'Learnings' section with haiku anecdotes, explanations of why git init is needed (Claude knows this), and the emoji-heavy commentary that adds tokens without value.	2 / 3
Actionability	Excellent executable examples throughout - copy-paste ready bash commands with proper flags, clear parameter tables, and concrete patterns for one-shot tasks, background monitoring, PR reviews, and parallel workflows.	3 / 3
Workflow Clarity	Multi-step processes are clearly sequenced with numbered steps (worktree workflow, PR review workflow), explicit monitoring checkpoints (process action:poll/log), and clear feedback loops for background task management.	3 / 3
Progressive Disclosure	Content is well-organized with clear sections and headers, but it's a monolithic document that could benefit from splitting detailed agent-specific content (Codex, Claude Code, Pi) into separate reference files. The inline tables and extensive examples make it longer than necessary for a SKILL.md overview.	2 / 3
	Total	10 / 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

Reviewed: 14 days 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.