CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

first-reader

Beta readers for any draft, run by simulating how a real reader experiences it, moment by moment. A skim gate, a no-lookahead timed read producing an attention transcript with quit points, a recall test of what a reader remembers the next day, and a trust ledger of the implied author. Use when the user asks for a beta read, beta readers, test readers, human review, reader review, to read something like a human, to be a first reader, whether a piece holds attention or will actually get read, for a quick read of whether a busy skimmer would even open a post, what readers will remember or take away tomorrow, where readers stop reading or bounce, or why a draft still feels off or hollow after anti-slop or humanizer edits. Final gate before publishing; reports where the reading broke; never rewrites.

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

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 well-engineered orchestration skill: concrete commands with flags and fallbacks, a mechanism-enforced sequence with genuine error-recovery loops, and clean one-level-deep separation into real reference and script files. Its only cost is length — roughly 300 lines with a few constraints restated in multiple sections — which keeps it just short of maximal token efficiency.

Suggestions

State the work-silently rule once (in the user contract, which already declares it overrides everything) and reference it from Step 0 and Adapting instead of restating it.

Merge the never-rewrite/no-fixes rule in Guardrails with the user contract's 'No numbered fixes, no suggestions' bullet so it appears once.

The 'first time the skill runs' teaching line in Adapting duplicates the starting-line wording from the user contract; point to it rather than repeating the full sentence.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence — it never explains basic concepts, and its length is mostly load-bearing commands, dispatch-prompt specs, and fallbacks. However, a few constraints are repeated across sections (work silently appears in the user contract, Step 0, and Adapting; never-rewrite appears in both the user contract and Guardrails), so it is not fully lean. Above anchor 3 because the duplication is deliberate reinforcement of critical rules rather than padded explanation.

4 / 5

Actionability

Guidance is fully executable: exact invocations like 'python3 scripts/feed.py serve <draft> --run <run-dir> --readers keen,skeptic --persona "keen=<one line>" ... --ready-file <run-dir>/feed.json', per-step subcommands ('feed.py next --log "needle=<-2..+2> expected... got..."', 'feed.py quit', 'feed.py transcript'), plus recall.py, signals.py, skim.py, ask.py, and room.py commands with flags and a concrete fallback (file mode) when subagents are unavailable. This is instruction-only but copy-paste actionable throughout.

5 / 5

Workflow Clarity

Steps 0–7 are explicitly sequenced with hard ordering constraints enforced by mechanism ('Start the feed in the background BEFORE dispatching any reader', signals.py 'only after the timed reads are complete'), a genre-dispatch gate up front, and error-recovery loops ('feed.py close --admin ... flushes early if a reader dies', 'if the cast was wrong for the piece, recast and rerun', 'If the log cannot support an answer, the reader says so'). Checkpoints (skim-gate verdict, recall judged against intended gist) are explicit.

5 / 5

Progressive Disclosure

The SKILL.md body is a workflow overview, and all detail is pushed one level deep to real, clearly signaled files: 'Read references/personas.md', 'per references/room.md', 'exactly as references/report.md specifies', 'per references/interview.md' — all four exist in the bundle, alongside a scripts/ directory whose seven files are all invoked by name. No nested references (the single interview.md → room.md mention is a sibling pointer, not a content chain).

5 / 5

Total

19

/

20

Passed

Description

96%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.

An exemplary description: concrete mechanism list, explicit and exhaustive trigger guidance in third person, and a clear niche statement. The only weakness is a couple of overly broad trigger terms ('human review', 'reader review') that could occasionally pull requests meant for other review skills.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete mechanisms — 'a skim gate, a no-lookahead timed read producing an attention transcript with quit points, a recall test of what a reader remembers the next day, and a trust ledger of the implied author' — plus the outcome ('reports where the reading broke; never rewrites'), which comprehensively covers what the skill does. It stays in third person and contains no filler; the length is dense with named actions, not padding.

5 / 5

Completeness

It explicitly answers both questions: 'what' is stated up front ('Beta readers for any draft, run by simulating how a real reader experiences it, moment by moment' plus the four mechanisms), and 'when' is an explicit 'Use when the user asks for...' clause with concrete trigger phrases. This matches the anchor-5 example pattern exactly.

5 / 5

Trigger Term Quality

The 'Use when' clause covers an unusually rich set of natural phrases users would actually say: 'a beta read, beta readers, test readers, human review, reader review, to read something like a human, to be a first reader, whether a piece holds attention or will actually get read, ... where readers stop reading or bounce'. Synonyms and colloquial variants are all present.

5 / 5

Distinctiveness Conflict Risk

The niche is clear (beta reading of drafts, final pre-publish gate) and most triggers ('beta read', 'first reader', 'skimmer', 'where readers stop reading') are distinctive, but 'human review' and 'reader review' are broad enough to minor-overlap with general review skills. Not anchor 5 ('minimal conflict risk') because of those two generic terms; clearly above anchor 3 since the skill's identity and complementary position ('after anti-slop or humanizer edits') are unmistakable.

4 / 5

Total

19

/

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

Shubhamsaboo/awesome-llm-apps

Path

agent_skills/first-reader/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.