SKILLEMALL.ai

BD debate-review

Two-model debate review of a GitHub PR, GitLab MR, Azure DevOps PR, or local working tree, posted as inline comments or printed. Use for any PR/MR review request, or a local review before a PR exists.

sickn33/agentic-awesome-skills Agent Skills author: sickn33 MIT 6 files body ≈ 1 241 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Two-model debate review of a GitHub PR, GitLab MR, Azure DevOps PR, or local working tree, posted as inline comments or printed.

As a process D 45/100 · Unfinished process — References files that are not bundled: scripts/review-pr.mjs

AnalyzerAzureGitHubGitLabQuality controltype and topics are labelled automatically from the skill text
JSON
Technical rating
B
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
80
Run on models
none yet
Process rating
D
45/100
Unfinished process
References files that are not bundled: scripts/review-pr.mjs
Tools and files w 18
0
Result and completion w 14
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

The same skill appears in 2 more places: agentic-awesome-skills, agentic-awesome-skills

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

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: scripts/review-pr.mjs
  • note frontmatter-key unknown frontmatter key "risk"
  • note frontmatter-key unknown frontmatter key "source"
  • note frontmatter-key unknown frontmatter key "source_repo"
  • note frontmatter-key unknown frontmatter key "source_type"
  • note frontmatter-key unknown frontmatter key "date_added"
  • note frontmatter-key unknown frontmatter key "license_source"
  • note edit-residue the text marks something as outdated (lines 25): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 45/100

Will not run. References files that are not bundled: scripts/review-pr.mjs
  • 0Tools and files. 1 referenced file(s) missing: scripts/review-pr.mjs
  • 0Result and completion. Does not say what the result is
  • 0Progress reporting. Says nothing while it works
  • 30Inputs and preconditions. Does not say what the process needs to start
  • 30Running it twice. 1 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 55Failures and branches. 1 branches
  • 100Steps. 11 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1241 tokens
  • low The response is described with custom markup (6 tags): a typed call is more reliable

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
  • +2Single-language instructions
  • +3Description length 200: enough signal without eating the budget
  • +4Structure: 6 headings
  • +3Step-by-step instructions: 11 items
  • +4Has examples (1 code blocks)
  • +4Reference files are cited in the instructions (2 of 2)
  • +1License stated

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