CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

deepen

Hold an ask to the bar a top professional in its field would set — a deeper ask, never a bigger one. Use when an ask is clear but nothing yet names the sources, methods, target, or outside check the work will meet.

Quality

79%

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 ./hope/skills/deepen/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 exemplar of token efficiency: a compact, well-sequenced instruction set with concrete questions, an output template, and explicit routing. Its only real gap is the absence of a worked example showing one field's deepened bar and how an item gets dropped, which keeps actionability and workflow clarity just below the top anchors.

Suggestions

Add one compact worked example: a field (e.g. 'SRE incident response'), one kept item and one dropped item, and the resulting four-line bar, so the drop judgment is demonstrated rather than only described.

Specify what to do when the user declines a kept item during the AskUserQuestion step (drop silently, or restate the bar without it).

DimensionReasoningScore

Conciseness

The ~25-line body is lean with no padding and no explanations of concepts Claude already knows; every instruction (questions, drop rule, interaction gate, template, routing) earns its place. It matches the lean-and-efficient top anchor.

5 / 5

Actionability

The body gives five numbered questions, a concrete drop rule, a named tool (AskUserQuestion) with explicit money/time/ships criteria, a copy-paste output template, and explicit routing conditions. It falls short of fully executable coverage only in lacking a worked example of a deepened bar for one field, matching the mostly-executable-with-minor-gaps anchor.

4 / 5

Workflow Clarity

The sequence is clear (silently name the field, answer the questions, apply the deeper-not-bigger filter, ask about costly items, hand back the bar, route to intent/consult), and the drop rule plus the 'Nothing survives' exit act as checkpoints. It misses the top anchor because there is no step covering the user declining a kept item or an explicit verification loop on the produced bar.

4 / 5

Progressive Disclosure

This is a single-file skill under 50 lines with no need for external references (no references/, scripts/, or assets/ bundle exists), organized in a logical order from questions through rules to template and routing. Per the rubric's simple-skill guideline this matches the top anchor.

5 / 5

Total

18

/

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 has an explicit and well-targeted 'Use when...' clause and a distinctive deeper-not-bigger identity, but its statement of what the skill does is metaphorical rather than concrete, and its natural trigger vocabulary is narrow. It is solidly above the midpoint but not comprehensive.

Suggestions

Replace the metaphorical what with concrete actions, e.g. 'Raises an ask's standard: names the sources, sharper methods, harder target, and outside verification the work must meet.'

Add natural trigger phrasings users would actually say, such as 'requirements', 'make this more rigorous', 'expert-level', or 'what would a specialist demand'.

Sharpen distinctiveness by contrasting with scope expansion, e.g. 'Deepens the bar an ask must meet without expanding its scope' as an explicit differentiator.

DimensionReasoningScore

Specificity

The description names its domain (raising an ask's standard) and enumerates concrete elements ("sources, methods, target, or outside check"), but the core action "Hold an ask to the bar a top professional in its field would set" is metaphorical rather than a list of concrete actions. This matches the anchor for naming the domain with 1-2 concrete actions, not the level above, which requires several specific listed actions.

3 / 5

Completeness

Both what ("Hold an ask to the bar a top professional in its field would set — a deeper ask, never a bigger one") and when ("Use when an ask is clear but nothing yet names the sources, methods, target, or outside check") are explicitly present. It falls short of the top anchor because the what relies on the bar metaphor rather than fully concrete trigger phrasing.

4 / 5

Trigger Term Quality

Terms like "ask", "sources", "methods", "target", "outside check", and "top professional" are relevant, and "a deeper ask, never a bigger one" is a memorable distinction. However, natural user phrasings such as "requirements", "more rigorous", or "expert-level" and their synonyms are missing, matching the some-keywords-but-missing-variations anchor rather than good coverage.

3 / 5

Distinctiveness Conflict Risk

"A deeper ask, never a bigger one" plus the narrow trigger condition (a clear ask lacking named sources/methods/target/verification) carves a distinct niche away from generic ask-refinement skills. Minor overlap risk remains with adjacent requirements-shaping skills, matching the mostly-distinct anchor rather than the clear-niche one.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

saadshahd/moo.md

Path

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