CtrlK
BlogDocsLog inGet started
Tessl Logo

structural-pre-flight

Authoritative pre-implementation discipline gate that fires when a new `.mjs` file is about to be authored. Stage 0 mechanical trigger; Stage 1 fast-path (sibling-file-lift pattern match) for matched patterns OR full Pre-Flight (ArchitectureOverview.md + ADR consultation + chief-architect framing) for novel directory choices. Closes the 0th-level discipline gap empirically demonstrated by `ai/daemons/wake/daemon.mjs` (originally misplaced in `ai/scripts/` as `bridge-daemon.mjs`) and `orchestrator-daemon.mjs` (PR #11008 same-class miss). Triggers: Use this skill before authoring or relocating any new `.mjs` file. Fires from `ticket-create` Stage 3 (Substrate), `ticket-intake` validation, `epic-review` Stage 3, and any direct authoring path. Sibling pattern match → 30-second fast-path; novel directory choice → full structural pre-flight before the file is written.

68

Quality

81%

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

87%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 lean, actionable overview that delegates appropriately to a single well-structured reference file; its only gap is that the two-stage workflow's validation checkpoints are not surfaced in the body itself.

DimensionReasoningScore

Conciseness

The body is three lean paragraphs that assume Claude's competence and delegate detail to the reference ('read and strictly adhere to ...workflow.md'), with every token earning its place, matching the score-3 lean-and-efficient anchor.

3 / 3

Actionability

It gives a concrete, executable instruction — 'use the view_file tool to read and strictly adhere to [specific path]' — naming both the tool and the exact file path; per the instruction-only scoring note, absence of code is not penalized when guidance is this actionable.

3 / 3

Workflow Clarity

Two stages are named ('30-second sibling-pattern fast-path AND a full Pre-Flight for novel directory choices') but the body shows no explicit validation checkpoints or error-recovery feedback loop for a file-authoring operation; the verification hooks live only in the reference, so the cap-at-2 guideline for missing validation in destructive/batch operations applies.

2 / 3

Progressive Disclosure

The body is a clear overview pointing one level deep to a real, well-organized reference file (structural-pre-flight-workflow.md, 224 lines with numbered sections), with the path clearly signaled — matching the score-3 anchor of a well-signaled one-level-deep reference.

3 / 3

Total

11

/

12

Passed

Description

75%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 complete and distinctive with an explicit 'Use when' trigger, but its concrete actions and natural trigger terms are diluted by dense internal jargon and case-specific history (PR numbers, daemon filenames) that pad rather than clarify.

Suggestions

Lead with the natural trigger ('Use before authoring or relocating any .mjs file') and demote the case-history evidence (daemon.mjs misplacement, PR #11008) into the reference file so the description stays clean.

Replace internal stage jargon ('Stage 0 mechanical trigger', 'sibling-file-lift') with plain action verbs a user would actually say ('check whether a sibling .mjs already lives in the target directory').

Trim over-claims like 'Authoritative ... discipline gate' and 'empirically demonstrated' — they read as fluff and do not add trigger value.

DimensionReasoningScore

Specificity

Concrete actions are named ('sibling-file-lift pattern match', 'ADR consultation', 'chief-architect framing', 'authoring or relocating any new .mjs file'), but they are wrapped in heavy meta-framing ('Authoritative pre-implementation discipline gate', 'Stage 0 mechanical trigger', '0th-level discipline gap') that obscures the clean action verbs seen in the score-3 anchor.

2 / 3

Completeness

It explicitly answers what the skill does (two-stage pre-flight gate) and when to use it via the explicit clause 'Triggers: Use this skill before authoring or relocating any new .mjs file', matching the score-3 anchor that requires both what AND when with explicit triggers.

3 / 3

Trigger Term Quality

Natural trigger terms exist ('authoring or relocating any new .mjs file', 'new module, daemon, service, script, helper'), but they are buried under internal jargon ('ticket-create Stage 3 (Substrate)', 'epic-review Stage 3', 'PR #11008 same-class miss') that a user would not naturally say, so coverage of common variations is incomplete.

2 / 3

Distinctiveness Conflict Risk

The niche is narrow and distinct — structural placement of .mjs files before authoring — with a trigger unlikely to fire for unrelated skills, matching the score-3 anchor of a clear niche with distinct triggers; references to sibling skills denote integration, not conflict.

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