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.

67

Quality

80%

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 ./skills/issue-creation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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 highly actionable with complete executable examples, clear workflows, and a well-structured decision tree. It is concise and appropriately organized for a self-contained skill with no external bundle dependencies.

DimensionReasoningScore

Conciseness

The body is efficiently organized with tables and terse command examples; a few field-description rows and repeated pre-flight checkboxes in examples add minor padding, but nothing over-explains concepts Claude already knows.

4 / 5

Actionability

Provides fully executable, copy-paste-ready `gh issue create` commands with complete `--body` payloads for both templates, plus a concrete command reference block covering the common cases.

5 / 5

Workflow Clarity

Sequences are clearly numbered (issue workflow and maintainer approval workflow) with a decision tree; validation is implicit via the maintainer approval gate, but there is no explicit verify-before-submit feedback loop for the destructive/batch approval step, keeping it just below 5.

4 / 5

Progressive Disclosure

Well-organized single-file skill under ~230 lines with clear section headers and no nested references; for a self-contained skill with no need for external bundle files, this structure earns the top score.

5 / 5

Total

18

/

20

Passed

Description

75%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 specific, well-scoped to the Engram issue workflow, and includes an explicit trigger clause. It is concise and free of fluff, sitting just below the top tier due to slightly less comprehensive trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain (issue creation) and several concrete actions ('Creating a GitHub issue, reporting a bug, or requesting a feature'), giving solid but not exhaustive coverage of capabilities.

4 / 5

Completeness

Clearly states what the skill does and provides an explicit 'Trigger:' clause for when to use it; the trigger is concrete but slightly less granular than the top anchor's 'Use when...' phrasing.

4 / 5

Trigger Term Quality

Includes natural trigger phrases users would say ('creating a GitHub issue', 'reporting a bug', 'requesting a feature'), though it is missing some synonyms like 'filing an issue' or 'bug report'.

4 / 5

Distinctiveness Conflict Risk

Scoped to Engram's issue-first enforcement with specific triggers, making it distinct from generic issue skills; minor overlap risk with broad GitHub-issue workflows.

4 / 5

Total

16

/

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