CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

62

Quality

73%

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

Fix and improve this skill with Tessl

tessl review fix ./planning/done/claude-code-integration/SKILL.md

The canonical home for this skill is claude-code-bridge in Raudbjorn/TTTRPS

SKILL.md
Quality
Evals
Security

Quality

Content

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

An actionable, well-organized skill body built around concrete executable examples across CLI, MCP, and library interfaces. The chief gap is workflow clarity: delegated operations can be destructive, yet no explicit validation/feedback loop is documented.

Suggestions

Add an explicit validate->fix->retry checkpoint in the delegation workflow (e.g. inspect Claude Code's diff/output, re-prompt to fix failures before proceeding) to lift workflow_clarity above the destructive-operation cap of 3.

Collapse the partly-redundant 'Usage Patterns' and 'Example Workflows' sections, or convert the pseudo '[claude_prompt]' blocks into the literal executable MCP/CLI calls already shown.

Move the two inline MCP config JSONs behind a short reference pointer if the file grows, to keep the overview scannable.

DimensionReasoningScore

Conciseness

Mostly lean code blocks and concise lists with no explanation of concepts Claude already knows; minor redundancy between 'Usage Patterns' and 'Example Workflows' and light narrative padding could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready CLI commands, a concrete MCP tool list, a Rust snippet, and config JSONs; the example workflows use a pseudo '[claude_prompt]' syntax that is not literally executable, leaving a minor gap.

4 / 5

Workflow Clarity

Workflows are loosely sequenced (prompt, review, continue) with only an implicit 'Check Results' checkpoint and no explicit validate->fix->retry loop, so the destructive/batch-operation cap of 3 applies.

3 / 5

Progressive Disclosure

No bundle files exist; the self-contained SKILL.md is well-sectioned (When to Use, Usage Patterns, Configuration, Best Practices, Example Workflows, Error Handling) with no nested references and only minor organization gaps.

4 / 5

Total

15

/

20

Passed

Description

78%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 well-structured description that clearly states both capability and explicit 'Use when' triggers with concrete actions. The main weakness is second-person voice ('you need to'), which the rubric penalizes on specificity.

Suggestions

Rewrite in third person to avoid the second-person penalty, e.g. 'Use when a separate Claude Code instance is needed to work on files, run tests, or perform multi-step coding operations in a specific directory.'

Tighten the somewhat marketing-toned closing line ('Enables Claude calling Claude patterns...') into a concrete capability statement.

DimensionReasoningScore

Specificity

Lists several concrete actions (delegate coding tasks, spawn a Claude Code instance to work on files, run tests, multi-step operations), but the second-person phrasing 'Use when you need to spawn' incurs the rubric's -1 specificity penalty.

3 / 5

Completeness

Explicitly answers both what ('Integrate with Claude Code CLI for delegating complex coding tasks') and when ('Use when you need to spawn a separate Claude Code instance...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good coverage of natural domain terms ('Claude Code', 'spawn a separate Claude Code instance', 'parallel work', 'multi-step coding operations'), with a few natural synonyms missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche of delegating to a separate Claude Code instance with distinct triggers; minor overlap risk with general coding skills due to the broad phrase 'complex coding tasks'.

4 / 5

Total

16

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Raudbjorn/TTTTRPS
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.