CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pre-flight-check

[Beta] Session-start scan that surfaces relevant learnings, recent errors, and eval status before work begins. Bridges the outer loop back into the inner loop by making accumulated knowledge visible at task start. Activated via SessionStart hook or manually before major tasks.

Quality

73%

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 ./plugin/skills/pre-flight-check/SKILL.md

The canonical home for this skill is pre-flight-check in pskoett/pskoett-ai-skills

SKILL.md
Quality
Evals
Security

Quality

Content

67%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-structured, largely actionable instruction skill with a real, working hook script and a clearly sequenced manual workflow. Its main weaknesses are padding in the motivational sections, an unimplemented future-enhancement section, and a documented hook output format that has drifted from what the bundled script actually prints.

Suggestions

Delete or compress the 'The Compounding Effect' section and the motivational prose in the intro ('the agent repeats mistakes... because nobody told it to look') — they restate the purpose without adding executable guidance.

Remove or shrink the 'Incremental Scanning (future enhancement)' section to a one-line note; detailed design for unimplemented caching does not belong in the working skill body.

Update the 'Hook Output' example to match the actual output of scripts/pre-flight.sh (pipe-delimited summary line, per-signal recommendation lines) and drop the 'last 7 days' claim the script does not implement, so the documented behavior matches execution.

DimensionReasoningScore

Conciseness

The body is mostly efficient — structured sections, file paths, and field names with little concept explanation Claude wouldn't know — but includes padded passages: 'the agent repeats mistakes that were already captured because nobody told it to look', the entire 'The Compounding Effect' section ('Every learning captured, every rule promoted... The knowledge gaps get smaller with every cycle'), and the 'Incremental Scanning (future enhancement)' paragraph about unimplemented functionality. These match the level-3 anchor of mostly efficient with some unnecessary content that could be tightened, not the severe padding of 2 or the lean level of 4-5.

3 / 5

Actionability

The manual deep scan gives concrete, executable guidance: exact files to read ('.learnings/LEARNINGS.md', '.evals/EVAL_INDEX.md'), exact fields to extract, explicit filter thresholds ('Recurrence-Count >= 3', 'Priority: high/critical'), and fully specified output templates; the hook delegates to a real executable script. It falls short of 5 because the documented hook output format diverges from what scripts/pre-flight.sh actually emits (the doc's 'High-priority items: [Pattern-Key]' list and 'last 7 days' filtering do not exist in the script), leaving minor gaps between instruction and execution.

4 / 5

Workflow Clarity

The manual scan is a clearly sequenced 5-step process (scan learnings → scan evals → check handoffs → relevance filter → output), matching 'clear sequence with most checkpoints present'. Validation checkpoints are largely inapplicable since the skill is explicitly read-only and non-blocking ('Does not modify .learnings/ files', 'Does not block execution'), so the level-5 requirement of explicit validation/feedback loops for risky operations does not apply; minor gaps (e.g., what to do when expected files are missing or malformed) keep it at 4 rather than 5.

4 / 5

Progressive Disclosure

Structure is good: the body is a well-organized overview with clear section headers, and its single bundle reference ('scripts/pre-flight.sh') is real, correctly pathed, and one level deep with no nested reference chains. Minor organization gaps keep it below 5: the two full output templates (hook + manual) are inlined in full, the 'Incremental Scanning' future-design discussion sits in the body rather than being deferred or dropped, and the hook output spec duplicates (and drifts from) the script's actual behavior.

4 / 5

Total

15

/

20

Passed

Description

67%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 solid description with a clear 'what' and an explicit activation ('when') clause, held back by weak trigger-term coverage. It reads as mechanism-oriented ('SessionStart hook', 'outer loop') rather than user-intent-oriented, so a user needing it might not naturally say these words.

Suggestions

Add a 'Use when...' clause with natural user phrasings, e.g. 'Use when starting a new session, resuming work on a project, or before beginning a major task to surface past learnings, errors, and failed evals.'

Include common synonyms and variations users would say — 'new session', 'previous sessions', 'past mistakes', 'known issues', 'start of work' — to improve trigger-term coverage.

Replace the conceptual 'Bridges the outer loop back into the inner loop' sentence with a concrete capability statement or move it after the concrete actions, since it adds abstraction without actionable information.

DimensionReasoningScore

Specificity

The description names several concrete actions — 'surfaces relevant learnings, recent errors, and eval status before work begins' — which matches the anchor for several specific actions with minor coverage gaps. It falls short of a 5 because 'Bridges the outer loop back into the inner loop by making accumulated knowledge visible' is conceptual framing rather than a concrete capability, and it is above 3 because more than 1-2 concrete actions are explicitly stated.

4 / 5

Completeness

Both 'what' (surfaces learnings, recent errors, eval status) and 'when' ('Activated via SessionStart hook or manually before major tasks') are explicitly present, matching the level-4 anchor where the 'when' exists but could be more specific with concrete user trigger phrases. It is not a 5 because it lacks a 'Use when...' clause with explicit trigger conditions a user would actually say, and not a 3 because the 'when' is explicitly stated rather than merely implied.

4 / 5

Trigger Term Quality

Some relevant natural keywords are present ('session-start scan', 'learnings', 'recent errors', 'before work begins'), matching the 'some relevant keywords but missing common variations' anchor. It misses common user phrasings like 'new session', 'previous sessions', 'past mistakes', or 'check what we already learned', so it does not reach the good-coverage level of 4.

3 / 5

Distinctiveness Conflict Risk

The niche is distinct — a session-start knowledge scan tied to specific artifacts (.learnings/, eval status, SessionStart hook) with minimal overlap risk, matching 'mostly distinct; minor overlap risk with closely related skills'. Minor overlap remains with closely related skills it references (context-surfing/handoff-checker), keeping it below 5.

4 / 5

Total

15

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

pskoett/pskoett-ai-skills

Path

plugin/skills/pre-flight-check/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.