CtrlK
BlogDocsLog inGet started
Tessl Logo

issue-creation

Create and triage GitHub issues from repository evidence. Trigger: issue creation, bug reports, feature requests, or issue approval.

70

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 strong, highly actionable skill body with executable commands, explicit validation checkpoints, and a mandatory privacy review checklist. The only minor gaps are some repeated stop-and-ask phrasing and a fully inline structure that could optionally externalize the privacy table.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence (no explanations of GitHub/issues) and is mostly lean, but the 'stop and ask' / 'never publish' mantras recur across several sections and could be tightened.

4 / 5

Actionability

Copy-paste-ready gh CLI commands cover discovery, duplicate search, web fallback, markdown-template publishing, and no-template fallback, with a concrete LABEL_ARGS construction pattern.

5 / 5

Workflow Clarity

A numbered 7-step workflow is reinforced by explicit validation gates (stop-and-ask on failed discovery, mandatory pre-submission privacy review, triage checklist) with feedback loops for error recovery.

5 / 5

Progressive Disclosure

Sections are clearly organized and self-contained with no nested references, but at ~140 lines all content is inline with no split into reference files, leaving minor organization headroom.

4 / 5

Total

18

/

20

Passed

Description

82%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 well-constructed description that explicitly covers both capability and trigger conditions with concrete, natural phrases. Its only weakness is modest action specificity, listing just two verbs (create, triage) for the domain.

Suggestions

Add one or two more concrete actions to broaden capability specificity, e.g. '...search for duplicates, apply repository labels, and publish via templates or fallback bodies.'

Include a common synonym in the trigger list such as 'tickets' or 'report a bug' to widen natural-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('GitHub issues from repository evidence') and two concrete actions ('Create and triage'), matching the anchor for 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

It clearly states what the skill does ('Create and triage GitHub issues from repository evidence') and explicitly answers when via a concrete 'Trigger:' clause, matching the top anchor.

5 / 5

Trigger Term Quality

The explicit 'Trigger: issue creation, bug reports, feature requests, or issue approval' provides good natural keyword coverage, though a few common synonyms (e.g. 'tickets', 'report a bug') are absent.

4 / 5

Distinctiveness Conflict Risk

The GitHub-issues niche scoped to 'repository evidence' with issue-specific triggers is clearly distinct with minimal overlap risk against other skills.

5 / 5

Total

17

/

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
Gentleman-Programming/gentle-ai
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.