CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gate-check

Advisor-checked decision gates. Freezes a drafted option set, has an independent external advisor rule it genuine / collapsed / malformed, then verifies the cited grounds before it reaches the user.

Quality

62%

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 ./epistemic-cooperative/skills/gate-check/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

This is a rigorously specified, genuinely novel procedure whose operational design (ordering, precommit, verification, bounded repetition) is strong — the sequencing and validation logic are among its best features. However, it is delivered as an extremely verbose philosophical treatise with no worked examples, no concrete artifact formats, and no progressive disclosure, so a reader pays a massive token cost to extract an executable procedure. The mechanism deserves a 4-5 skill; the writing delivers a 3.

Suggestions

Cut justification-of-justification prose: state each rule and at most one reason, moving the extended rationale (e.g. the multi-clause defenses of ordering and bounds) to a reference file or deleting it — the body could shrink by well over half.

Add one worked example: a sample frozen option set, the actual dispatch file text sent to codex, the precommit record, and the advisor reply with its grounds checked — this would convert the abstract pipeline into copy-adaptable artifacts.

Split detail into one-level-deep reference files (e.g. ADVISOR-INTERFACE.md for the codex adapter and record lifecycle, DISPOSITIONS.md for the full table semantics) and keep SKILL.md as a lean overview of the five phases.

DimensionReasoningScore

Conciseness

The body runs ~250 lines / 53KB of recursive prose in which nearly every rule is stated, then justified, then the justification justified (e.g. 'Everything below exists to keep those apart, including from itself'). It avoids explaining concepts Claude already knows, so it is not a 1, but the pervasive philosophical padding — each paragraph could be cut by more than half without losing operational content — is far past 'several unnecessary explanations'.

2 / 5

Actionability

The phases do enumerate specifics — dispatch exactly four things, ask for four back, precommit two records, run seven verification checks, dispose via a table — which is more than high-level hints. But there is no worked example, no sample dispatch file text, no precommit record format, and no path naming pattern, so an executor must invent the concrete mechanics of every artifact the skill requires.

3 / 5

Workflow Clarity

The pipeline is explicitly sequenced (Phase 0–4) with an exhaustive disposition table, an error-handling table, and genuine bounded feedback loops (re-anchor once, rebuild once, recheck once, every repetition bounded at one). It falls short of 5 because the actual procedure must be excavated from dense nested prose — the sequencing and checkpoints are present but not cleanly legible, which is the 'clearly sequenced' bar the anchor sets.

4 / 5

Progressive Disclosure

Section headers and tables give the document real structure, better than a headerless wall, so it is above a 2. But there are no bundle files at all — no references/, scripts/, or assets/ — and ~250 lines of dense content (the Rules restatements, advisor interface mechanics, record lifecycle, observer semantics) are inlined in SKILL.md where a skill of this complexity should split detail into one-level-deep reference files.

3 / 5

Total

12

/

20

Passed

Description

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

The description communicates a distinctive, mechanism-specific skill in third person, but it is written in the skill's own internal vocabulary rather than user-facing trigger language. It states a clear 'what' while entirely omitting 'when', which limits its discoverability and trigger accuracy.

Suggestions

Add an explicit trigger clause, e.g. 'Use when a decision gate with drafted options is about to be presented and its options may not be genuinely distinct.'

Replace or gloss internal jargon ('genuine / collapsed / malformed', 'cited grounds') with natural user-facing terms like 'options that all lead to the same place' or 'checks the evidence behind each conclusion'.

Include natural synonyms users would say — 'choices', 'decision options', 'second opinion', 'independent check' — to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The description names three concrete staged actions — 'Freezes a drafted option set', 'has an independent external advisor rule it genuine / collapsed / malformed', 'verifies the cited grounds' — in proper third-person voice. It falls short of 5 because the verdict taxonomy and phrases like 'cited grounds' are internal jargon that leave the practical outcome for the user underspecified.

4 / 5

Completeness

The 'what' is clear — a three-stage freeze/adjudicate/verify mechanism — but there is no 'Use when...' clause or any equivalent explicit trigger guidance, which caps completeness at 3 per the rubric. A reader learns what the skill does but never when to reach for it.

3 / 5

Trigger Term Quality

'Decision gates', 'option set', and 'advisor' are semi-natural keywords, but 'genuine / collapsed / malformed' and 'cited grounds' are vocabulary no user would actually say, and common variations like 'choices', 'options', 'second opinion', or 'adversarial check' are absent. It has some relevant keywords but misses the natural phrases and synonyms a user would utter.

3 / 5

Distinctiveness Conflict Risk

'Advisor-checked decision gates' combined with the independent-external-advisor mechanism carves a recognizable niche with distinct triggers. There is minor overlap risk with general decision-review or second-opinion skills, keeping it below 5.

4 / 5

Total

14

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

jongwony/epistemic-protocols

Path

epistemic-cooperative/skills/gate-check/SKILL.md

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.