CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

clarify-question-loop

Use when a meta-agent request is too ambiguous to safely generate, package, publish, or adapt without one to five targeted questions.

Quality

70%

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 ./.agents/skills/clarify-question-loop/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 an efficient, actionable instruction skill with a clear sequenced procedure, concrete question texts, plain-language translations, and explicit budgets and stop rules. Its main defect is external: three referenced paths do not exist in the bundle, so the progressive-disclosure structure does not actually resolve. Minor internal gaps (undefined mode classification, duplicated question) keep actionability and workflow clarity just below top marks.

Suggestions

Ship the referenced files in the bundle (e.g. references/clarify-question-loop.md, references/builder-interview-research-gate.md) or remove the '## Reference' and contract pointers so no path dangles.

Add brief criteria for 'Classify the current best mode' in step 1, or point to where those criteria live, so the procedure is self-contained.

DimensionReasoningScore

Conciseness

The body is lean and procedural with no explanations of concepts Claude already knows, and project-specific budget numbers ('chat 3-5 in one batch, stormbreaker <= 8 across two batches') earn their tokens. Minor tightening is possible — the Korean single-expert question is duplicated verbatim in Procedure step 2 and Default Questions, and the budgets paragraph is dense — so it fits anchor 4 (efficient, minor instances that could be trimmed) rather than 5.

4 / 5

Actionability

Guidance is highly concrete for an instruction-only skill: literal copy-paste question texts (including the full Korean plain-language question), verbatim translation mappings ('synthesis -> 마지막에 결과를 한데 모으는 일'), explicit budgets, and a crisp stop rule ('If more than five functional-quality questions remain, return to the Builder Interview'). It falls short of anchor 5 because step 1 ('Classify the current best mode') gives no criteria and depends on external context, leaving a minor gap.

4 / 5

Workflow Clarity

The 8-step Procedure is clearly sequenced with an escalation checkpoint (step 5's return-to-gate rule) and a feedback loop (step 7's 're-run mode classification if needed' after answers arrive). This matches anchor 4 (clear sequence, most checkpoints present, minor validation gaps) rather than 5 — mode classification criteria are external and there is no explicit checklist for when assumptions listed in step 8 are acceptable.

4 / 5

Progressive Disclosure

Sections are well-organized and the skill is short enough to be self-contained, but the body points to 'contracts/builder-interview-research-gate.md', 'agentlas_cloud/interview/', and 'docs/clarify-question-loop.md' — none of which exist in the skill bundle (no references/, scripts/, or assets/ directories are present). Per the guideline to score against the actual bundle structure, these dangling references make navigation fail, matching anchor 3 (references present but not resolvable/signaled well) rather than 4.

3 / 5

Total

15

/

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 has a strong, explicit trigger clause but never directly states what the skill does — the action (asking one to five targeted clarifying questions) must be inferred from the 'without ...' phrasing. Trigger terms lean on internal jargon ('meta-agent request') and miss natural synonyms. It is distinctive within its niche but reads more like half of a complete description.

Suggestions

State the action explicitly, e.g. 'Asks one to five targeted clarifying questions to resolve ambiguity before generating, packaging, publishing, or adapting a meta-agent package.'

Add natural trigger terms users would actually say — 'clarify', 'unclear requirements', 'ambiguous request', 'ask me questions' — instead of relying on 'meta-agent request' jargon.

Keep the explicit 'Use when...' clause but pair it with the 'what' in the standard pattern: capabilities first, trigger second (see the rubric's good examples).

DimensionReasoningScore

Specificity

The domain is named (clarifying ambiguous 'meta-agent request' work) and the mechanism is concretely quantified ('one to five targeted questions'), but the skill's actual actions are never stated directly — only implied through the 'without ... targeted questions' construction. It matches anchor 3 (domain plus 1-2 concrete actions, not comprehensive) rather than 4, which requires several explicitly listed actions.

3 / 5

Completeness

The 'when' is explicit and specific ('Use when a meta-agent request is too ambiguous to safely generate, package, publish, or adapt'), but the 'what' is only implied — the verb 'ask' never appears, so the reader must infer the skill asks clarifying questions. Per the guideline to score only what is explicitly stated, this sits between anchor 2 (only 'when' present) and anchor 4 (both explicit), landing at 3.

3 / 5

Trigger Term Quality

Relevant keywords exist ('too ambiguous', 'targeted questions', 'generate, package, publish, or adapt'), but 'meta-agent request' is internal jargon users would not naturally say, and common variations like 'clarify', 'unclear requirements', or 'ask me questions' are missing. This lands on anchor 3 (some relevant keywords, missing common synonyms) rather than 4.

3 / 5

Distinctiveness Conflict Risk

The trigger is scoped to a distinct niche — ambiguity in meta-agent generation/packaging/publishing/adaptation — with a quantified question budget, giving minimal overlap risk with unrelated skills. It matches anchor 4 (mostly distinct, minor overlap with closely related skills such as general interviewing/clarification skills) rather than 5, since 'ambiguous request' alone could overlap with generic clarification skills.

4 / 5

Total

13

/

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

agentlas-ai/Agentlas-OS

Path

.agents/skills/clarify-question-loop/SKILL.md

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.