CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

intent

Turn a rough ask into a clear work order. Use when the ask is rough, unspoken, or double-readable — before planning or building.

78

1.10x
Quality

83%

Does it follow best practices?

Impact

97%

1.10x

2 of 3 eval scenarios. Add 1 more for a full score.

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exceptionally token-efficient instruction-only skill: concrete routing rules with named tool invocations and a clear loop, organized appropriately for its size. The only real gaps are the unspecified method behind the initial lookup step and implicit rather than explicit validation of the final work order.

DimensionReasoningScore

Conciseness

The 16-line body is telegraphic with zero padding: no concept explanations, no restatements, and every line either routes, asks, or states an output, fitting the lean-and-efficient top anchor.

5 / 5

Actionability

Concrete condition-to-skill routing rules, named tool invocations ("invoking the named skill with the Skill tool", "with AskUserQuestion"), and an explicit output spec ("the ask, the bar it must meet, and what it must NOT do") make this mostly executable; the opening instruction "Look up what the record, the repo, or the world can answer" gives no method or tools, a minor gap that keeps it below 5.

4 / 5

Workflow Clarity

The sequence (lookup → route → re-route → ask open questions → deepen → state work order → shape) is clear and includes an explicit termination loop ("Route again until nothing is left to invent"), but validation checkpoints are implicit and some transitions are compressed, matching the most-checkpoints-present anchor rather than the explicit-validation anchor at 5.

4 / 5

Progressive Disclosure

At 16 lines with no bundle files and no content that warrants external references, the body's paragraph-and-bullet organization fully satisfies structure and navigation; per the rubric's simple-skill guideline, this can score 5 without headers or reference files.

5 / 5

Total

18

/

20

Passed

Description

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

A strong description that explicitly covers both what and when in minimal tokens, with a well-defined niche. Its main weakness is trigger coverage: it leans on one invented term ("double-readable") and misses the common synonyms users naturally say for an unclear request.

Suggestions

Replace or supplement "double-readable" with natural user phrasings such as "unclear", "vague", or "ambiguous ask" so the trigger matches what users actually say.

Consider naming one or two additional concrete actions (e.g., distinguishing what only the user can decide from what can be looked up) to raise specificity beyond a single stated transformation.

DimensionReasoningScore

Specificity

"Turn a rough ask into a clear work order" names one concrete transformation with a clear input and output, but no further actions are enumerated, matching the 1-2-concrete-actions anchor rather than the several-actions anchor at 4.

3 / 5

Completeness

The description explicitly answers both: what it does ("Turn a rough ask into a clear work order") and when to use it ("Use when the ask is rough, unspoken, or double-readable — before planning or building") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Phrases like "rough", "unspoken", and "before planning or building" are relevant triggers, but common natural variations users would say ("unclear", "vague", "ambiguous") are missing and "double-readable" is invented jargon no user would naturally say.

3 / 5

Distinctiveness Conflict Risk

The intent-clarification-before-planning niche is mostly distinct with specific triggers, but there is minor overlap risk with planning and requirements-gathering skills that could claim the same situations.

4 / 5

Total

15

/

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

saadshahd/moo.md

Path

hope/skills/intent/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.