BC kaggle
Unified Kaggle skill. Use when the user mentions kaggle, kaggle.com, Kaggle competitions, datasets, models, notebooks, GPUs, TPUs, badges, or anything Kaggle-related. Handles account setup, competition reports, dataset/model downloads, notebook execution, competition submissions, badge collection, and general Kaggle questions.
Unified Kaggle skill.
As a process C 56/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
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.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
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.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
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 · 8
✓ No critical or high findings
Medium and low: 8
-
medium Dangerous commands
cmd-persistencemodules/badge-collector/scripts/phase_5_streaks.py:67Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)print(f" 1. Create a plist at ~/Library/LaunchAgents/com.kaggle.streak.plist")
code literal -
medium Dangerous commands
cmd-persistencemodules/badge-collector/scripts/phase_5_streaks.py:70Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)print(f" 2. Load it: launchctl load ~/Library/LaunchAgents/com.kaggle.streak.plist")
code literal -
medium Dangerous commands
cmd-persistencemodules/badge-collector/scripts/phase_5_streaks.py:71Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)print(f" 3. To stop: launchctl unload ~/Library/LaunchAgents/com.kaggle.streak.plist")
code literal -
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bashallowed-tools: Bash Read WebFetch
-
low Dangerous commands
cmd-cron-mentionmodules/badge-collector/scripts/phase_5_streaks.py:74Mentions editing / listing crontab (string literal in code, not executed)print(f" 1. Open crontab: crontab -e")
code literal -
low Dangerous commands
cmd-cron-mentionmodules/badge-collector/scripts/phase_5_streaks.py:77Mentions editing / listing crontab (string literal in code, not executed)print(f" 3. Save and exit. Verify with: crontab -l")
code literal -
low Exfiltration
read-dotenvmodules/kllm/scripts/setup_env.sh:20Reads a .env filesource .env
-
low Exfiltration
read-dotenvmodules/registration/scripts/setup_env.sh:17Reads a .env filesource .env
Files scanned: 44. 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 56/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 30Running it twice. 15 mutating operations with no state check
- 70When it triggers. States when to use, but not when not to
- 85Steps. 63 steps, 3 vague phrases
- 100Tools and files. Tools declared in frontmatter
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2630 tokens
- 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
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
- +2Single-language instructions
- +3Description length 328: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 63 items
- +4Has examples (5 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.