SKILLEMALL.ai
GitHub ↗ RU Sign in

CD issue-comment

Add structured comments to issues using templates for progress, feedback, or blockers

jmagly/aiwg Agent Skills author: jmagly 1 file body ≈ 4 404 tokens Open the sourcegithub.com↗ analyzed 9 h ago

Add structured comments to issues using templates for progress, feedback, or blockers

As a process D 49/100 · Unfinished process — References files that are not bundled: templates/issue-comments/al-cycle.md

TemplateGitHubInfrastructureData and analyticsAI and agentstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
84/100
safety, quality, tests
Safety 60%
100
Quality 40%
61
Run on models
none yet
Process rating
D
49/100
Unfinished process
References files that are not bundled: templates/issue-comments/al-cycle.md
Tools and files w 18
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

The same skill appears in 2 more places: aiwg, aiwg

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning missing-ref reference to a missing file: templates/issue-comments/al-cycle.md
  • note frontmatter-key unknown frontmatter key "namespace"
  • note frontmatter-key unknown frontmatter key "commandHint"
  • note edit-residue the text marks something as outdated (lines 11): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 49/100

Will not run. References files that are not bundled: templates/issue-comments/al-cycle.md
  • 0Tools and files. 1 referenced file(s) missing: templates/issue-comments/al-cycle.md
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 2 mutating operations with no state check
  • 40Result and completion. Does not say what the result is
  • 50Failures and branches. 0 branches, has a failure section
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 70Execution cost. Instruction body is 4404 tokens
  • 100Steps. 65 steps
  • 100Consistency. Name and required fields are in place
  • low 10 top-level sections: this looks like several domains in one skill

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Description length 85: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 39 headings
  • +3Step-by-step instructions: 65 items
  • +4Has examples (38 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 61.