CtrlK
BlogDocsLog inGet started
Tessl Logo

ask

Send a request to a CCB agent with `ask`.

61

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 ./inherit_skills/gemini_skills/ask/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 body is highly actionable and well-structured: a sequenced decision procedure, concrete executable command forms, and explicit error-recovery guidance. The only minor weakness is slight repetition in the --chain guardrails that could be tightened.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence (no padding about what CCB is), with every guardrail addressing a distinct failure mode; minor repetition around --chain handling keeps it just below a 5.

4 / 5

Actionability

Provides copy-paste-ready heredoc command templates for the common cases (plain ask and --chain --artifact-reply) plus concrete error-recovery directives ('If CCB says `ask --chain requires an active parent job`, retry once with plain ask').

5 / 5

Workflow Clarity

The numbered Decision Card is a clearly sequenced process with explicit gates (dependency, result intent, request fidelity), an error feedback loop (retry once on chain rejection), and a definitive terminal step ('end the turn ... do not poll').

5 / 5

Progressive Disclosure

Self-contained skill with no bundle files and no nested references; content is well-organized into clearly headed sections (Decision Card, Guardrails, command examples), satisfying the simple-skill exception for a 5.

5 / 5

Total

19

/

20

Passed

Description

53%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 is specific and distinct but incomplete: it states clearly what the skill does yet omits any explicit trigger guidance for when to invoke it. Adding a 'Use when...' clause would raise completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases (e.g., 'Use when the user asks to delegate work to a CCB agent, hand off a subtask, or collaborate via CCB `ask`').

Include common synonyms/users' phrasings such as 'delegate', 'hand off', 'collaborate', or 'CCB' to broaden trigger-term coverage.

Optionally enumerate 1-2 more concrete capabilities (e.g., routing results, silent delegation) to lift specificity from 3 toward 4-5.

DimensionReasoningScore

Specificity

Names the domain ('CCB agent') and one concrete action ('Send a request ... with `ask`'), matching the score-3 anchor of domain + 1-2 concrete actions without being comprehensive.

3 / 5

Completeness

Provides a clear 'what' ('Send a request to a CCB agent with `ask`') but no explicit 'when' / 'Use when...' trigger guidance, which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Contains relevant keywords ('request', 'CCB agent', 'ask') a user might say, but lacks common variations or synonyms, fitting the score-3 anchor.

3 / 5

Distinctiveness Conflict Risk

Tied to a specific named system (CCB) and command (`ask`), giving a clear niche with only minor overlap risk against other CCB-related skills, matching the score-4 anchor.

4 / 5

Total

13

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

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.