CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

delegate-claude

Delegate a bounded implementation, prototype, benchmark, or file artifact to Claude Code, which owns the reasoning and delivery in the current checkout or a selected standalone clone, directing a Codex helper as sole code writer for substantial changes. Use when an authorized task benefits from Claude's reasoning, design judgment, or taste, or when asked to delegate execution to Claude. Answer-only investigations, recommendations, and text drafts belong to consult-claude.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

81%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.

A well-engineered workflow skill: fully executable commands, a clearly sequenced delegation lifecycle with strong validation checkpoints and feedback loops, and good cross-file delegation of shared detail. Its main weakness is conciseness — resume/model rules recur across sections and some deep mechanics could be trimmed or split out.

Suggestions

Consolidate the resume rules into a single 'Resumes' subsection: the instruction to repeat nondefault --model/--effort, --workspace, --codex, and write-root choices currently appears in at least three places across 'Dispatch and continue'.

Move or tighten the deep sandbox and write-root mechanics (e.g., symlink resolution rules, which shell variables the sandbox unsets) into a short reference file, keeping SKILL.md focused on the decision-relevant facts of the dispatch workflow.

Reference [Codex assistance](../consult-claude/references/codex-assistance.md) once at first mention instead of twice ('described in' and again as 'Read ... before enabling it').

DimensionReasoningScore

Conciseness

The body is information-dense with no basic-concept padding, but the resume/model-flag rules are repeated across sections ("Repeat any --workspace, --codex and write-root choices", "Repeat any deliberate nondefault --model or --effort on each follow-up", "Repeat the same --codex capability, helper model, limits and write roots on parent resumes"), [Codex assistance] is linked twice, and passages such as sandbox variable behavior and write-root symlink resolution could be tightened. This fits "mostly efficient but could be tightened" better than the minor-instances anchor.

3 / 5

Actionability

Provides copy-paste ready commands for the common cases: two full launcher invocations with all flags, "git clone --no-local /absolute/source/checkout /absolute/worker/clone", and hardened acceptance-inspection commands ("git -c core.fsmonitor= -c core.hooksPath=/dev/null diff --no-ext-diff --no-textconv <recorded-baseline>"). A concrete example brief and explicit documentation of --workspace, --codex, --codex-model, --resume, --dry-run, and --codex-write-root round out fully executable guidance.

5 / 5

Workflow Clarity

The macro sequence (brief, choose checkout, dispatch, resume, accept) is clearly sectioned with explicit validation checkpoints: "Before dispatch, record git status", "A zero process exit alone does not establish completion", "reproduce the checks that decide acceptance, especially those Claude could not run", plus an explicit error-recovery feedback loop ("For a failed acceptance check, send the evidence and a focused correction to the same session") and concrete stop conditions.

5 / 5

Progressive Disclosure

Well-organized sections, and shared detail is delegated through clearly signaled one-level-deep links ([Codex assistance](../consult-claude/references/codex-assistance.md), [consult-claude](../consult-claude/SKILL.md), the account-setup anchor) rather than duplicated inline. At roughly 250 lines, deep policy detail (sandbox internals, write-root resolution rules) stays in the body where a reference file would keep SKILL.md closer to an overview, leaving minor organization gaps.

4 / 5

Total

17

/

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 description: it states concrete deliverable types and the ownership model in third-person imperative voice, gives an explicit "Use when" clause with natural trigger phrases, and cleanly boundaries itself against consult-claude. The only room for improvement is broader synonym coverage and fuller enumeration of the skill's capabilities.

DimensionReasoningScore

Specificity

Lists several concrete actions and artifact types ("Delegate a bounded implementation, prototype, benchmark, or file artifact", "directing a Codex helper as sole code writer") with concrete delivery mechanics, matching the several-specific-actions-with-minor-gaps anchor. It stops short of comprehensive capability coverage since checkout selection, acceptance, and resume mechanics are only implied.

4 / 5

Completeness

Explicitly answers what ("Delegate a bounded implementation... which owns the reasoning and delivery in the current checkout or a selected standalone clone") and when ("Use when an authorized task benefits from Claude's reasoning... or when asked to delegate execution to Claude") with concrete trigger phrases. The "when" clause is explicit and specific, not merely present-but-improvable, matching the top anchor.

5 / 5

Trigger Term Quality

Good natural keyword coverage including the direct phrase "delegate execution to Claude" plus "implementation", "prototype", "benchmark", and "Claude's reasoning, design judgment, or taste". A few natural variants users might say (e.g., "hand off to Claude", "have Claude build") are missing, so it is not comprehensive.

4 / 5

Distinctiveness Conflict Risk

Carves a clear niche (delivery-owning delegation) and explicitly disambiguates the closest competing skill: "Answer-only investigations, recommendations, and text drafts belong to consult-claude." Distinct triggers plus an explicit boundary yield minimal conflict risk.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 6 suspicious

Warning

Total

15

/

16

Passed

Repository

EpicenterHQ/epicenter

Path

.agents/skills/delegate-claude/SKILL.md

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.