SKILLEMALL.ai

BD github-issue-triage

Issue triage and lifecycle management agent for ZeroClaw. Use this skill whenever the user wants to: triage open issues, close stale/duplicate/fixed issues, apply labels, run a backlog sweep, enforce the current issue stale policy, or handle a specific issue. Trigger on: 'triage issues', 'issue triage', 'sweep issues', 'close stale issues', 'handle issue #N', 'backlog sweep', 'label issues', 'stale pass', 'wont-fix pass', 'issue accounting', 'how many issues', 'backlog health', or any request involving issue lifecycle management for the ZeroClaw project.

zeroclaw-labs/zeroclaw Agent Skills author: zeroclaw-labs Apache-2.0 2 files body ≈ 2 105 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Issue triage and lifecycle management agent for ZeroClaw.

As a process D 48/100 · Unfinished process — References files that are not bundled: ../../../docs/book/src/maintainers/labels.md

ProcedureGitHubOperations and projectsAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
93/100
safety, quality, tests
Safety 60%
100
Quality 40%
82
Run on models
none yet
Process rating
D
48/100
Unfinished process
References files that are not bundled: ../../../docs/book/src/maintainers/labels.md
Tools and files w 18
0
Result and completion w 14
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. 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: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../../../docs/book/src/maintainers/labels.md

Process rating: all ten parameters 48/100

Will not run. References files that are not bundled: ../../../docs/book/src/maintainers/labels.md
  • 0Tools and files. 1 referenced file(s) missing: ../../../docs/book/src/maintainers/labels.md
  • 0Result and completion. Does not say what the result is
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 1 mutating operations with no state check
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 85Steps. 18 steps, 1 vague phrases
  • 100When it triggers. States when to use and when not to
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2105 tokens
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

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)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 560: enough signal without eating the budget
  • +4Structure: 10 headings
  • +3Step-by-step instructions: 18 items
  • +4Has examples (2 code blocks)
  • +4Reference files are cited in the instructions (1 of 1)

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