CD pilot-cron
Scheduled recurring task submission. Use this skill when: 1. You need periodic task execution on a fixed schedule 2. You want automated recurring tasks without manual intervention 3. You need time-based triggers for network operations Do NOT use this skill when: - Tasks should trigger on events, not time (use pilot-workflow) - You only need to run a task once - The schedule is irregular and can't be expressed as a cron pattern
As a process D 48/100 · Unfinished process — weak spots: steps, result and completion, inputs and preconditions
What is at stake
The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.
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
- Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
- 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
-
high Dangerous commands
cmd-persistenceSKILL.md:44Persistence mechanism (cron / launchd / scheduled task / autorun registry)crontab -l | { cat; echo "0 * * * * /path/to/submit-task.sh"; } | crontab - # Every hour -
high Dangerous commands
cmd-persistenceSKILL.md:45Persistence mechanism (cron / launchd / scheduled task / autorun registry)crontab -l | { cat; echo "0 2 * * * /path/to/daily-backup.sh"; } | crontab - # Daily at 2 AM
Medium and low: 5
-
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bashallowed-tools: Bash
-
low Dangerous commands
cmd-cron-mentionSKILL.md:44Mentions editing / listing crontabcrontab -l | { cat; echo "0 * * * * /path/to/submit-task.sh"; } | crontab - # Every hour -
low Dangerous commands
cmd-cron-mentionSKILL.md:45Mentions editing / listing crontabcrontab -l | { cat; echo "0 2 * * * /path/to/daily-backup.sh"; } | crontab - # Daily at 2 AM -
low Dangerous commands
cmd-cron-mentionSKILL.md:70Mentions editing / listing crontabcrontab -l
-
low Dangerous commands
cmd-cron-mentionSKILL.md:92Mentions editing / listing crontabcrontab -l 2>/dev/null | grep -v 'pilot-cron' > /tmp/crontab.tmp || true
Files scanned: 2. 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 48/100
- 0Steps. Prose only: no discrete steps
- 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
- 0Progress reporting. Says nothing while it works
- 100Tools and files. Tools declared in frontmatter
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 479 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
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 430: enough signal without eating the budget
- +4Structure: 5 headings
- +4Has examples (6 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 86.