CtrlK
BlogDocsLog inGet started
Tessl Logo

github-issue-creator

Transform messy input (error logs, voice notes, screenshots) into clean, actionable GitHub issues.

54

Quality

61%

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/github-issue-creator/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

68%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 content is well-structured and actionable with a concrete template and examples, but the workflow lacks explicit sequencing and any validation/verification step for the file-creation operation, capping workflow clarity at 3. Conciseness and progressive disclosure are strong.

Suggestions

Add an explicit numbered workflow (e.g. 1. Extract facts from input, 2. Classify severity, 3. Fill template, 4. Check /issues/ for duplicates, 5. Write file) with a validation checkpoint.

Replace the vague final 'When to Use' line with concrete trigger conditions or remove it entirely to tighten conciseness.

Add guidance for screenshot/image inputs beyond the inline reference format, since they are named as a primary input type.

DimensionReasoningScore

Conciseness

The body is mostly lean with a focused output template, guidelines, and worked examples; the only clear filler is the closing 'When to Use' line ('This skill is applicable to execute the workflow or actions described in the overview.').

4 / 5

Actionability

Provides a concrete fill-in output template, an output location with a naming convention, a severity rubric, and two complete worked examples covering common input types; minor gaps such as no instruction for handling screenshots beyond a reference format.

4 / 5

Workflow Clarity

The process is only implicit (parse input -> fill template -> write file) with no explicit sequence or validation checkpoints (e.g. checking for duplicate existing issues before creating a file), which the rubric caps at 3 for batch file-creation without verification.

3 / 5

Progressive Disclosure

No bundle files exist, and the single SKILL.md is organized into clear sections (Output Template, Output Location, Guidelines, Examples); the long worked-examples block is justified inline but keeps this just below a 5.

4 / 5

Total

15

/

20

Passed

Description

53%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 clearly states what the skill does and names concrete input types, but it omits any explicit 'when to use' trigger guidance, which the rubric caps at completeness 3. Trigger term coverage is decent but lacks synonyms.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases (e.g. 'Use when the user pastes an error, dictates a bug by voice, or shares a screenshot to file as a GitHub issue').

Include synonyms users actually say, such as 'bug reports', 'stack traces', 'crash logs', and 'file an issue'.

Consider listing the concrete sub-actions (extract facts, classify severity, format into the issue template) to lift specificity toward 5.

DimensionReasoningScore

Specificity

Names the domain and a concrete action ('Transform messy input (error logs, voice notes, screenshots) into clean, actionable GitHub issues') but covers only a single transform action rather than multiple specific operations.

3 / 5

Completeness

The 'what' is clear (transform messy input into GitHub issues) but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Natural keywords like 'error logs', 'voice notes', 'screenshots', and 'GitHub issues' appear, but there are no synonyms or common variations (e.g. 'bug reports', 'stack traces', 'stacktraces').

3 / 5

Distinctiveness Conflict Risk

The niche is fairly distinct (GitHub issue creation from messy input) with minor overlap risk against general note-taking or summarization skills, but it is not maximally explicit on triggers.

4 / 5

Total

13

/

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.