CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

target

Define how unsupervised work is judged before it runs. Use when work will run without a human watching, optimizing toward something.

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/target/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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 lean body with an explicit amend-until-verdict feedback loop, loud validation checkpoints, and concrete decision rules for deriving the contract. The main defects are the dangling `cheat-museum.md` reference at the judge step and prose compressed hard enough in places (e.g. the draft bullet) that a worked example would help.

Suggestions

Ship the referenced `cheat-museum.md` false-pass catalog (e.g. under references/) or remove the reference — the judge step depends on it and the file is absent from the bundle.

Add one short worked example of a locked contract (observable, reading command, direction, terminal value, cap, invariants) to ground the densely compressed draft bullet.

DimensionReasoningScore

Conciseness

The body is 23 lines of prose with zero padding and no explanation of concepts Claude already knows — every sentence carries instruction ("Success is defined before the run, not by it."). Lean and efficient; every token earns its place.

5 / 5

Actionability

Concrete decision rules ("the literal command that reads it (the strongest the work allows: drive the running app for a UI, a live terminal for a TUI, tests otherwise)"), named skills to invoke per condition, and enumerated contract parts make the guidance mostly executable. Minor gaps: no worked example of a finished contract, and the judge step's "known false-pass catalog in `cheat-museum.md`" is not present in the bundle.

4 / 5

Workflow Clarity

Clear condition-driven sequence (clarify → elicit → draft → anchor → judge) with an explicit feedback loop ("Each open false pass judge finds re-enters as an amendment — back through the drafting and anchoring conditions above — until the verdict stands"), explicit validation checkpoints ("A command that will not run fails here, loudly"; "It locks only when judge's verdict stands and the user locks it"), and error recovery for post-run gaming ("amend it here and rerun from the last honest point").

5 / 5

Progressive Disclosure

Sections are well-organized and the body is short, but its single external reference — "Start from the known false-pass catalog in `cheat-museum.md`" — points to a file that does not exist in the skill directory (no references/ or bundle files are present). A dangling dependency on a core step prevents a higher score despite good structure.

3 / 5

Total

17

/

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.

A concise, third-person description with an explicit 'Use when' clause targeting a genuinely distinct niche. Its weaknesses are an abstract 'what' (one meta-level action instead of concrete capabilities) and trigger coverage that omits natural synonyms like 'autonomous' or 'unattended'.

Suggestions

Enumerate 2-3 concrete capabilities in the description, e.g. "Drafts a success contract with one observable done-reading, anchors subjective criteria to machine-checkable rules, and red-teams the contract for false passes."

Add natural trigger synonyms to the 'Use when' clause: "autonomous", "unattended", "overnight", or "background runs", alongside "without a human watching".

DimensionReasoningScore

Specificity

"Define how unsupervised work is judged before it runs" names the domain and a single action, but the action is abstract — it never enumerates concrete capabilities like contract drafting, anchoring fuzzy criteria, or false-pass hunting. Not 4 (no list of several specific actions); not 2 because an actual action is stated rather than bare domain-naming.

3 / 5

Completeness

Both parts are present: what = "Define how unsupervised work is judged before it runs" and an explicit when = "Use when work will run without a human watching, optimizing toward something". Falls short of anchor 5 because the 'what' is a single abstract action without concrete capability detail.

4 / 5

Trigger Term Quality

"Use when work will run without a human watching, optimizing toward something" includes some natural phrases, but misses common variations users would actually say such as "autonomous", "unattended", "overnight", or "background run". Anchor 3 (some relevant keywords, missing synonyms) is the best fit.

3 / 5

Distinctiveness Conflict Risk

The trigger condition — work running "without a human watching, optimizing toward something" — is a narrow, distinctive niche with little overlap risk against typical file/format skills. Not 5 because it could still overlap with general planning or evaluation-type skills.

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/target/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.