DC data-scientist
Processes and analyzes data with resident-kernel engines (DuckDB, Polars) and one-shot tools. Use for CSV/parquet/JSON analysis, group-by/join/aggregation, time series, distributions, cleaning, or plotting a dataset.
Processes and analyzes data with resident-kernel engines (DuckDB, Polars) and one-shot tools.
As a process C 60/100 · Has gaps — weak spots: inputs and preconditions, running it twice, progress reporting
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 · 10
✓ No critical or high findings
Medium and low: 10
-
medium Dangerous commands
cmd-pipe-to-shell-known-hostreferences/uv-setup.md:19Pipe-to-shell installer from a well-known host (still executes remote code)curl -LsSf https://astral.sh/uv/install.sh | sh # official installer → ~/.local/bin/uv
-
medium Dangerous commands
cmd-pipe-to-shell-known-hostreferences/uv-setup.md:27Pipe-to-shell installer from a well-known host (still executes remote code)curl -LsSf https://astral.sh/uv/install.sh | sh # official installer → ~/.local/bin/uv
-
medium Dangerous commands
cmd-execpolicy-bypassreferences/uv-setup.md:35Runs PowerShell with execution policy bypassedpowershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"
-
medium Dangerous commands
cmd-pipe-to-shell-known-hostreferences/uv-setup.md:45Pipe-to-shell installer from a well-known host (still executes remote code)curl -LsSf https://astral.sh/uv/install.sh | sh
-
medium Dangerous commands
cmd-pipe-to-shell-known-hostreferences/uv-setup.md:54Pipe-to-shell installer from a well-known host (still executes remote code)- run: curl -LsSf https://astral.sh/uv/install.sh | sh
-
medium Dangerous commands
cmd-execpolicy-bypassscripts/setup-uv.ps1:28Runs PowerShell with execution policy bypassedpowershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"
-
medium Dangerous commands
cmd-pipe-to-shell-known-hostscripts/setup-uv.sh:39Pipe-to-shell installer from a well-known host (still executes remote code)curl -LsSf https://astral.sh/uv/install.sh | sh
-
medium Dangerous commands
cmd-pipe-to-shell-known-hostscripts/setup-uv.sh:41Pipe-to-shell installer from a well-known host (still executes remote code)wget -qO- https://astral.sh/uv/install.sh | sh
-
low Dangerous commands
cmd-execpolicy-bypassreferences/uv-setup.md:10Runs PowerShell with execution policy bypassed (documentation table row)| Windows (PowerShell) | `powershell -ExecutionPolicy Bypass -File scripts/setu…ps1` |
table -
low Dangerous commands
cmd-pipe-to-shell-known-hostreferences/uv-setup.md:30Pipe-to-shell installer from a well-known host (still executes remote code) (quoted — discussed, not commanded)The installer detects glibc vs musl and downloads the right static binary. On minimal containers, ensure `curl` (or `wget`) exists; `wget -qO- https://astral.sh/uv/install.sh | sh` is the fallback.
quoted
Files scanned: 11. 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 60/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 13 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1377 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)
- +4No input/output examples
- -32 of 5 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 216: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 13 items
- +3Output format is stated explicitly
- +4Reference files are cited in the instructions (5 of 5)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.