CtrlK
BlogDocsLog inGet started
Tessl Logo

lane-intent

Narrow, non-authoritative, TTL-bound pre-V-B-A signal for collision-prone / high-blast / long-V-B-A lanes (deep memory-mining, tech-debt-radar, multi-turn architectural V-B-A). Distinct from authoritative `[lane-claim]` (post-V-B-A). Triggers: Use this skill BEFORE broadcasting `[lane-intent] evaluating #N` to confirm scope-trigger qualifies — narrow scope, not blanket coverage. Do NOT auto-fire for short single-turn V-B-A where direct `[lane-claim]` after V-B-A suffices.

64

Quality

75%

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 ./.agents/skills/lane-intent/SKILL.md
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 an exemplary lean overview: it defers detail to a single, clearly-signaled reference file that exists in the bundle, gives a verbatim required payload line, and sequences the read-before-broadcast action unambiguously. No changes needed.

DimensionReasoningScore

Conciseness

The body is a lean three-paragraph overview with no concept padding; it assumes Claude's competence and every line (read the protocol, source of authority, required first payload line) earns its place.

3 / 3

Actionability

For an instruction-only skill it gives fully actionable guidance: a specific file path to read and a verbatim 'First payload line MUST declare: "..."' string that is copy-paste ready.

3 / 3

Workflow Clarity

As a simple skill the single action is unambiguous (read the protocol before broadcasting, then emit the required first line), and the 3-condition scope-trigger gate is explicitly referenced as the gating checkpoint.

3 / 3

Progressive Disclosure

The body is a concise overview that points one level deep to a real bundle file (references/lane-intent-protocol.md), clearly signaling what it contains (scope-trigger gate, TTL+recovery semantics, anti-patterns).

3 / 3

Total

12

/

12

Passed

Description

50%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 highly distinctive, with explicit positive and negative triggers and a clear contrast against the sibling lane-claim skill. Its weaknesses are voice (second-person imperative) and trigger-term quality, being saturated with project-internal jargon that no user would naturally utter.

Suggestions

Rewrite the description in third person (e.g. 'Emits a narrow, non-authoritative, TTL-bound pre-V-B-A signal...') instead of the second-person imperative 'Use this skill BEFORE broadcasting' to avoid the specificity voice penalty.

Replace or supplement internal jargon ('V-B-A', 'high-blast', 'scope-trigger') with natural user-facing trigger phrases so the skill surfaces when a user actually describes the relevant situation.

Lead with one concrete capability verb before the qualifying conditions, so the 'what it does' reads as an action rather than only a signal-classification.

DimensionReasoningScore

Specificity

Names a domain and some actions ('deep memory-mining, tech-debt-radar, multi-turn architectural V-B-A') but describes an abstract signaling protocol rather than concrete CRUD-style actions; reduced from a base of 2 by the second-person imperative 'Use this skill BEFORE broadcasting' per the voice guideline.

1 / 3

Completeness

It explicitly answers both what ('Narrow, non-authoritative, TTL-bound pre-V-B-A signal') and when with explicit triggers ('Use this skill BEFORE broadcasting...', 'Do NOT auto-fire for short single-turn V-B-A'), so it is not capped at 2.

3 / 3

Trigger Term Quality

The description is dominated by internal jargon ('V-B-A', 'high-blast', 'TTL-bound', 'scope-trigger', 'lane-claim', 'lane-intent evaluating #N') rather than natural keywords a user would actually say, matching the 'technical jargon' anchor.

1 / 3

Distinctiveness Conflict Risk

It carves a clear niche (collision-prone / high-blast / long-V-B-A lanes) and explicitly contrasts itself with 'authoritative [lane-claim] (post-V-B-A)', making a wrong-skill trigger unlikely.

3 / 3

Total

8

/

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.