BD magento-admin
Complete Magento 2 store administration via SSH key auth, REST API, GraphQL, and direct DB access. For server owners on their own infrastructure. SSH key auth and passwordless sudo required.
As a process D 45/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 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
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 8603 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "requires" - note
frontmatter-keyunknown frontmatter key "security" - note
frontmatter-keyunknown frontmatter key "prompt_injection_mitigation"
Process rating: all ten parameters 45/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 11 mutating operations with no state check
- 40Execution cost. Instruction body is 8603 tokens: crowds the task out of the window
- 55Failures and branches. 1 branches
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 85Steps. 21 steps, 2 vague phrases
- 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 32 top-level sections: this looks like several domains in one skill
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
- -2localhost URLs: will not work for another user
- -212 emoji in the instructions: noise for the model
- +2Single-language instructions
- +3Description length 190: enough signal without eating the budget
- +4Structure: 33 headings
- +3Step-by-step instructions: 21 items
- +4Has examples (80 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 56.
External checks
ClawHub: suspicious
This is a real Magento administration skill, but it gives an agent broad production-store power with incomplete guardrails around command inputs and destructive actions.
LLM: suspicious (high) · VirusTotal: · 29 May 2026