CtrlK
BlogDocsLog inGet started
Tessl Logo

engram-branch-pr

PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.

68

Quality

81%

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

87%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 and well-structured, with executable commands, regex patterns, and a clear validation-backed workflow. Minor conciseness gains are available by deduplicating the type listings across the branch, PR-label, and commit tables.

Suggestions

Consolidate the repeated type/label mappings (branch naming, PR type table, conventional commit types) into a single canonical table to reduce redundancy and token cost.

Consider splitting the detailed conventional-commit examples into a reference file if the skill grows, to keep SKILL.md as a lean overview.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence, using tables and tight command blocks rather than prose; it leans efficient with only minor padding (e.g. re-listing branch/commit types in multiple tables) that could be trimmed.

4 / 5

Actionability

It provides fully executable, copy-paste-ready bash commands (git/gh/go test) plus concrete regex patterns, label mappings, and complete PR body templates covering the common cases.

5 / 5

Workflow Clarity

The numbered workflow is clearly sequenced with explicit validation checkpoints (verify status:approved, run unit+e2e tests, wait for 5 automated checks) and an automated-checks table that serves as a verification checklist with feedback on rejection.

5 / 5

Progressive Disclosure

Content is well-organized into clearly signaled sections (When to Use, Critical Rules, Workflow, Branch Naming, PR Body Format, Automated Checks, Conventional Commits, Commands) with no nested references and no bundle files needed; it is slightly dense in one file but appropriately self-contained for a focused workflow skill.

4 / 5

Total

18

/

20

Passed

Description

76%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 strong and complete, clearly stating both what the skill does and when to trigger it, scoped to the Engram issue-first system. It is slightly limited on specificity (a single action family) and could add a few more natural trigger synonyms.

Suggestions

Add one or two more concrete actions to broaden specificity, e.g. '...and verifying linked approved issues before opening a PR'.

Include additional natural trigger phrases such as 'submitting a branch for review' or 'preparing a PR description' to improve keyword coverage.

DimensionReasoningScore

Specificity

It names the domain (PR creation) and a concrete action ('creating a pull request', 'opening a PR', 'preparing changes for review'), but these are all variations of one action rather than multiple distinct concrete actions, so it stops at '1-2 concrete actions'.

3 / 5

Completeness

It explicitly answers both 'what' ('PR creation workflow for Engram following the issue-first enforcement system') and 'when' ('Trigger: When creating a pull request, opening a PR, or preparing changes for review') with concrete trigger phrases.

5 / 5

Trigger Term Quality

It includes natural phrases users say ('creating a pull request', 'opening a PR', 'preparing changes for review') with the synonym 'PR' alongside 'pull request', but lacks the broader vocabulary (e.g. 'submitting', 'reviewing changes') that would make coverage comprehensive.

4 / 5

Distinctiveness Conflict Risk

The Engram-specific 'issue-first enforcement system' framing gives it a clear niche and distinct triggers, with only minor overlap risk against generic git/PR skills.

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.