DD google-tasks
Read and manage Google Tasks task lists and individual tasks via the Tasks v1 REST API. Use when the user mentions Google Tasks, todo / pending / overdue tasks, weekly task recap, grouping todos by list, adding or completing a task, or moving / deleting tasks.
Read and manage Google Tasks task lists and individual tasks via the Tasks v1 REST API.
As a process D 46/100 · Unfinished process — weak spots: steps, result and completion, inputs and preconditions
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 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
- 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
✓ No critical or high findings
Medium and low: 5
-
medium Exfiltration
net-credential-useSKILL.md:46Credential used in a network call (verify the destination is the intended service)curl -sS -H "Authorization: Bearer $GOOGLE_TASKS_TOKEN" \
-
medium Exfiltration
net-credential-useSKILL.md:58Credential used in a network call (verify the destination is the intended service)curl -sS -H "Authorization: Bearer $GOOGLE_TASKS_TOKEN" \
-
medium Exfiltration
net-credential-useSKILL.md:61Credential used in a network call (verify the destination is the intended service)curl -sS -H "Authorization: Bearer $GOOGLE_TASKS_TOKEN" \
-
medium Exfiltration
net-credential-useSKILL.md:76Credential used in a network call (verify the destination is the intended service)curl -sS -H "Authorization: Bearer $GOOGLE_TASKS_TOKEN" \
-
medium Exfiltration
net-credential-useSKILL.md:96Credential used in a network call (verify the destination is the intended service)curl -sS -H "Authorization: Bearer $GOOGLE_TASKS_TOKEN" \
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "connections" - note
frontmatter-keyunknown frontmatter key "allowed_tools"
Process rating: all ten parameters 46/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
- 30Running it twice. 8 mutating operations with no state check
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Failures and branches. 3 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2677 tokens
- 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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- -5TODO / placeholder text left in the skill
- +2Single-language instructions
- +3Description length 260: enough signal without eating the budget
- +4Structure: 18 headings
- +4Has examples (15 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.