CtrlK
BlogDocsLog inGet started
Tessl Logo

human-gate

Runs the human-verification lane of an agent loop, and proves review happened before work is called done. Builds a single-file HTML review page, collects batched feedback as a structured artifact instead of chat prose, and runs a gate that refuses to close while a BLOCKER is open, the reviewer is unnamed, or nobody has reviewed at all. Use when a plan, spec, RFC, report, landing page, migration, or any irreversible action needs human sign-off before shipping, or on requests such as 'get sign-off', 'have someone check this', 'hold until reviewed', 'needs approval first'. NOT for making AI text sound human (use content-humanizer or behuman). NOT for reviewing code diffs (use md-review or code-reviewer).

77

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 tightly structured, operational SKILL.md with executable commands, an explicit gate-validated workflow, and well-signaled one-level-deep references to a real bundle. Only minor conciseness trimming would push it to a perfect score.

Suggestions

Tighten the opening positioning prose ("Machine verification answers ... This answers what no script can") into a single clause so the first tokens are operational rather than expository.

The conditional pointer "Read human-gate-context.md first if it exists" references a file not present in the bundle; either add it or drop the reference to avoid a dangling pointer.

DimensionReasoningScore

Conciseness

The body is dense and mostly earns its tokens, but the opening framing ("Machine verification answers ... This answers what no script can") and some positioning prose could be trimmed without losing actionability; not a 5 only because of those minor expository passages.

4 / 5

Actionability

Copy-paste-ready command block (open/status/collect/close with flags and exit codes), a concrete sidecar example, and explicit severities give fully executable guidance covering the common cases.

5 / 5

Workflow Clarity

The loop is clearly sequenced (open → status → collect → close) with explicit validation checkpoints: `close` exit 2 means not done, non-blocking status codes, G1–G7 gate rules, and round-cap escalation — feedback loops are present for this batch/gate operation.

5 / 5

Progressive Disclosure

SKILL.md is a lean overview with one-level-deep, clearly signaled pointers to existing bundles — "Reasoning lives in references/", "Worked example and JSON contract are in assets/" — and the referenced files (references/×3, scripts/×3, assets/×2) are all present.

5 / 5

Total

19

/

20

Passed

Description

100%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 strong, third-person description that concisely states concrete capabilities, explicit use-when triggers with natural user phrasing, and sharp NOT-for boundaries that disambiguate it from sibling skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Builds a single-file HTML review page", "collects batched feedback as a structured artifact", and "runs a gate that refuses to close while a BLOCKER is open, the reviewer is unnamed, or nobody has reviewed at all" — with comprehensive coverage and no vague filler.

5 / 5

Completeness

Explicitly answers both what (builds page, collects feedback, runs gate) and when ("Use when a plan, spec, RFC, report, landing page, migration, or any irreversible action needs human sign-off before shipping") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural phrases users would say are present verbatim — "'get sign-off'", "'have someone check this'", "'hold until reviewed'", "'needs approval first'" — alongside concrete artifacts (plan, spec, RFC, report, landing page, migration).

5 / 5

Distinctiveness Conflict Risk

Clear niche (human sign-off lane) plus explicit negative boundaries — "NOT for making AI text sound human (use content-humanizer or behuman)" and "NOT for reviewing code diffs (use md-review or code-reviewer)" — minimizing conflict risk.

5 / 5

Total

20

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
alirezarezvani/claude-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.