CB nex-life-logger
Track computer activity (browser history, active windows, YouTube videos) locally and query it with AI. All activity data stays on your machine. LLM features require explicit user configuration. Ask your agent what you were doing at any time.
As a process B 71/100 · Nearly there — weak spots: inputs and preconditions, progress reporting
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 instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".
If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.
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 · 5
-
high Dangerous commands
cmd-persistencesetup.sh:179Persistence mechanism (cron / launchd / scheduled task / autorun registry)launchctl load "$PLIST"
Medium and low: 4
-
medium Exfiltration
net-redirectable-api-keylib/config.py:49Helper sends the API key to a host configured by an environment variable — the key can be redirected to another serverAPI key + configurable base URL from environment
-
medium Dangerous commands
cmd-persistencenex-life-logger.py:646Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)plist = os.path.expanduser("~/Library/LaunchAgents/com.nexai.life-logger.plist")code literal -
medium Dangerous commands
cmd-persistencenex-life-logger.py:662Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)plist = os.path.expanduser("~/Library/LaunchAgents/com.nexai.life-logger.plist")code literal -
medium Dangerous commands
cmd-shell-rcsetup.sh:109Writes to a shell startup fileecho " Add this to your ~/.bashrc or ~/.zshrc"
Files scanned: 17. 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 71/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 100Steps. 33 steps
- 100Failures and branches. 3 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2237 tokens
- 100Running it twice. Mutating operations check current state
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)
- +2Single-language instructions
- +3Description length 242: enough signal without eating the budget
- +4Structure: 19 headings
- +3Step-by-step instructions: 33 items
- +3Output format is stated explicitly
- +4Has examples (11 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.