CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

claude-code-bridge

Integrate with Claude Code CLI for delegating complex coding tasks. Use when you need to spawn a separate Claude Code instance to work on files, run tests, or perform multi-step coding operations in a specific directory. Enables "Claude calling Claude" patterns for parallel work or specialized contexts.

Quality

83%

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

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

The content is a well-organized, actionable reference covering MCP, CLI, and library usage with concrete commands and config examples. It is concise with sensible error-handling guidance; the main improvements would be replacing illustrative pseudo-syntax with literal tool invocations and folding output verification into the workflow steps.

DimensionReasoningScore

Conciseness

The body is efficient: commands, tool names, and config are shown directly with no explanations of concepts Claude already knows. Minor instances could be trimmed, such as the opening line 'Delegate coding tasks to Claude Code CLI from any context' duplicating the frontmatter description, so it falls just below the leanest anchor.

4 / 5

Actionability

Mostly executable guidance: real CLI commands ('claude -p "..." --output-format json', '--continue', '--resume <session-id>'), named MCP tools, and a Rust snippet. The MCP usage examples use illustrative '[claude_prompt] prompt: ...' pseudo-syntax rather than literal invocations, a minor gap versus copy-paste readiness.

4 / 5

Workflow Clarity

Example workflows are clearly sequenced, including a followup loop ('# After reviewing results: [claude_continue]') and a 'Check Results' best practice acting as a checkpoint. However, validation of delegated output is only mentioned as advice rather than built into the workflow steps, a minor gap against the explicit-validation anchor.

4 / 5

Progressive Disclosure

No bundle files exist and all content is inline, but the ~130-line body is well-sectioned and appropriately sized for a single file. Structure is good with clear headers; it neither needs nor references external material, placing it just below the well-signaled multi-file reference anchor.

4 / 5

Total

16

/

20

Passed

Description

83%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 that clearly states what the skill does and when to use it, with concrete trigger phrases and a distinctive niche. It could reach the top tier by replacing generic phrasing ('delegating complex coding tasks') with more specific capabilities and broader natural-language synonyms.

DimensionReasoningScore

Specificity

The description names the domain and several concrete actions ('spawn a separate Claude Code instance to work on files, run tests, or perform multi-step coding operations in a specific directory'), but 'delegating complex coding tasks' is generic and capabilities like session resumption are absent, so it falls just short of the comprehensive-coverage anchor.

4 / 5

Completeness

It explicitly answers both 'what' ('Integrate with Claude Code CLI for delegating complex coding tasks') and 'when' with a concrete trigger clause ('Use when you need to spawn a separate Claude Code instance to work on files, run tests, or perform multi-step coding operations in a specific directory'), matching the top anchor.

5 / 5

Trigger Term Quality

Good natural phrases users would say: 'spawn a separate Claude Code instance', 'Claude calling Claude', 'parallel work', 'run tests'. A few natural synonyms are missing (e.g., 'delegate coding task', 'subagent', 'hand off'), keeping it below the comprehensive synonym coverage anchor.

4 / 5

Distinctiveness Conflict Risk

The 'Claude calling Claude' delegation niche is fairly distinct with specific triggers, but there is minor overlap risk with general agent-orchestration or subagent-delegation skills, so it sits between the 'mostly distinct' and 'clear niche' anchors.

4 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Raudbjorn/TTTRPS

Path

planning/done/claude-code-integration/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.