CtrlK
BlogDocsLog inGet started
Tessl Logo

ticket-intake

Authoritative protocol defining the "Pre-Execution Reflection Gate". Mandates architectural validation, negative ROI calculation, and duplicate sweeps before an agent is permitted to begin working on a GitHub Issue. Triggers: Use this skill immediately when assigned a ticket whose authoring you did NOT see, before checking out a branch or writing any codebase modifications. A ticket YOU authored this session is exempt; one you authored in an earlier session runs a cheap drift probe instead — never an exemption you judge for yourself.

67

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/ticket-intake/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A deliberately terse overview that excels at conciseness and progressive disclosure, correctly offloading detail to real reference files. Actionability and workflow clarity are capped at 2 because the body delegates nearly all executable/sequential detail to the referenced workflow rather than carrying a minimal inline skeleton.

Suggestions

Add a one-line inline summary of the gate's first concrete step (e.g. the validation-sweep order) so the body is actionable without opening the reference.

Surface a minimal validation checkpoint inline ('do not branch until the sweep, ROI, and duplicate checks pass') so the workflow's gating intent is visible in SKILL.md itself.

DimensionReasoningScore

Conciseness

The body is extremely lean — five short lines that assume Claude's competence, delegate detail to references, and add no concept explanations; every token earns its place.

3 / 3

Actionability

It names a concrete tool (`view_file`) and a concrete path, but the core instruction ('read and strictly adhere to ... before proceeding') points to a reference rather than giving executable steps inline; the concrete action is delegated.

2 / 3

Workflow Clarity

The sequence is present and unambiguous (do not begin; read the workflow; or use payload; self-authored carve first), but validation checkpoints and the multi-step ordering live entirely in the referenced 31KB workflow rather than in the body itself.

2 / 3

Progressive Disclosure

Clear overview with well-signaled, one-level-deep references (ticket-intake-workflow.md, self-authored-carve.md) that are real files in ./references/, and content is appropriately split rather than inlined.

3 / 3

Total

10

/

12

Passed

Description

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

A specific, complete, and distinctive description with explicit trigger guidance and concrete mandated actions. It is slightly verbose and could use more natural user-facing keywords, and the third-person voice guideline is met ('Mandates...', 'Triggers: Use...').

Suggestions

Add natural-language keywords a user might actually say (e.g. 'ticket', 'issue', 'before I start coding', 'is this ticket still valid') to improve trigger-term coverage.

Tighten the long same-session/earlier-session carve clause; the exemption detail can live in the body rather than the description.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'architectural validation', 'negative ROI calculation', and 'duplicate sweeps' — rather than vague abstractions.

3 / 3

Completeness

Clearly states what the skill does (mandates validation, ROI, duplicate sweeps before work) and gives an explicit 'Triggers: Use this skill immediately when...' clause answering when.

3 / 3

Trigger Term Quality

It includes 'GitHub Issue' and 'ticket' but natural trigger phrasing a user would say is thin; the language is procedural ('assigned a ticket', 'checking out a branch') rather than keyword-rich.

2 / 3

Distinctiveness Conflict Risk

The Pre-Execution Reflection Gate niche tied to tickets whose authoring the agent did not see is a distinct trigger unlikely to fire for other skills.

3 / 3

Total

11

/

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.