BC timedoctor
Integrates with TimeDoctor API to pull employee time tracking data, worklogs, statistics, and productivity metrics using simple Python scripts
As a process C 60/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, consistency
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
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 4
✓ No critical or high findings
Medium and low: 4
-
medium Dangerous commands
cmd-shell-rcREADME.md:102Writes to a shell startup fileecho 'export TIMEDOCTOR_TOKEN="your-token"' >> ~/.bashrc
-
medium Dangerous commands
cmd-shell-rcREADME.md:103Writes to a shell startup fileecho 'export TIMEDOCTOR_COMPANY_ID="your-company-id"' >> ~/.bashrc
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:73High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)export TIMEDOCTOR_TOKEN="1jxE…Qns"
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:328High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)export TIMEDOCTOR_TOKEN='1jxE…Qns'
quoted
Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 60/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (timedoctor) differs from the folder (timedoctor-skill)
- 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Execution cost. Instruction body is 4510 tokens
- 100Steps. 123 steps
- 100Failures and branches. 2 branches, has a failure section
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- low 15 top-level sections: this looks like several domains in one skill
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)
- +1No license
- +2Single-language instructions
- +3Description length 142: enough signal without eating the budget
- +4Structure: 47 headings
- +3Step-by-step instructions: 123 items
- +3Output format is stated explicitly
- +4Has examples (33 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.