CtrlK
BlogDocsLog inGet started
Tessl Logo

jbaruch/skill-issue-policy

The codified ticket-handling policy from 'Skill Issue' — a skill, a script, and a rule packaged as one distributable context artifact.

80

1.42x
Quality

92%

Does it follow best practices?

Impact

100%

1.42x

Average score across 1 eval scenario

SecuritybySnyk

Advisory

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

evals-required.mdrules/

alwaysApply:
Yes
description:
Every skill change ships with an eval scenario in the same PR

Evals Required

  • Any PR that ADDS a skill, or CHANGES a skill's behavior, MUST include an eval scenario under evals/ that exercises that behavior — in the same PR.
  • A skill change without a matching evals/ scenario is a blocking violation: request changes, do not merge.
  • This applies to every skill that carries LLM-side judgment. "It's small" or "baseline already does it" is not an exemption here — the eval is the proof, and it ships with the change.

README.md

tile.json