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

74%

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 ./skills/pre-flight-check/SKILL.md
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 concrete file paths, filter rules, and output templates, plus a real supporting script. Its weaknesses are padded sections (compounding-effect prose, a future-enhancement design note) that dilute token efficiency, and a few small gaps such as the unstated manual invocation method.

Suggestions

Cut or compress 'The Compounding Effect' and 'Incremental Scanning (future enhancement)' sections to one or two lines each (or move the caching design into a comment in pre-flight.sh) to improve token efficiency.

State explicitly how the manual deep scan is invoked (e.g., a slash command or 'ask me to run a pre-flight check on [area]') so the primary action is unambiguous.

Clarify the reference to handoff-checker.sh — either drop it (Step 3 already describes the check inline) or note it is a sibling skill's script, since it is not part of this skill's bundle.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete steps, field lists, and output templates, but 'The Compounding Effect' section and the unimplemented 'Incremental Scanning (future enhancement)' section are motivational/speculative padding that could be cut. The 'Without this...' motivation paragraph also explains what is already evident from the skill's purpose.

3 / 5

Actionability

Names exact files to read (.learnings/LEARNINGS.md, ERR.md, FEATURE_REQUESTS.md, HEALS.md, .evals/EVAL_INDEX.md), the fields to extract, explicit filter rules, copy-ready output templates for both hook and manual modes, and references the real scripts/pre-flight.sh. Minor gap: how to invoke the manual deep scan (command or trigger) is never stated, and the .learnings entry format is assumed.

4 / 5

Workflow Clarity

Steps 1-5 are clearly sequenced with an explicit decision gate (relevance filter with concrete criteria: Area match, file overlap, Priority high/critical, Recurrence-Count >= 3) and conditional handling ('if exists'). Not 5 because there is no guidance for malformed or partially missing Step-1 files, and the hook/manual modes' relationship to each other could be tighter. The read-only nature means the destructive/batch validation cap does not apply.

4 / 5

Progressive Disclosure

The body's bundle reference (scripts/pre-flight.sh) is a real, verified file and is clearly signaled; sections are well-organized and the ~125-line body is appropriate overview material. Not 5 because handoff-checker.sh is referenced as if bundled but does not exist in the bundle, and the hook output example duplicates detail that could live in or beside the script.

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 that states concrete capabilities and explicit activation triggers in third person. Its main weaknesses are trigger-term coverage (missing natural synonyms like 'pre-flight' or 'past mistakes' in favor of loop jargon) and slightly incomplete action coverage relative to what the skill actually surfaces.

Suggestions

Replace or trim the jargon sentence 'Bridges the outer loop back into the inner loop' and add natural trigger terms such as 'pre-flight check', 'past mistakes', or 'handoff files'.

Mention the additional surfaced signals (handoff files, verified fixes) so the capability list matches the body.

Consider a 'Use when...' phrasing tied to user situations (e.g., 'Use when starting a session on a project with accumulated learnings or before tackling a major task').

DimensionReasoningScore

Specificity

'Session-start scan that surfaces relevant learnings, recent errors, and eval status' names the domain and several concrete actions. Not 5 because coverage has gaps — the body also surfaces handoffs and verified HEALS fixes, which the description omits; not 3 because it lists more than 1-2 concrete actions.

4 / 5

Completeness

Clearly answers what ('surfaces relevant learnings, recent errors, and eval status before work begins') and has explicit when-equivalent trigger guidance ('Activated via SessionStart hook or manually before major tasks'), so it is not capped at 3. Not 5 because the 'when' describes the activation mechanism rather than concrete user-side trigger phrases ('Use when...').

4 / 5

Trigger Term Quality

'learnings', 'recent errors', and 'eval status' are relevant keywords, but 'Bridges the outer loop back into the inner loop' is internal jargon users would not say, and natural variations like 'pre-flight', 'past mistakes', 'prior sessions', or 'handoffs' are missing. Fits 'some relevant keywords but missing common variations or synonyms' rather than 'good coverage, a few missing'.

3 / 5

Distinctiveness Conflict Risk

'Session-start scan' is a distinct niche trigger unlikely to fire for unrelated skills. Not 5 because the terms 'learnings' and 'eval status' overlap with sibling skills in the same loop (learning-aggregator, eval-creator), creating minor wrong-skill trigger risk; not 3 because the session-start timing anchor keeps it mostly distinct.

4 / 5

Total

15

/

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

pskoett/pskoett-ai-skills

Path

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.