CB palest-ink
Track and recall your daily activities including git commits, web browsing, shell commands, and VS Code edits. Use this skill whenever the user asks about their recent activity, wants a daily report or summary, asks "what did I do today/yesterday/this week", wants to find a specific commit or webpage they visited, asks about browsing history, needs to recall any past work activity, or queries about specific content they viewed online. Also trigger when the user mentions palest-ink, activity tracking, daily log, work journal, daily report, or activity summary. Trigger for questions like "which website had info about X", "when did I commit the code for Y", "show my git activity".
As a process B 71/100 · Nearly there — weak spots: 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.
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 · 9
-
high Dangerous commands
cmd-persistencecollectors/install.sh:162Persistence mechanism (cron / launchd / scheduled task / autorun registry)launchctl load "$PLIST_PATH"
Medium and low: 8
-
medium Dangerous commands
cmd-persistencecollectors/install.sh:125Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)PLIST_PATH="$HOME/Library/LaunchAgents/${PLIST_LABEL}.plist"code literal -
medium Dangerous commands
cmd-persistencecollectors/install.sh:130Persistence mechanism (cron / launchd / scheduled task / autorun registry) (detector / deny-list definition)crontab -l 2>/dev/null | grep -v "palest-ink" | crontab -
detector -
medium Dangerous commands
cmd-persistencecollectors/uninstall.sh:17Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)PLIST_PATH="$HOME/Library/LaunchAgents/${PLIST_LABEL}.plist"code literal -
medium Dangerous commands
cmd-persistencecollectors/uninstall.sh:32Persistence mechanism (cron / launchd / scheduled task / autorun registry) (detector / deny-list definition)crontab -l 2>/dev/null | grep -v "palest-ink" | crontab -
detector -
low Dangerous commands
cmd-cron-mentioncollectors/install.sh:128Mentions editing / listing crontabif crontab -l 2>/dev/null | grep -q "palest-ink"; then
-
low Dangerous commands
cmd-cron-mentioncollectors/install.sh:130Mentions editing / listing crontabcrontab -l 2>/dev/null | grep -v "palest-ink" | crontab -
-
low Dangerous commands
cmd-cron-mentioncollectors/uninstall.sh:31Mentions editing / listing crontabif crontab -l 2>/dev/null | grep -q "palest-ink"; then
-
low Dangerous commands
cmd-cron-mentioncollectors/uninstall.sh:32Mentions editing / listing crontabcrontab -l 2>/dev/null | grep -v "palest-ink" | crontab -
Files scanned: 20. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "tools"
Process rating: all ten parameters 71/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 28 steps
- 100Failures and branches. 5 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1284 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -41 reference files, but SKILL.md never points to them: the model will not open them
- +1No license
- +2Single-language instructions
- +5Description quotes 4 example trigger phrases
- +3Description length 686: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 28 items
- +4Has examples (7 code blocks)
- +3All 3 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.