What Are Skills?
Skills are reusable diagnostic playbooks that extend Siclaw’s capabilities. Each skill is a directory containing a description and optional executable scripts.Skill Tiers
team > core
Creating a Skill
1. Write the SKILL.md
2. Add Scripts (Optional)
Security Review Gate
Scripts follow a mandatory review workflow before execution:Static Analysis
Danger patterns are checked automatically:| Severity | Examples | |
|---|---|---|
| Critical | rm -rf, mkfs, dd if=, fork bomb | |
| High | chmod 777, `curl | sh, eval, > /dev/sda` |
| Medium | kill -9, pkill, reboot, shutdown |
AI Review
An LLM reviews the script semantics with a mandatory rule: “Skills MUST be strictly read-only.”Human Approval
A user withskill_reviewer role must approve before the skill can be executed.
Script Execution
When a skill script is approved and executed viarun_skill:
- Interpreter:
bashfor.sh,python3for.py(detected automatically) - Timeout: Default 180s, max 300s
- Arguments: Passed as array to
spawn()— no shell interpolation (injection-safe) - Max output: 10 MB combined stdout + stderr
- Injected environment:
KUBECONFIG,SICLAW_DEBUG_IMAGE,SICLAW_CREDENTIALS_DIR
Skill scripts are exempt from the binary allowlist. This is the only way to run otherwise-blocked binaries (like
sed or awk) — the security review gate is the safety mechanism.