Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Manage Vikunja projects and tasks (overdue/due/today), mark done, and get quick summaries via the Vikunja API.
Manage Vikunja projects and tasks (overdue/due/today), mark done, and get quick summaries via the Vikunja API.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Use Vikunja as the source of truth for tasks and completions, and interact with it from Clawdbot.
You can provide credentials either via environment variables or via Clawdbotβs skills config.
Set these environment variables in the same environment where the gateway runs: export VIKUNJA_URL="https://vikunja.xyz" # Recommended: use a JWT (starts with "eyJ") export VIKUNJA_TOKEN="<jwt>" # Alternative: login with username/password (the helper CLI will request a JWT) export VIKUNJA_USERNAME="<username>" export VIKUNJA_PASSWORD="<password>"
Edit ~/.clawdbot/clawdbot.json: { skills: { entries: { "vikunja-fast": { enabled: true, env: { VIKUNJA_URL: "https://vikunja.xyz", VIKUNJA_TOKEN: "<jwt>" } } } } } Notes: VIKUNJA_URL can be the base URL; the helper normalizes to /api/v1. Vikunja auth expects a JWT bearer token for most API calls (Authorization: Bearer <jwt>). If you only have a non-JWT token (often starts with tk_...), use /login to obtain a JWT.
curl -fsS -X POST "$VIKUNJA_URL/login" \ -H "Content-Type: application/json" \ -d '{"username":"YOUR_USERNAME","password":"YOUR_PASSWORD","long_token":true}' | jq
curl -fsS "$VIKUNJA_URL/user" \ -H "Authorization: Bearer $VIKUNJA_TOKEN" | jq
curl -fsS "$VIKUNJA_URL/projects" \ -H "Authorization: Bearer $VIKUNJA_TOKEN" | jq '.[] | {id, title}'
This skill ships with a tiny helper CLI: {baseDir}/vikunja.sh Examples: # Overdue across all projects {baseDir}/vikunja.sh overdue # Due today {baseDir}/vikunja.sh due-today # Arbitrary filter (Vikunja filter syntax) {baseDir}/vikunja.sh list --filter 'done = false && due_date < now' # Show / complete a task {baseDir}/vikunja.sh show 123 {baseDir}/vikunja.sh done 123 Notes: Output formatting: Each task should be formated as: <EMOJI> <DUE_DATE> - #<ID> <TASK> Emoji comes from the project title when it starts with one; otherwise uses π¨ Due dates are rendered as Mon/D (time + year removed) This skill uses GET /tasks/all to fetch tasks across all projects
TASK_ID=123 curl -fsS -X POST "$VIKUNJA_URL/tasks/$TASK_ID" \ -H "Authorization: Bearer $VIKUNJA_TOKEN" \ -H "Content-Type: application/json" \ -d '{"done": true}' | jq
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.