CtrlK
BlogDocsLog inGet started
Tessl Logo

turn-memory-pre-flight

Authoritative protocol for verifying the correct placement and impact of new agentic memory substrate additions. Triggers: Use before inserting or mutating turn-loaded/skill-loaded memory substrate (`AGENTS.md`, `AGENTS_ATLAS.md`, `.agents/skills/**`, `.codex/CODEX.md`, `.claude/CLAUDE.md`, `.agents/ANTIGRAVITY_RULES.md`) to prevent future-session bias.

80

Quality

100%

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

100%Weight 40%Scale 1-3

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

The body is a model of progressive disclosure: a minimal, well-organized overview that delegates all detail to a single real, one-level-deep reference file. It is concise, gives a concrete executable action, and the single step is unambiguous. No improvements needed.

DimensionReasoningScore

Conciseness

The body is three lean lines with no concept explanation or padding — it assumes Claude's competence and every token earns its place, matching the lean-and-efficient anchor rather than the could-be-tightened level 2.

3 / 3

Actionability

Gives a concrete, executable instruction — "Use `view_file` to read `references/turn-memory-pre-flight-workflow.md`" — with a specific tool and verified file path, making the single action copy-paste ready rather than abstract.

3 / 3

Workflow Clarity

This is a simple single-purpose skill whose body states one unambiguous mandatory action (read the reference before mutating substrate); the simple-skill guidance allows workflow clarity to score 3 when the single action is unambiguous, rather than level 2's checkpoint-gap anchor.

3 / 3

Progressive Disclosure

The body is a concise overview with one clearly signaled, single-level reference to `references/turn-memory-pre-flight-workflow.md`, which exists and contains the actual content without further delegation, matching the clear-overview-one-level anchor rather than the inline-or-undersignaled level 2.

3 / 3

Total

12

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 precise, uses third-person/imperative voice, and gives explicit what-and-when guidance with concrete substrate file triggers. It avoids vagueness and over-claiming while staying concise. This is a strong, well-structured skill description.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "verifying the correct placement and impact" and "inserting or mutating" — alongside concrete targets (named substrate files), matching the anchor for multiple specific concrete actions rather than the domain-only level 2.

3 / 3

Completeness

Explicitly answers both what (verifying correct placement and impact of new memory substrate additions) and when ("Triggers: Use before inserting or mutating..."), satisfying the explicit-both anchor rather than the when-implied level 2.

3 / 3

Trigger Term Quality

Uses a natural "Triggers: Use before inserting or mutating..." clause and enumerates the exact substrate file paths an agent would reference, giving good coverage of natural terms rather than the partial level 2.

3 / 3

Distinctiveness Conflict Risk

The narrow niche of memory-substrate placement verification with named harness files is unlikely to fire for unrelated skills, matching the clear-niche anchor instead of the overlapping level 2.

3 / 3

Total

12

/

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
neomjs/neo
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.