BC patrick
Access Patrick's expertise library for executive decision infrastructure. List, fetch, and manage structured expertise with context variables. Use for executive briefings, decision framing, and strategic analysis.
Access Patrick's expertise library for executive decision infrastructure.
As a process C 60/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, progress reporting
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.
The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
How to improve
- 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.
- 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
-
high Dangerous commands
cmd-pipe-to-shellSKILL.md:27Downloads and executes remote code from an unrecognised host (pipe to shell)curl -fsSL https://portal.patrickbot.io/downloads/latest/install.sh | bash
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 60/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (web, git) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 50 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3249 tokens
- 100Running it twice. Mutating operations check current state
- 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
- high The skill tells the model to perform an irreversible action with no human approval
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)
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +3Description length 213: enough signal without eating the budget
- +4Structure: 37 headings
- +3Step-by-step instructions: 50 items
- +3Output format is stated explicitly
- +4Has examples (34 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.