CtrlK
BlogDocsLog inGet started
Tessl Logo

i-have-adhd

Use when the user invokes /i-have-adhd, says they have ADHD, or asks for ADHD-friendly output. Also used as a required writing filter by the docs skill. Don't use for marketing copy or after the user says "stop adhd mode" or "normal mode".

73

Quality

92%

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

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.

A tightly written, highly actionable style skill with concrete Bad/Good examples, a clear single workflow, and an explicit pre-send validation checklist. The only marginal improvement is trimming the rationale section that Claude could infer.

Suggestions

Consider shortening 'What ADHD changes about reading' to one line per fact (drop the explanatory second sentence) since each rule already encodes the implication, or fold the facts into the relevant rules as inline rationale.

Optionally move the 'When to break the rules' overrides to a collapsed/secondary section so the core 10 rules load first, though at 144 lines this is optional.

DimensionReasoningScore

Conciseness

The body is lean with punchy Bad/Good examples and no padding about basic concepts, but the 'What ADHD changes about reading' section is a minor instance of rationale that Claude could largely infer and could be trimmed, matching 'efficient; minor instances of over-explanation' rather than 'every token earns its place' (5).

4 / 5

Actionability

Each of the 10 rules pairs a concrete directive with a Bad/Good example using exact phrasings and specific commands/paths (e.g. 'npm install jsonwebtoken', 'src/auth.ts:42'), and the pre-send check is a concrete deletable checklist — fully actionable for an instruction-only skill.

5 / 5

Workflow Clarity

The single workflow is clearly sequenced (apply rules → pre-send check → send) with an explicit validation checkpoint ('verify: if the reader reads only the first line and the last line...'), and the 'When to break the rules' section supplies override logic; this is a clean checklist with a verify step, scoring 5.

5 / 5

Progressive Disclosure

No bundle files exist and none are needed; the single file is organized under clear headers (Persistence, What ADHD changes, Rules, When to break, Pre-send check) with easy navigation and no nested references, so structure is appropriate for a cohesive single-file style guide.

5 / 5

Total

19

/

20

Passed

Description

90%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 strong, well-scoped description that gives explicit trigger conditions, exclusions, and a secondary use case. Its only soft spot is capability specificity, which is inherent to a style/filter skill rather than a content-processing one.

DimensionReasoningScore

Specificity

The description names the domain ('ADHD-friendly output', 'required writing filter by the docs skill') and concrete triggers, but the capability itself is abstract — a style/filter skill has few concrete 'actions' to list, so it sits at 'names domain and 1-2 concrete actions' rather than 'lists several specific actions' (4).

3 / 5

Completeness

It explicitly answers both what (ADHD-friendly output / writing filter) and when (the three trigger conditions plus exclusions), with concrete trigger phrases, matching the 'clearly and explicitly answers both what AND when' anchor.

5 / 5

Trigger Term Quality

It covers natural user phrasings comprehensively — 'invokes /i-have-adhd', 'says they have ADHD', 'asks for ADHD-friendly output' — plus negative stop phrases ('stop adhd mode', 'normal mode'), matching the 'comprehensive coverage including synonyms' anchor.

5 / 5

Distinctiveness Conflict Risk

The /i-have-adhd invocation and ADHD-specific triggers carve a clear niche with minimal overlap; the only adjacency (the docs skill) is explicitly scoped as a prerequisite, fitting 'clear niche with distinct triggers; minimal conflict risk'.

5 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
TanStack/ai
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.