CtrlK
BlogDocsLog inGet started
Tessl Logo

read-all-adrs

Read every ADR markdown file in the project's docs/adr/ folder so you have full context on past decisions. Use only when the user explicitly calls it.

60

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/thinking-and-docs/read-all-adrs/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

The skill's single action is concrete and actionable, but the body is marred by triple repetition, a hostile filler line, and a leftover TODO, with no verification step or organization. It communicates intent yet reads as unpolished and unprofessional.

Suggestions

Remove the profanity, the TODO comment, and the duplicate restatements; state the instruction once, cleanly.

Add a brief verification step for the batch read (e.g., 'List docs/adr/*.md first and confirm each was read in full') to raise workflow clarity.

Organize with a minimal heading (e.g., '## What to do') so the short body reads as intentionally structured.

DimensionReasoningScore

Conciseness

The body is short but padded: the core 'read every ADR' instruction is repeated three times and includes a profanity-laced exhortation ('DO NOT BE A LAZY CUNT. ACTUALLY DO THIS.') and a leftover TODO comment that earn no informational value.

2 / 3

Actionability

For this single-purpose instruction skill, 'Read EVERY single ADR .md file in this project's docs/adr/ folder, start to finish' is a concrete, unambiguous, executable instruction with a specific path; absence of code is not penalized when guidance is actionable.

3 / 3

Workflow Clarity

The single action is unambiguous, but this is a batch read operation with no verification step (e.g., listing/confirming all ADRs were read), and the redundant restatements obscure the sequence rather than clarifying it.

2 / 3

Progressive Disclosure

The body is tiny and needs no external references, but it has no organized sections (only prose, a TODO comment, and filler), so it does not meet the 'well-organized sections' bar for a 3 on short skills.

2 / 3

Total

9

/

12

Passed

Description

75%

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 is concrete and distinct with an explicit 'Use only when...' trigger, but uses second-person voice and offers only narrow trigger-term coverage. It is competent but could be tightened and broadened.

Suggestions

Rewrite in third person / imperative process voice (e.g., 'Reads every ADR ...') and drop 'so you have full context' to avoid the second-person voice penalty.

Broaden trigger terms to include 'architecture decision records', 'ADRs', and 'decision logs' so users can naturally invoke it.

Consider stating the value of the context (e.g., 'to inform current design decisions') more concisely instead of the second-person framing.

DimensionReasoningScore

Specificity

The phrase 'Read every ADR markdown file in the project's docs/adr/ folder' names a concrete action and a specific path, but it is a single action rather than multiple concrete capabilities, and the second-person 'so you have full context' triggers the voice penalty (-1).

2 / 3

Completeness

It states both what ('Read every ADR markdown file ... so you have full context on past decisions') and when ('Use only when the user explicitly calls it'), satisfying the explicit-trigger requirement.

3 / 3

Trigger Term Quality

'ADR markdown file' and 'docs/adr/ folder' are relevant keywords, but coverage is limited — missing common variations like 'architecture decision records' or natural phrasings a user might say.

2 / 3

Distinctiveness Conflict Risk

The ADR-specific niche ('docs/adr/ folder', 'past decisions') is clear and unlikely to trigger for unrelated skills.

3 / 3

Total

10

/

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
mishatojk/davidskills
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.