BB pansclaw-code
Use the PansClaw Code CLI (Rust reimplementation of Claude Code) for AI-assisted coding. Triggers when: user wants to run coding tasks via pansclaw code, delegate code writing/refactoring to pansclaw code, or use it interactively. Handles auto-build if binary is missing/outdated. Prerequisites: MINIMAX_API_KEY, ANTHROPIC_API_KEY, or local Ollama models.
As a process B 66/100 · Nearly there — weak spots: result and completion, 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 · 1
✓ No critical or high findings
Medium and low: 1
-
medium Dangerous commands
cmd-pipe-to-shellscripts/build.sh:18Downloads and executes remote code from an unrecognised host (pipe to shell) (string literal in code, not executed)echo " 安装: curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh"
code literal
Files scanned: 10. 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 66/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 16 steps, 1 vague phrases
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 940 tokens
- 100Running it twice. No mutating operations
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
- +3Output format is not stated: the model decides each time
- -4Absolute local paths (C:\Users, /home/…): not portable
- -43 reference files, but SKILL.md never points to them: the model will not open them
- -34 of 4 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 355: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 16 items
- +4Has examples (10 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.