CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

engram-backlog-triage

Backlog triage protocol for Engram: audit open issues and PRs, classify each item, infer maintainer ideology from comments, and produce an actionable disposition report. Trigger: Auditing open issues or PRs, triaging the backlog, reviewing contributor submissions as a maintainer, or applying triage to any GitHub repo.

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

75%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 highly actionable, well-sequenced triage protocol with concrete commands, decision rules, and output templates throughout. Its main weaknesses are a redundant prompt-template section that duplicates earlier phases and a monolithic single-file structure where some content would be better placed in reference files.

Suggestions

Remove or drastically shorten the 'Reusable Prompt Template' section — it re-lists the Phase 1 fetch commands and classification steps verbatim; a one-line pointer to adapt the philosophy table would suffice.

Add an explicit post-action verification step (e.g., re-check issue state and linked PR status after closing/merging) to create a validation feedback loop for the destructive batch actions.

Move the report template and/or suggested-comment boilerplate into a references/ file (e.g., references/report-template.md) so SKILL.md stays a lean overview.

DimensionReasoningScore

Conciseness

The body avoids explaining known concepts, but the 'Reusable Prompt Template' section (~25 lines) duplicates the gh fetch commands and classification steps already detailed in Phases 1–2, which is more than a minor trim.

3 / 5

Actionability

Provides copy-paste-ready gh commands with explicit --json field lists, a --jq maintainer-comment filter, per-disposition decision rules, quick-action commands, and a fully worked report template with suggested comment text covering the common cases.

5 / 5

Workflow Clarity

Five phases are clearly sequenced with explicit pre-action checkpoints (approved-issue gate before merge, duplicate confirmation before close, 're-run native validation after issue changes'), but there is no explicit re-verification or error-recovery loop after destructive actions execute.

4 / 5

Progressive Disclosure

Well-organized single file with clear section headers and tables, but at ~275 lines with no bundle files, content like the reusable prompt template and report template is inlined rather than split into reference files.

4 / 5

Total

16

/

20

Passed

Description

88%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 strong description that clearly states concrete capabilities and includes an explicit, natural-language trigger clause. Trigger term coverage and distinctiveness are slightly short of comprehensive, with a few missing synonyms and minor overlap risk against generic PR-review skills.

DimensionReasoningScore

Specificity

Lists four concrete, comprehensive actions — 'audit open issues and PRs, classify each item, infer maintainer ideology from comments, and produce an actionable disposition report' — with no coverage gaps for the domain.

5 / 5

Completeness

Explicitly answers both 'what' (the four named actions) and 'when' via a dedicated 'Trigger:' clause with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Natural trigger phrases like 'triaging the backlog', 'auditing open issues or PRs', and 'reviewing contributor submissions as a maintainer' are present, but common variations such as 'clean up the issue tracker' or 'stale issues' are missing.

4 / 5

Distinctiveness Conflict Risk

The maintainer backlog-triage niche is mostly distinct, but 'reviewing contributor submissions as a maintainer' and 'applying triage to any GitHub repo' create minor overlap with general code-review/PR-review skills.

4 / 5

Total

18

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Gentleman-Programming/engram

Path

skills/backlog-triage/SKILL.md

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.