CtrlK
BlogDocsLog inGet started
Tessl Logo

create-issue-gate

Use when starting a new implementation task and an issue must be created with strict acceptance criteria gating before execution.

61

Quality

72%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/create-issue-gate/SKILL.md

The canonical home for this skill is create-issue-gate in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 a tight, highly actionable gate workflow with a concrete command, a full issue template, and an explicit acceptance-criteria checkpoint. Its only real gaps are minor status-value repetition and a hand-off rather than a full retry loop.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence with no concept padding, but the Status values are restated across the Required Fields list, Status Rules, and the template, leaving minor redundancy that fits anchor 4 rather than 5.

4 / 5

Actionability

It provides a concrete command ("gh issue create"), a copy-paste body template, concrete valid/invalid acceptance-criteria examples, and explicit status definitions, fully covering the common case per anchor 5.

5 / 5

Workflow Clarity

The create -> gate -> set-status -> block/allow-execution sequence is clear with the acceptance-criteria gate as an explicit checkpoint and a recovery path ("stop and request user-provided acceptance criteria"), but the recovery is a hand-off rather than a validate-fix-retry loop, matching anchor 4.

4 / 5

Progressive Disclosure

No bundle files exist, so the single self-contained SKILL.md is appropriately organized into well-labeled sections (Overview, Required Fields, Gate, Template, Status Rules, Handoff) with no nested references, fitting anchor 4; it is slightly over the simple-skill line count so not a 5.

4 / 5

Total

17

/

20

Passed

Description

62%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 well-formed with an explicit "Use when..." trigger and a concrete gating concept, landing above average on completeness and distinctiveness. It is held back by compressed action coverage and some jargon in the trigger phrasing.

Suggestions

Expand the "what" into a short action list (e.g. "Create GitHub issues with required fields and block execution until acceptance criteria are testable") to lift specificity toward 4-5.

Swap jargon like "gating before execution" for natural phrasing such as "block work until the criteria are testable" to improve trigger-term quality.

Add common synonyms a user might say (e.g. "task", "ticket", "definition of done") to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain ("an issue must be created") and the concrete gating action ("strict acceptance criteria gating before execution"), but coverage stays at 1-2 actions rather than a comprehensive action list, matching anchor 3.

3 / 5

Completeness

Both halves are present: the explicit "Use when starting a new implementation task..." trigger plus a clear "what" (create an issue gated by acceptance criteria), but the "what" is compressed into the trigger clause so it is not maximally explicit, matching anchor 4.

4 / 5

Trigger Term Quality

It includes some natural phrases a user might say ("starting a new implementation task", "issue", "acceptance criteria") but leans on jargon like "gating before execution" and lacks common synonyms, fitting anchor 3 rather than 4.

3 / 5

Distinctiveness Conflict Risk

The issue-creation-with-acceptance-gate niche is fairly distinct with minimal overlap against generic task skills, though "new implementation task" is broad enough to risk minor overlap with other delivery skills, matching anchor 4.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-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.