CtrlK
BlogDocsLog inGet started
Tessl Logo

intent

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

71

1.32x
Quality

77%

Does it follow best practices?

Impact

94%

1.32x

Average score across 1 eval scenario

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

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 skill body is a tight, well-structured routing workflow with clear sequencing and feedback loops, assuming Claude's intelligence throughout. The only minor weakness is a few abstract directives that could be made more concrete.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: no concept explanations, no padding, every line directs action; matches 'Lean and efficient; every token earns its place'.

5 / 5

Actionability

Concrete gating conditions, named skills invoked with the Skill tool, and explicit decision branches give mostly executable guidance, but phrases like 'retrieve what the record, the repo, or the world can answer' are slightly abstract; fits anchor 4 with minor gaps.

4 / 5

Workflow Clarity

Clear Extract → Gate → Route → Output sequence with an explicit re-routing loop ('Route again until nothing blocks the ask'), a negative-question checkpoint, and a closing confirmation; this is a gating/routing workflow (not destructive/batch) so the validation cap does not apply, matching the explicit-checkpoints anchor.

5 / 5

Progressive Disclosure

Under 50 lines, well-organized into labeled sections (Extract/Gate/Route/Output) with no external references needed; the simple-skill exception permits a 5 for clear, well-organized content.

5 / 5

Total

19

/

20

Passed

Description

62%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 clearly states both what the skill does and when to use it, with a defined niche distinct from related routing skills. It would benefit from listing more concrete actions and adding the natural synonyms a user might voice.

Suggestions

Add one or two more concrete actions (e.g., 'extracts the ask and its blockers, routes each to the right skill') to lift specificity from one named action to several.

Include natural user-facing trigger phrases (e.g., 'when the request is vague, ambiguous, or could mean two different things') alongside the abstract descriptors.

Sharpen the 'Use when' clause with a concrete user situation to push completeness toward a 5.

DimensionReasoningScore

Specificity

Names the domain and a concrete action ('Turn a rough ask into a clear work order') but lists only one core action rather than multiple specific actions; anchor 3 fits better than 4 which expects several listed actions.

3 / 5

Completeness

Both 'what' (turn a rough ask into a work order) and an explicit 'Use when...' clause with concrete trigger phrases are present, but the 'when' could be more specific about the user-facing situations; fits anchor 4 rather than 5 which demands fully concrete trigger phrases on both sides.

4 / 5

Trigger Term Quality

Trigger terms ('rough, unspoken, or double-readable') are natural descriptors of an ambiguous ask but lack common synonyms and variations users would actually voice; matches 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

It carves a clear niche (pre-planning intent refinement) with distinct triggers, though it borders on overlapping with the adjacent skills it names (shape, clarify, elicit); minor overlap risk places it at 4 rather than 5.

4 / 5

Total

14

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
saadshahd/moo.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.