ask

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

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./inherit_skills/dsh_skills/ask/SKILL.md

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 a lean, action-oriented reference: a concrete executable template plus tight, tool-specific flag and correction guidance with clear stop-after-submit boundaries, and it is appropriately scoped for a simple single-purpose skill with no bundle dependencies.

Dimension	Reasoning	Score
Conciseness	Every sentence delivers tool-specific guidance (flags, stop-after-submit, routing rule) with no padding and no explaining of concepts Claude already knows, matching the 'lean and efficient; assumes Claude's competence; every token earns its place' anchor; it cannot exceed 5 and is clearly above 4 where minor over-explanation would appear.	5 / 5
Actionability	It provides a concrete executable heredoc template and specific flag/command guidance (`--chain`, `--silence`, `ccb followup`, avoid `watch`/`pend`/`ping`/`ask get`), matching 'mostly executable guidance; concrete code or commands with minor gaps'; it stops short of 5 because only the single common case is exemplified rather than multiple covered cases.	4 / 5
Workflow Clarity	As a simple single-purpose skill the action is unambiguous—submit the ask, then stop—and explicit guardrails plus the correction-flow guidance make the sequence and its boundaries clear, qualifying for the simple-skill exception to score 5; no destructive/batch validation cap applies.	5 / 5
Progressive Disclosure	The skill is under 50 lines, single-purpose, and needs no external references (no references/scripts/assets bundle exists), so the well-organized single-heading body satisfies the 'under 50 lines with no need for external references can score 5' guideline; it is not below 4 because nothing is inlined that belongs in a separate file.	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 concise and names a concrete action with a distinct tool-specific niche, but it lacks an explicit 'when to use' trigger clause and offers limited keyword variations, capping completeness and trigger-term quality at the midpoint.

Suggestions

Add an explicit 'Use when...' clause stating when to invoke ask (e.g., when the user requests delegation or project memory assigns a task to another mounted agent).

Include natural trigger synonyms or variations a user might say, such as 'delegate', 'hand off', or 'subtask', to broaden keyword coverage.

Optionally list one or two more concrete capabilities (e.g., chaining or follow-up correction) to lift specificity from a single action toward fuller coverage.

Dimension	Reasoning	Score
Specificity	The phrase 'Send a request to another CCB agent with `ask`' names the domain (CCB agent delegation) and one concrete action (send a request via ask), matching the 'names domain and 1-2 concrete actions, not comprehensive' anchor; it is not a 2 because the action is concrete rather than generic, and not a 4 because only one action is named with no broader coverage.	3 / 5
Completeness	It gives a clear 'what' ('Send a request to another CCB agent with `ask`') but no explicit 'when'/'Use when' trigger, which per the judging guidelines caps completeness at 3; it is above 2 because the 'what' is concrete rather than vague, and cannot reach 4 without an explicit usage trigger.	3 / 5
Trigger Term Quality	It surfaces 'request', 'CCB agent', and 'ask' as relevant keywords but offers no synonyms or natural variations a user might phrase differently, fitting the 'some relevant keywords but missing common variations' anchor; below 4 due to thin coverage, above 2 because the terms are on-topic rather than generic.	3 / 5
Distinctiveness Conflict Risk	The CCB `ask` delegation niche is mostly distinct with only minor overlap risk against general agent-delegation concepts, matching the 'mostly distinct; minor overlap risk' anchor; not a 5 because 'request to another agent' is conceptually broad enough to risk slight overlap, not a 3 because the tool-specific framing is clearly distinguishable.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: SeemSeam/claude_codex_bridge
Path: inherit_skills/dsh_skills/ask/SKILL.md
Commit: 18bf0af

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

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.