SKILLEMALL.ai
GitHub ↗ RU Sign in

CC devops-excellence

DevOps and CI/CD expert. Use when setting up pipelines, containerizing applications, deploying to Kubernetes, or implementing release strategies. Covers GitHub Actions, Docker, K8s, Terraform, and GitOps.

Not recommendedcritical or high security findings
majiayu000/spellbook Agent Skills author: majiayu000 MIT 7 files body ≈ 2 351 tokens Open the sourcegithub.com↗ analyzed 3 d ago

DevOps and CI/CD expert.

As a process C 59/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice

ProcedureGitHubDockerKubernetesGitLabInfrastructuretype 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
81/100
safety, quality, tests
Safety 60%
76
Quality 40%
88
Run on models
none yet
Process rating
C
59/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

What is at stake

The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.

Exfiltration
If you install

The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".

For the author

If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.

How to improve

  1. Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
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

  • high Exfiltration exfil-webhook-url reference/release-strategies.md:665
    Webhook / callback URL commonly used for exfiltration (verify the destination)
    url: https://hooks.slack.com/services/YOUR/WEBHOOK
Medium and low: 2
  • medium Exfiltration exfil-read-secret-files templates/Dockerfile:144
    Reads credential / secret files (security demo / example)
    #   RUN --mount=type=secret,id=npmrc,target=/root/.npmrc npm ci
    demo
  • low Exfiltration read-dotenv SKILL.md:75
    Reads a .env file (Dockerfile instruction (build context, not runtime exfiltration))
    COPY .env /app/.env
    Dockerfile

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

Against the Agent Skills spec

✓ No remarks against the Agent Skills spec

Process rating: all ten parameters 59/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 7 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 100Tools and files. No external tools needed
  • 100Steps. 21 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2351 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 204: enough signal without eating the budget
  • +4Structure: 25 headings
  • +3Step-by-step instructions: 21 items
  • +4Has examples (15 code blocks)
  • +4Reference files are cited in the instructions (1 of 4)

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