BF vikunja
Production-oriented Vikunja task/project management skill with deterministic commands and strong validation.
As a process F 34/100 · Will not run — weak spots: steps, result and completion, when it triggers
AnalyzerInfrastructureOperations and projectstype and topics are labelled automatically from the skill text
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
- 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
-
low Exfiltration
net-credential-usetest-smoke.sh:15Credential used in a network call (verify the destination is the intended service) (test fixture / example file)curl -sS -H "Authorization: Bearer $VIKUNJA_TOKEN" "$VIKUNJA_URL/api/v1/projects" | jq -r --arg t "$title" '.[] | select(.title==$t) | .id' | head -n1
fixture -
low Exfiltration
net-credential-usetest-smoke.sh:23Credential used in a network call (verify the destination is the intended service) (test fixture / example file; quoted — discussed, not commanded)id="$(curl -sS -X PUT "$VIKUNJA_URL/api/v1/projects" -H "Authorization: Bearer $VIKUNJA_TOKEN" -H 'Content-Type: application/json' -d "{\"title\":\"$title\"}" | jq -r '.id')"fixturequoted -
low Exfiltration
net-credential-usevikunja.sh:860Credential used in a network call (verify the destination is the intended service) (quoted — discussed, not commanded)response="$(curl -sS -X PUT "${API_BASE}/tasks/${task_id}/attachments" -H "Authorization: Bearer ${VIKUNJA_TOKEN}" --connect-timeout 10 --max-time 60 -F "$file_arg")"quoted -
low Exfiltration
net-credential-usevikunja.sh:868Credential used in a network call (verify the destination is the intended service) (quoted — discussed, not commanded)code="$(curl -sS -o "$output" -w "%{http_code}" -X GET "${API_BASE}/tasks/${task_id}/attachments/${attachment_id}" -H "Authorization: Bearer ${VIKUNJA_TOKEN}" --connect-timeout 10 --maquoted
Files scanned: 6. 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") - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 34/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
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (vikunja) differs from the folder (vikunja-complete)
- 100Tools and files. No external tools needed
- 100Execution cost. Instruction body is 1055 tokens
- 100Running it twice. No mutating operations
- low 13 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)
- +3Description length 108: 120–800 characters recommended
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +4Structure: 14 headings
- +4Has examples (14 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 63.
External checks
ClawHub: clean
This is a disclosed Vikunja command-line integration with sensitive admin features that should be used carefully, but the artifacts do not show hidden or malicious behavior.
LLM: benign (high) · VirusTotal: · 29 May 2026