BC gog-safety
Build and deploy safety-profiled gogcli binaries with compile-time command removal. Use when setting up gog for an AI agent with restricted permissions — choosing between L1 (draft only), L2 (collaborate), or L3 (standard write). Covers building from PR
As a process C 56/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
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
- 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 · 7
✓ No critical or high findings
Medium and low: 7
-
medium Dangerous commands
cmd-privilegescripts/deploy-gog-safe.sh:70Privilege escalation / world-writable permissionssudo rm -f /usr/local/bin/gog-backup
-
medium Dangerous commands
cmd-privilegescripts/deploy-gog-safe.sh:72Privilege escalation / world-writable permissionssudo mv /usr/local/bin/gog /usr/local/bin/gog-backup
-
medium Dangerous commands
cmd-privilegescripts/deploy-gog-safe.sh:74Privilege escalation / world-writable permissionssudo mv /tmp/gog-safe-new /usr/local/bin/gog
-
medium Dangerous commands
cmd-privilegescripts/deploy-gog-safe.sh:75Privilege escalation / world-writable permissionssudo chmod +x /usr/local/bin/gog
-
low Dangerous commands
cmd-privilegescripts/build-gog-safe.sh:137Privilege escalation / world-writable permissions (string literal in code, not executed)echo " ssh <host> 'sudo mv /usr/local/bin/gog /usr/local/bin/gog-backup && sudo mv /tmp/gog-safe /usr/local/bin/gog && sudo chmod +x /usr/local/bin/gog'"
code literal -
low Dangerous commands
cmd-privilegescripts/deploy-gog-safe.sh:128Privilege escalation / world-writable permissions (string literal in code, not executed)echo "To rollback: ssh $HOST 'sudo mv /usr/local/bin/gog-backup /usr/local/bin/gog'"
code literal -
low Dangerous commands
cmd-privilegeSKILL.md:56Privilege escalation / world-writable permissions (quoted — discussed, not commanded)ssh <host> 'sudo mv /usr/local/bin/gog-backup /usr/local/bin/gog'
quoted
Files scanned: 8. 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 56/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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 8 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 100Tools and files. No external tools needed
- 100Steps. 9 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 675 tokens
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 253: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 9 items
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.