CtrlK
BlogDocsLog inGet started
Tessl Logo

ask

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

60

Quality

71%

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

Quality

Content

93%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 skill body is a tight, executable policy: a sequenced decision card, concrete command templates, and disciplined guardrails with an explicit stop-after-submit checkpoint. It is highly token-efficient and well-organized, with only minor validation-loop formality separating it from a perfect workflow-clarity score.

DimensionReasoningScore

Conciseness

The body is lean and dense with decision rules and guardrails, assuming Claude's competence and never explaining concepts it already knows; every line is actionable policy, matching 'Lean and efficient; every token earns its place'.

5 / 5

Actionability

It provides fully executable, copy-paste-ready command templates ('command ask "$TARGET" <<EOF...') plus concrete flag-selection criteria covering common cases, matching 'Fully executable; copy-paste ready code or commands'.

5 / 5

Workflow Clarity

The Decision Card gives a clearly sequenced pre-flight checklist (need delegation -> dependency gate -> result intent -> request fidelity) with explicit guidance and an 'After submit, stop' terminal checkpoint, but it lacks a formal validate/feedback loop and is not a multi-step destructive workflow; it sits just below 5 on minor validation-gap grounds.

4 / 5

Progressive Disclosure

No bundle files exist and none are needed for this sub-50-line skill; the content is well-organized into clearly labeled sections (Decision Card, Guardrails, command templates) with no nested references, so the simple-skill exception yields a 5.

5 / 5

Total

19

/

20

Passed

Description

50%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 concise and names a concrete action, but it is terse: it lacks an explicit 'when to use' trigger clause and offers only minimal capability detail. It reads as a one-line tool summary rather than a trigger-rich skill description.

Suggestions

Add an explicit 'Use when...' clause naming natural user triggers (e.g. delegating work to a CCB agent, collaborating with another CCB agent, handing off a task).

Enumerate the concrete capabilities (delegation with --chain, --silence, --compact, artifact-based requests) so the 'what' is comprehensive, not a single action.

Include natural synonyms and the command token 'ask' / 'CCB ask' as trigger terms users would actually say.

DimensionReasoningScore

Specificity

It names the concrete action ('Send a request to a CCB agent') but offers only that single action with no enumeration of capabilities or variations, matching the 'Names domain and 1-2 concrete actions, but not comprehensive' anchor.

3 / 5

Completeness

It gives a clear 'what' ('Send a request to a CCB agent') but has no 'Use when...' clause in the description itself; the missing explicit trigger guidance caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

The relevant keywords ('ask', 'CCB', 'delegate', 'collaboration') are present but the description lacks natural trigger phrasings a user would say and misses common synonyms; it sits between 'Some relevant keywords but missing common variations' (3) and 'Good keyword coverage' (4), closer to 3.

3 / 5

Distinctiveness Conflict Risk

The description is somewhat specific to the CCB tool niche but the wording is terse and generic enough that it could overlap with other delegation/collaboration skills, fitting 'Somewhat specific but could still overlap with similar skills'.

3 / 5

Total

12

/

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.