How do I install the Vikunja skill?

Run npx skillmds add modbender/vikunja in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Vikunja safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts, makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Vikunja?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Vikunja free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Vikunja?

modbender (@modbender) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Vikunja by modbender — Agent Skill

Name: Vikunja
Rating: 4.2 (5 reviews)
Author: modbender

Vikunja

Manage tasks and projects on a self-hosted Vikunja instance. Use when the user wants to create, view, complete, or manage tasks, check what's due or overdue, list projects, or get task notifications. Also use for to-do lists, reminders, and task tracking.

modbender af5d367 2 files · 10.9 KB Updated Sep 9, 2026 12 repo stars

File contents

Vikunja Task Manager

Manage tasks and projects on a self-hosted Vikunja instance via REST API.

Setup

Set these environment variables:

export VIKUNJA_URL="https://your-vikunja-instance.com"
export VIKUNJA_TOKEN="your-api-token"

Get your API token: Vikunja → Settings → API Tokens → Create token.

Commands

List tasks

{baseDir}/scripts/vikunja.sh tasks --count 10
{baseDir}/scripts/vikunja.sh tasks --project "Shopping" --count 5
{baseDir}/scripts/vikunja.sh tasks --search "groceries"
{baseDir}/scripts/vikunja.sh tasks --sort priority --order desc

Overdue tasks

{baseDir}/scripts/vikunja.sh overdue

Tasks due soon (next N hours)

{baseDir}/scripts/vikunja.sh due --hours 24
{baseDir}/scripts/vikunja.sh due --hours 48

Create a task

{baseDir}/scripts/vikunja.sh create-task --project "Tasks" --title "Buy milk" --due "2026-02-01" --priority 3

Priority: 1 (low) to 5 (urgent). Due date format: YYYY-MM-DD.

Complete a task

{baseDir}/scripts/vikunja.sh complete --id 123

Get task details

{baseDir}/scripts/vikunja.sh task --id 123

List projects

{baseDir}/scripts/vikunja.sh projects

Create a project

{baseDir}/scripts/vikunja.sh create-project --title "New Project" --description "Optional description"

Get notifications

{baseDir}/scripts/vikunja.sh notifications

Due Date Monitoring

To get proactive notifications about due/overdue tasks, set up a cron job:

clawdbot cron add \
  --name "Task due check" \
  --cron "0 9,14 * * *" \
  --tz "America/Denver" \
  --session isolated \
  --message "Check Vikunja for overdue and upcoming tasks (next 24 hours). If any are found, notify me with the list." \
  --deliver \
  --channel telegram

Notes

Project names in --project are case-insensitive
Filter expressions follow Vikunja filter syntax (see https://vikunja.io/docs/filters)
All times are handled in America/Denver timezone

---name: vikunjadescription: Manage tasks and projects on a self-hosted Vikunja instance. Use when the user wants to create, view, complete, or manage tasks, check what's due or overdue, list projects, or get task notifications. Also use for to-do lists, reminders, and task tracking.--- # Vikunja Task Manager Manage tasks and projects on a self-hosted Vikunja instance via REST API. ## Setup Set these environment variables: ```bash export VIKUNJA_URL="https://your-vikunja-instance.com" export VIKUNJA_TOKEN="your-api-token" ``` Get your API token: Vikunja → Settings → API Tokens → Create token. ## Commands ### List tasks ```bash {baseDir}/scripts/vikunja.sh tasks --count 10 {baseDir}/scripts/vikunja.sh tasks --project "Shopping" --count 5 {baseDir}/scripts/vikunja.sh tasks --search "groceries" {baseDir}/scripts/vikunja.sh tasks --sort priority --order desc ``` ### Overdue tasks ```bash {baseDir}/scripts/vikunja.sh overdue ``` ### Tasks due soon (next N hours) ```bash {baseDir}/scripts/vikunja.sh due --hours 24 {baseDir}/scripts/vikunja.sh due --hours 48 ``` ### Create a task ```bash {baseDir}/scripts/vikunja.sh create-task --project "Tasks" --title "Buy milk" --due "2026-02-01" --priority 3 ``` Priority: 1 (low) to 5 (urgent). Due date format: YYYY-MM-DD. ### Complete a task ```bash {baseDir}/scripts/vikunja.sh complete --id 123 ``` ### Get task details ```bash {baseDir}/scripts/vikunja.sh task --id 123 ``` ### List projects ```bash {baseDir}/scripts/vikunja.sh projects ``` ### Create a project ```bash {baseDir}/scripts/vikunja.sh create-project --title "New Project" --description "Optional description" ``` ### Get notifications ```bash {baseDir}/scripts/vikunja.sh notifications ``` ## Due Date Monitoring To get proactive notifications about due/overdue tasks, set up a cron job: ```bash clawdbot cron add \ --name "Task due check" \ --cron "0 9,14 * * *" \ --tz "America/Denver" \ --session isolated \ --message "Check Vikunja for overdue and upcoming tasks (next 24 hours). If any are found, notify me with the list." \ --deliver \ --channel telegram ``` ## Notes - Project names in `--project` are case-insensitive - Filter expressions follow Vikunja filter syntax (see https://vikunja.io/docs/filters) - All times are handled in America/Denver timezone

Frequently asked questions