CtrlK
BlogDocsLog inGet started
Tessl Logo

engram-issue-creation

Issue creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a GitHub issue, reporting a bug, or requesting a feature.

75

Quality

92%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with executable gh commands and a well-gated approval workflow, organized into clear sections. Its main weakness is token redundancy from two inline example bodies that duplicate the field tables above them.

Suggestions

Trim the two inline `gh issue create --body` examples so each shows only a couple of filled fields rather than restating every field already documented in the Required Fields tables.

Move the full worked example bodies into a short reference snippet or collapse one example, keeping one canonical bug and one feature example rather than near-complete duplicates of the template structure.

Consider extracting the two large template-field tables into a referenced file only if the skill grows; for now keep them inline but ensure examples reference fields by name instead of reproducing them.

DimensionReasoningScore

Conciseness

Tables, critical rules, and the decision tree are dense and assume Claude's competence, but the two full inline `gh issue create --body` examples restate the field structure already given in the Required Fields tables, duplicating content that could be tightened.

2 / 3

Actionability

It provides fully executable `gh issue create/edit` commands, real copy-paste template bodies with concrete titles and labels, and an explicit Commands section — copy-paste ready rather than pseudocode.

3 / 3

Workflow Clarity

A clear numbered workflow (search → template → fill → pre-flight → submit → wait for approval → PR) with an explicit gate (maintainer must add status:approved before a PR) and a maintainer approval loop with approve/comment-close branches.

3 / 3

Progressive Disclosure

It is a self-contained, single-file skill with no external references needed and clear sections (When to Use, Critical Rules, Workflow, Templates, Labels, Approval, Decision Tree, Commands); no nested/deep references to penalize.

3 / 3

Total

11

/

12

Passed

Description

100%

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 concise, third-person, and answers both what and when with an explicit trigger clause. It is a strong, specific, low-conflict description.

DimensionReasoningScore

Specificity

"Issue creation workflow for Engram" names the domain and pairs it with concrete actions — "creating a GitHub issue, reporting a bug, or requesting a feature" — listing multiple specific actions rather than vague language.

3 / 3

Completeness

It states what ("Issue creation workflow for Engram following the issue-first enforcement system") and an explicit when ("Trigger: When creating a GitHub issue..."), satisfying both halves with an explicit trigger clause.

3 / 3

Trigger Term Quality

"When creating a GitHub issue, reporting a bug, or requesting a feature" uses natural phrases a user would actually say; matches the rubric's good-coverage anchor though it omits a few variations like "file an issue".

3 / 3

Distinctiveness Conflict Risk

Scoping to "Engram" and the "issue-first enforcement system" with GitHub-issue-specific triggers carves a clear niche unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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/engram
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.