CtrlK
BlogDocsLog inGet started
Tessl Logo

goal-scoping

Scope a GOAL (release / initiative / major objective) into a few coherent owned LANES — the planning front-end of the epic lifecycle. Convert goals into lanes (not scrap tickets); peers self-select lanes; the planner defines goal+lanes but never assigns a peer. Triggers: before decomposing a release/initiative/major-goal into work; when a goal needs scoping into owned streams; when work is being chased as scattered micro-tickets with no owned lanes; when tempted to skip planning OR to assign peers to lanes.

71

Quality

86%

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

86%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, lean SKILL.md body that cleanly routes to a single organized reference holding the full multi-step process with validation bars. Slight headroom on actionability and in-body workflow sequencing because the concrete steps live in the reference.

DimensionReasoningScore

Conciseness

The body is lean and unpadded — a single routing directive with no re-explanation of concepts Claude already knows; every token earns its place.

5 / 5

Actionability

Gives a concrete, executable instruction (named tool `view_file` and exact path to the workflow reference) and the reference itself holds actionable bars, but the substantive steps are delegated to the reference rather than inlined copy-paste-ready examples.

4 / 5

Workflow Clarity

The body's gating action is unambiguous and routes to a workflow with explicit checkpoints (the lane test, the graduation bar, close-by-goal), but it lacks a fully explicit validate→fix→retry feedback loop in-body.

4 / 5

Progressive Disclosure

Clear overview (trigger + route) pointing to a single, well-signaled, one-level-deep reference that exists and is not further nested, with content appropriately split.

5 / 5

Total

18

/

20

Passed

Description

87%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 strong, third-person description that clearly states both capability and explicit trigger conditions, with concrete domain-specific actions and a distinct niche versus sibling epic skills. Minor room to add synonyms for the most common phrasings.

DimensionReasoningScore

Specificity

Lists several concrete, domain-specific actions ('Scope a GOAL into a few coherent owned LANES', 'Convert goals into lanes (not scrap tickets)', 'peers self-select lanes', 'the planner defines goal+lanes but never assigns a peer') with only minor gaps relative to fully tangible file-ops coverage.

4 / 5

Completeness

Explicitly answers both 'what' (scope a goal into owned lanes — the planning front-end) and 'when' via a dedicated 'Triggers:' block with multiple concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural trigger phrases a user would say ('scattered micro-tickets with no owned lanes', 'before decomposing a release/initiative/major-goal', 'tempted to skip planning OR to assign peers'), with good coverage though a few synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

Carves a clear niche ('planning front-end of the epic lifecycle', goal → owned lanes) and explicitly distinguishes itself from sibling skills via the anti-assignment and anti-scrap-ticket framing, yielding minimal conflict risk.

5 / 5

Total

18

/

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.

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.