CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gateguard

PreToolUse fact-forcing gate that denies the first Edit/Write/Bash (including MultiEdit and NotebookEdit) attempt until the agent presents concrete facts (importers, data schemas, verbatim user instruction), then allows retry; A/B-tested at +2.25 quality points. Use when enabling or configuring the GateGuard hook, exempting paths via env vars, or handling first-touch denials.

Quality

75%

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 ./skills/gateguard/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is dense, accurate, and largely actionable, with a clear decision-order sequence and concrete configuration commands. Its dominant weakness is token efficiency: ~700 lines of implementation edge-case rules are inlined into SKILL.md rather than split into reference files. Progressive disclosure suffers further because the referenced detail files do not exist in the bundle.

Suggestions

Move the exhaustive rule enumerations (prior-search credit matching rules, public-surface language lists, comment/whitespace triviality rules) into a references/ file and keep a decision-relevant summary in SKILL.md.

Ship the cited files (docs/gateguard/change-profile.md, docs/gateguard/question-effectiveness.md, scripts/gateguard-report.js) in the bundle or remove/replace the citations, since every deferred-to path currently dangles.

Add the actual hooks.json snippet to Quick Start Option A and an explicit verification step (e.g. confirm the hook fires via GATEGUARD_METRICS) to close the workflow gap.

DimensionReasoningScore

Conciseness

The ~700-line body exhaustively enumerates implementation edge cases (the prior-search credit section alone spans ~120 lines of rules like "a tool-use id that appears more than once never counts" and "commands containing `$( )`, backticks... longer than 8192 characters, never credit") that belong in reference docs. It is noticeably verbose with padded rule detail, though it does not explain concepts Claude already knows, so it stays above the severely-padded anchor.

2 / 5

Actionability

Provides mostly executable guidance: a concrete env-var table with defaults, the report command "node scripts/gateguard-report.js --dir /path/to/state --json", a copy-paste JSON env block, and a numbered order-of-checks. Minor gaps remain — Option A says "Enable it via hooks.json" without showing the hooks.json snippet, and the pip/Option B flow's relationship to the ECC hook is left implicit.

4 / 5

Workflow Clarity

The gate's decision flow is an explicit ordered sequence ("the first rule that applies wins: 1. Exempt... 9. Deny") with batch handling guidance ("Send dependent edits... sequentially, not in a parallel batch") and a retry loop ("present the facts, retry the denied edit, and re-read the file"). The destructive/batch validation cap does not bind since the skill configures a gate rather than performing destructive operations itself; what keeps it from 5 is the absence of an explicit verify-the-setup step in Quick Start.

4 / 5

Progressive Disclosure

Section headers and anchors make the document navigable, but the bundle contains no references/, scripts/, or assets/ directories, so cited paths ("docs/gateguard/change-profile.md", "docs/gateguard/question-effectiveness.md", "scripts/gateguard-report.js", "see the design notes for the full list") dangle, and large rule sets that belong in separate files are inlined. This matches the some-structure-but-inline-heavy anchor rather than the well-placed one, since navigation fails exactly where the body defers detail.

3 / 5

Total

13

/

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.

The description is specific, in third person, and explicitly pairs a concrete capability statement with a "Use when..." trigger clause covering configuration, exemptions, and denial handling. Trigger terms are natural and product-specific, keeping conflict risk low. Only minor coverage gaps (disablement terms, the Bash gate split) keep specificity and trigger quality at 4.

DimensionReasoningScore

Specificity

Names several concrete actions — "denies the first Edit/Write/Bash (including MultiEdit and NotebookEdit) attempt until the agent presents concrete facts (importers, data schemas, verbatim user instruction), then allows retry" — with minor gaps (the destructive/routine Bash split and broader config surface are not mentioned). It exceeds the 1-2-actions anchor and falls just short of comprehensive coverage.

4 / 5

Completeness

Explicitly answers both: what ("PreToolUse fact-forcing gate that denies the first... attempt until the agent presents concrete facts... then allows retry") and when ("Use when enabling or configuring the GateGuard hook, exempting paths via env vars, or handling first-touch denials") with concrete trigger phrases. Both are clearly and explicitly stated, matching the top anchor rather than the merely-adequate one.

5 / 5

Trigger Term Quality

"Use when enabling or configuring the GateGuard hook, exempting paths via env vars, or handling first-touch denials" gives good natural-phrase coverage a user would actually say, plus tool names (Edit/Write/Bash, MultiEdit, NotebookEdit). A few natural terms are missing (e.g. "disable/turn off GateGuard", "hook not firing"), so it does not reach comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

"PreToolUse fact-forcing gate", "GateGuard hook", and "first-touch denials" define a clear product-specific niche with distinct triggers and minimal conflict risk against generic editing or hook skills. The 4 anchor ("minor overlap risk") understates how product-anchored the triggers are.

5 / 5

Total

18

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (714 lines); consider splitting into references/ and linking

Warning

metadata_version

'metadata.version' is missing

Warning

referenced_paths_exist

Referenced path issues: 2 possibly missing (scripts/gateguard-report.js, scripts/hooks/gateguard-fact-force.js), 1 deeper-than-1-level

Warning

Total

13

/

16

Passed

Repository

affaan-m/ECC

Path

skills/gateguard/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.