CtrlK
BlogDocsLog inGet started
Tessl Logo

he-linear-plan

Convert approved HE cognition into small live-ready Linear execution tracking. Use when strategy, reframe, plan, bug, or source-prompt evidence needs scoped issue, milestone, or project routing with explicit confirmation before any live mutation.

70

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Failed to scan

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Quality

Content

85%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, action-oriented skill body with a clear sequenced procedure, explicit validation/feedback loops, and clean one-level-deep progressive disclosure. The main weakness is mild redundancy across the boundary sections.

DimensionReasoningScore

Conciseness

Dense and lean, assuming Claude's competence without explaining known concepts, but a few boundary lists (Safety Boundaries, Execution Boundaries, Constraints) restate overlapping rules and could be tightened.

4 / 5

Actionability

A concrete 12-step procedure with executable commands (e.g. the check_bluf_structure.py invocation) and a precise status vocabulary, though literal payload templates and routing-map contents are deferred to references rather than shown inline.

4 / 5

Workflow Clarity

A clearly sequenced 12-step procedure with explicit validation checkpoints (step 12 stops at the first failed gate, recording pass/fail/blocked) and reinforced feedback loops in the Failure Mode and Validation sections for this batch/mutation context.

5 / 5

Progressive Disclosure

The body is a navigable overview with a purpose-labeled References section pointing to one-level-deep reference files, and the local bundle (contract.yaml, evals.yaml, task-profile.json) is present and referenced.

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 precise, third-person description that cleanly answers both what the skill does and when to use it, with concrete trigger nouns and a distinct niche. It is slightly jargon-heavy and could add more synonyms, but otherwise strong.

DimensionReasoningScore

Specificity

Names the domain and several concrete routing actions ("scoped issue, milestone, or project routing with explicit confirmation before any live mutation"), with minor coverage gaps around how payloads or labels are handled.

4 / 5

Completeness

Explicitly states what it does ("Convert approved HE cognition into small live-ready Linear execution tracking") and when to use it ("Use when strategy, reframe, plan, bug, or source-prompt evidence needs scoped issue... routing"), with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural trigger nouns a domain user would say ("strategy, reframe, plan, bug, or source-prompt evidence"), but the phrasing is jargon-heavy ("HE cognition") and lacks common synonyms, keeping it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (Linear routing of approved HE cognition) with distinct trigger terms and an explicit confirmation-before-mutation boundary that minimizes overlap with adjacent skills.

5 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
jscraik/Agent-Skills
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.