SKILLEMALL.ai

CD setup-status

Reports which brewcode setup skills are installed, stale, partial or missing in this project, compares the version each installed artifact was generated under against the installed plugin, prints the exact command to run for each, and upgrades the stale ones on request, one fresh subagent per setup, re-probed after each. Triggers: setup status, what is installed, upgrade setups, что установлено, обнови сетапы.

kochetkov-ma/claude-brewcode Claude Code author: kochetkov-ma 40 files · 29 scripts body ≈ 11 006 tokens Open the sourcegithub.com↗ analyzed 7 h ago

Reports which brewcode setup skills are installed, stale, partial or missing in this project, compares the version each installed artifact was generated under…

As a process D 39/100 · Unfinished process — References files that are not bundled: assets/semble-first.md.template, references/memory-guide.md, references/agent-audit.md

GeneratorData and analyticsAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
C
78/100
safety, quality, tests
Safety 60%
95
Quality 40%
52
Run on models
none yet
Process rating
D
39/100
Unfinished process
References files that are not bundled: assets/semble-first.md.template, references/memory-guide.md, references/agent-audit.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

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Broad scope medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

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 SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
  3. 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 · 1

✓ No critical or high findings

Medium and low: 1
  • medium Broad scope meta-broad-allowed-tools SKILL.md:1
    Broad tool permissions pre-approved: Bash
    allowed-tools: Read Bash Glob Grep AskUserQuestion Agent

Files scanned: 15. 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 body-long SKILL.md body ≈ 11006 tokens (recommended < 5000); move details to references/
  • warning missing-ref reference to a missing file: assets/semble-first.md.template
  • warning missing-ref reference to a missing file: references/memory-guide.md
  • warning missing-ref reference to a missing file: references/agent-audit.md
  • warning missing-ref reference to a missing file: references/hard-sync.md
  • warning missing-ref reference to a missing file: references/prompting-guide.md
  • note edit-residue the text marks something as outdated (lines 230, 240, 285, 289, 290, 297): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 39/100

Will not run. References files that are not bundled: assets/semble-first.md.template, references/memory-guide.md, references/agent-audit.md
  • 0Tools and files. 5 referenced file(s) missing: assets/semble-first.md.template, references/memory-guide.md, references/agent-audit.md
  • 0Result and completion. Does not say what the result is
  • 0Failures and branches. Linear process with no failure handling
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 12 mutating operations with no state check
  • 40Execution cost. Instruction body is 11006 tokens: crowds the task out of the window
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 7 steps
  • 100Consistency. Name and required fields are in place
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 17 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (22 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
  • -31 of 4 scripts are never mentioned in SKILL.md
  • +2Single-language instructions
  • +3Description length 413: enough signal without eating the budget
  • +4Structure: 23 headings
  • +3Step-by-step instructions: 7 items
  • +4Has examples (7 code blocks)
  • +4Reference files are cited in the instructions (8 of 9)
  • +1License stated

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