SKILLEMALL.ai
GitHub ↗ RU Sign in

CB deploy

GitHub Actions deployment: workflows, releases, GHCR, CI/CD with safety gates. Triggers: deploy, release, workflow.

kochetkov-ma/claude-brewcode Claude Code author: kochetkov-ma 17 files · 12 scripts body ≈ 6 131 tokens Open the sourcegithub.com↗ analyzed 2 d ago

GitHub Actions deployment: workflows, releases, GHCR, CI/CD with safety gates.

As a process B 74/100 · Nearly there — weak spots: when it triggers, running it twice

ProcedureGitHubDockerInfrastructureAI 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%
93
Quality 40%
70
Run on models
none yet
Process rating
B
74/100
Nearly there
When it triggers w 12
20
Running it twice w 4
30
Failures and branches w 10
50
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.
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 · 3

✓ No critical or high findings

Medium and low: 3
  • medium Broad scope meta-broad-allowed-tools SKILL.md:1
    Broad tool permissions pre-approved: Bash
    allowed-tools: Read Write Edit Bash Agent AskUserQuestion Glob Grep
  • low Exfiltration read-dotenv references/workflow-templates.md:343
    Reads a .env file
    if [ -f .env ]; then HAD_ENV=true; cp .env .env.bak; fi
  • low Exfiltration read-dotenv references/workflow-templates.md:347
    Reads a .env file
    cp .env.bak .env

Files scanned: 10. 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 ≈ 6131 tokens (recommended < 5000); move details to references/

Process rating: all ten parameters 74/100

  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 53 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 70Execution cost. Instruction body is 6131 tokens
  • 75Steps. 3 steps
  • 100Tools and files. Tools declared in frontmatter
  • 100Result and completion. Output format and completion criterion are stated
  • 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 11 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (4 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)
  • +3Description length 115: 120–800 characters recommended
  • +2Single-language instructions
  • +4Structure: 57 headings
  • +3Step-by-step instructions: 3 items
  • +3Output format is stated explicitly
  • +4Has examples (40 code blocks)
  • +4Reference files are cited in the instructions (3 of 3)
  • +3All 4 scripts are documented
  • +1License stated

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