CtrlK
BlogDocsLog inGet started
Tessl Logo

ask

Delegate work or request information from another CCB-managed agent using ask. Use when the user asks Grok to ask, delegate to, hand off to, consult, or send work to a named CCB agent, or when project memory requires CCB collaboration.

70

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

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.

The content delivers a clear, sequenced decision procedure with concrete command templates and explicit error-recovery guidance, and it avoids padding almost entirely. Its weaknesses are minor: some redundancy across guardrail bullets, missing literal examples for the silence/compact variants, and a single-file structure that, while well-organized, is denser than the ideal progressive-disclosure shape.

Suggestions

Consolidate the repeated chain/silence routing rules (Guardrails bullets around lines 49–52 overlap the Decision Card's dependency gate) into one canonical statement to cut redundant tokens.

Add a fully literal example invocation (real target name and short message) and templates for the `--silence` and `--compact` variants so all common cases are copy-paste ready.

Consider moving the long exception-handling guardrails (followup injection states, lineage routing, diagnostics) into a references/ file, keeping SKILL.md as a lean overview with one-level-deep pointers.

DimensionReasoningScore

Conciseness

The body is dense and prescriptive with no explanation of concepts Claude already knows, but the chain/silence routing rules recur across several guardrail bullets (e.g., "Use `--chain` only for a real child dependency; use `--silence` for independent no-result work" restates the Decision Card's dependency gate), so minor tightening is possible. It sits between 'mostly efficient' (3) and 'lean, every token earns its place' (5) — efficient with a few redundant restatements, matching anchor 4.

4 / 5

Actionability

Concrete heredoc command templates cover the plain and full-flag cases, and error handling is explicit ("If CCB says `ask --chain requires an active parent job`, retry once with plain `ask`"). Not 5 because no fully literal example with a real target and message is given and the `--silence`/`--compact` variants have no template; not 3 because the guidance is executable rather than pseudocode.

4 / 5

Workflow Clarity

The numbered Decision Card (need delegation → dependency gate → result intent → request fidelity) gives a clear sequenced procedure, followed by submit → stop → report with explicit error-recovery loops (chain-error retry, permission-denied reporting). This is messaging/delegation, not a destructive or batch operation, so the validation cap does not apply; the sequence plus feedback loops matches anchor 5.

5 / 5

Progressive Disclosure

The skill has no bundle files, references no external paths, and is organized into clean sections (Decision Card, Guardrails, templates) with everything appropriately inline. Not 5 because the body runs ~87 lines — above the under-50-line simple-skill threshold under which well-organized sections alone would earn a 5 — and the dense guardrail set could arguably live in a reference file; not 3 because structure is good and nothing that belongs elsewhere is misplaced.

4 / 5

Total

17

/

20

Passed

Description

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

The description clearly and explicitly states both what the skill does and when to use it, with comprehensive natural-language trigger synonyms and a well-niched scope that poses minimal conflict risk. The only weakness is moderate capability specificity — it summarizes the action at a high level rather than enumerating the full range of delegation behaviors it supports.

Suggestions

Enumerate the concrete delegation capabilities (e.g., choosing silence/compact/artifact reply modes, chained child dependencies, sending corrections to active jobs) instead of stopping at 'delegate work or request information'.

Optionally name the other invocation paths (followup corrections, diagnostics like get/pend/watch) so the capability surface is comprehensively represented rather than implied.

DimensionReasoningScore

Specificity

"Delegate work or request information from another CCB-managed agent using ask" names the domain and 1-2 concrete actions, but does not enumerate the broader capability surface (flags, followups, diagnostics). It matches the 'names domain and 1-2 concrete actions, but not comprehensive' anchor; not 4 because several specific actions are not listed, not 2 because the actions given are concrete rather than generic.

3 / 5

Completeness

It explicitly answers what ("Delegate work or request information from another CCB-managed agent using ask") and when ("Use when the user asks... or when project memory requires CCB collaboration") with concrete trigger phrases. Both halves match the anchor exactly, so neither 4 nor lower applies.

5 / 5

Trigger Term Quality

"ask, delegate to, hand off to, consult, or send work to a named CCB agent, or when project memory requires CCB collaboration" comprehensively covers the natural synonyms a user would say for this task. Not 4 because no common variation of the trigger phrasing is missing for this domain (there are no file-extension equivalents to include).

5 / 5

Distinctiveness Conflict Risk

The scope is tightly niched to CCB-managed agents and the `ask` command, with distinct trigger phrases ("named CCB agent", "project memory requires CCB collaboration") that would not fire for unrelated skills. Clear niche with minimal conflict risk matches the anchor; no overlap risk justifying 4.

5 / 5

Total

18

/

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
SeemSeam/claude_codex_bridge
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.