CtrlK
BlogDocsLog inGet started
Tessl Logo

explore

Find out what audience signals exist for an idea about people. Describe who you're trying to reach in plain English and see what's out there — which signals Watt has, how big and how fresh each one is, and what related angles are worth a look. A guided, one-question-at-a-time walk, so you get the lay of the land before building anything from it. Start here to size up an idea or get your bearings — "what's out there for runners", "is Watt a fit for X", "what else relates to Y" — or type /watt:explore.

69

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable and clearly sequenced, with concrete tools, formats, and error-recovery checkpoints. It is held back by heavy repetition that bloats the body and an overview that is too long given that detailed procedures already live in separate files.

Suggestions

De-duplicate the governing rules: state "one decision per turn / stop at the question", "never invent a signal", "read-only / discovery-only", and "pass by trait_hash" once each and reference them, rather than restating them in Purpose, each flow step, and How to behave.

Move the per-step narration/format detail (candidate card columns, option label grammar, profile-view axes) into the existing context files so SKILL.md reads as a lean overview that links out, strengthening both conciseness and progressive disclosure.

Ensure the referenced context/discovery.md, context/scoring.md, and context/adjacencies.md are present in the bundle so the on-demand reads resolve, since no bundle directory currently contains them.

DimensionReasoningScore

Conciseness

The body is ~22 KB / ~150 lines and restates its governing principles many times ("one decision per turn / stop" in the Purpose, each flow beat, and How to behave; "never invent a signal", "read-only", and "pass by trait_hash" each repeated across sections), so it is accurate but padded and could be tightened substantially. It is not a 1 because it does not pad with concepts Claude already knows.

2 / 3

Actionability

Guidance is concrete and executable: named tool calls (trait_search, visualize, cat "<Bundle root>/context/discovery.md"), specific option formats ("name · ~size · fresh/standard"), numeric bounds (1–3 searches, 2–4 options, ≤2-line reads), named render types, and quoted refusal/example utterances.

3 / 3

Workflow Clarity

A clearly sequenced 7-step flow with a per-beat stop checkpoint, a tracked kept-set/pool-view update on every change, and explicit feedback loops in Failure modes plus the first-call liveness gate for error recovery.

3 / 3

Progressive Disclosure

The three heavy procedures are split into one-level-deep, clearly signaled context/*.md references ("read it once this session with cat ..."), but those files are not present in any bundle directory so cannot be verified, and the SKILL.md overview is itself a dense monolith with step detail that could live in those separate files.

2 / 3

Total

10

/

12

Passed

Description

90%

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 strong, specific description with explicit trigger guidance and a clear niche. Its only real weakness is voice: it is written in second person rather than the prescribed third person.

Suggestions

Rewrite in third person to match the prescribed voice (e.g., "Finds what audience signals exist... Describes who the user is trying to reach..."), dropping "you're"/"you get".

DimensionReasoningScore

Specificity

It lists multiple concrete capabilities ("which signals Watt has, how big and how fresh each one is, and what related angles are worth a look"), which would be a 3, but it is written in second person ("Describe who you're trying to reach", "so you get the lay of the land"), so specificity is reduced by 1 per the third-person guideline.

2 / 3

Completeness

It answers both what ("Find out what audience signals exist... which signals Watt has, how big and how fresh each one is") and when with an explicit trigger clause ("Start here to size up an idea or get your bearings — ... — or type /watt:explore").

3 / 3

Trigger Term Quality

Natural trigger phrases a user would say are present and varied — "what's out there for runners", "is Watt a fit for X", "what else relates to Y", plus "size up an idea", "get your bearings", and the /watt:explore invocation.

3 / 3

Distinctiveness Conflict Risk

It carves a clear Watt / Signal Graph / audience-signals niche with the distinct /watt:explore trigger, making conflict with unrelated skills unlikely.

3 / 3

Total

11

/

12

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
wattdata/plugin
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.