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.

1.04x
Quality

76%

Does it follow best practices?

Impact

92%

1.04x

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

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./hope/skills/intent/SKILL.md
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.

The body is an exceptionally lean, self-contained routing procedure that names concrete tools and skills with explicit routing criteria and a termination loop. Its only weaknesses are interpretive decision criteria without worked examples and no verification step for the final work order, which keep actionability and workflow clarity at 4 rather than 5.

DimensionReasoningScore

Conciseness

The 16-line body is lean with zero padding: every sentence instructs ("Look up what the record, the repo, or the world can answer", "Route again until nothing is left to invent") and nothing explains concepts Claude already knows. Matches anchor 5 ('Lean and efficient; assumes Claude's competence; every token earns its place') with no over-explanation to trim as anchor 4 would require.

5 / 5

Actionability

The guidance is mostly executable for an instruction-only skill: it names the exact tool ("invoking the named skill with the Skill tool", "AskUserQuestion") and each routing rule maps a specific condition to a named skill (clarify, elicit, explain, interrogate, reframe, deepen, shape). Not 5 because the routing conditions and the cost heuristic ("costs less to undo than the question costs to ask") require interpretation with no worked examples; better than 3 since tool invocations and criteria are concrete, not pseudocode.

4 / 5

Workflow Clarity

A clear sequence is present — look up answerable facts, route the rest by kind, re-route until nothing is left to invent, ask open questions, state the work order — with an explicit termination condition ("Route again until nothing is left to invent") and a decision rule for turning gaps into assumptions. No destructive or batch operations, so the validation cap does not apply; not 5 because there is no verification step for the final work order and some step ordering is implicit.

4 / 5

Progressive Disclosure

The skill is self-contained at ~16 lines with no bundle files (references/, scripts/, assets/ are absent) and no need for external references; the routing bullet list plus short closing procedure is well-organized for this size. Per the rubric's simple-skill note, an under-50-line skill with no need for external references scores 5 with well-organized sections.

5 / 5

Total

18

/

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 an explicit what and a well-timed when clause, but the what is a single abstract action and the trigger vocabulary leans on coined terms ("double-readable", "unspoken") rather than the natural phrases users would say. It is serviceable but below the standard of the good examples, which list concrete capabilities and natural trigger synonyms.

Suggestions

Replace coined trigger terms with natural user vocabulary: add synonyms like "vague", "unclear", "ambiguous", or "not sure what they want" alongside or instead of "unspoken" and "double-readable".

Make the what concrete: enumerate the actual capabilities (e.g., "resolve ambiguous requests, elicit unstated requirements, and route each gap to a clarification skill, producing a written work order with success criteria and exclusions").

Briefly define the output artifact ("work order") in the description so the skill's deliverable is distinguishable from generic planning or requirements-gathering skills.

DimensionReasoningScore

Specificity

"Turn a rough ask into a clear work order" names the domain but describes only one abstract transformation with no concrete sub-actions (no mention of routing, questioning, or what a work order contains). This matches the anchor 'Names the domain but actions are minimal or generic'; it falls short of 3 because there are no concrete actions listed, only a single generic one.

2 / 5

Completeness

Both parts are explicit: the what ("Turn a rough ask into a clear work order") and the when ("Use when the ask is rough, unspoken, or double-readable — before planning or building"). Not 5 because the trigger phrases are abstract characterizations rather than concrete natural phrases, and the what leaves "work order" undefined; it exceeds 3 because the when clause is present and explicit.

4 / 5

Trigger Term Quality

The trigger clause "Use when the ask is rough, unspoken, or double-readable — before planning or building" contains some relevant keywords ("rough", "ask", "planning", "building"), but relies on coined terms ("unspoken", "double-readable") no user would naturally say and misses common synonyms like "vague", "unclear", "ambiguous", or "requirements". This fits anchor 3 ('Some relevant keywords but missing common variations or synonyms') better than 2, since there is more than one relevant keyword.

3 / 5

Distinctiveness Conflict Risk

The timing marker "before planning or building" carves out a distinct pre-planning niche, but "rough ask" is broad and overlaps heavily with the whole family of clarification/requirements skills (clarify, elicit, explain, interrogate, reframe referenced in the body). Fits anchor 3 ('Somewhat specific but could still overlap with similar skills'); not 4 given the size of the overlapping skill family.

3 / 5

Total

12

/

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.