CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

shape

Decide the technical path once the ask is clear. Use when the WHAT is confirmed but more than one way to build it remains — architecture, technology, design.

1.13x
Quality

76%

Does it follow best practices?

Impact

95%

1.13x

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

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./hope/skills/shape/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 unusually tight, well-sequenced routing procedure with concrete tool invocations and an explicit termination condition — strong on token efficiency and actionability for an instruction-only skill. Its one real defect is the broken reference to loop-selection.md, which sends the reader to a file that does not exist in the bundle.

Suggestions

Fix the dangling reference: either ship loop-selection.md in a references/ directory or inline the loop-selection guidance (it is only needed for iterative work), since no bundle files exist at all.

Add one short worked example of an open choice and its resolution (e.g., 'Postgres vs. SQLite — resolved to SQLite because the app is single-user, Postgres lost on ops burden') to make the 'state each resolved choice with its reason and what lost' step concrete.

DimensionReasoningScore

Conciseness

The body is lean with zero padding: no explanations of concepts Claude already knows, and every clause carries load (e.g., 'however likely the assumption, is open' is a load-bearing qualifier, not filler). It fully assumes Claude's competence.

5 / 5

Actionability

The guidance is mostly executable for an instruction-only skill: named skills to invoke with the Skill tool (judge, draft, elicit, clarify, explain, inversion, intent, deepen), a concrete lookup list (CLAUDE.md, project rules, repo, docs, web), and a specific tool call (AskUserQuestion). It falls short of 5 because no examples illustrate what an open choice or a resolved-choice statement looks like in practice.

4 / 5

Workflow Clarity

A clear sequence is present (hold changes → establish the bar → route each open choice → re-enter routing until stable → ask all at once → state resolutions) with an explicit feedback loop ('Route again until every open choice has the user's decision or confirmation and none conflict') and a verification step ('state each resolved choice with its reason and what lost'). Minor gaps — the ordering between the Route loop and 'The path' section is implicit — keep it below 5.

4 / 5

Progressive Disclosure

The sections are well organized for a sub-50-line skill, but its single external reference — 'read `loop-selection.md`' — is dangling: no references/ directory or loop-selection.md file exists anywhere in the skill bundle. A broken navigation path is worse than a merely unclear signal, so this lands at 3 rather than 4.

3 / 5

Total

16

/

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 cleanly answers both what the skill does and when to use it, with a well-delineated niche in the decision-making lifecycle. Its main weaknesses are limited action coverage (one verb) and a thin set of natural trigger terms that would help users (and Claude) invoke it reliably.

Suggestions

List the concrete actions the skill performs, not just one — e.g., 'Compare candidate approaches, route each open choice to the right clarification skill, and present every decision at once' — to lift specificity.

Add natural trigger phrases users actually say, such as 'approach', 'tech stack', 'framework choice', 'tradeoffs', or 'how should we build this', to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The description gives one concrete action ('Decide the technical path') and names its domain ('architecture, technology, design'), matching the anchor for 1-2 concrete actions. It is not a 4 because only a single action is listed rather than several specific capabilities.

3 / 5

Completeness

Both parts are present: what ('Decide the technical path') and an explicit when ('Use when the WHAT is confirmed but more than one way to build it remains'). It falls short of a 5 because the when-clause is a conversation-state condition rather than concrete trigger phrases a user would actually say.

4 / 5

Trigger Term Quality

It includes some relevant keywords ('architecture', 'technology', 'design', 'more than one way to build it') but misses common variations and synonyms users naturally say such as 'approach', 'tech stack', 'framework', or 'which library'. This sits at 'some relevant keywords but missing common variations' rather than 'good keyword coverage'.

3 / 5

Distinctiveness Conflict Risk

The boundary markers 'once the ask is clear' and 'the WHAT is confirmed' carve a distinct niche (path decision after requirements are settled), separating it from requirements-clarification skills. Minor overlap risk remains with general planning or design-branching skills, keeping it below 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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

saadshahd/moo.md

Path

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