---

name: vikunja description: This skill should be used when the user asks to "check my tasks", "show my tasks", "what should I work on", "add task", "update task", "complete task", mentions "Vikunja" or "Boosted tasks". By default, focus on the Boosted project (ID 3) unless the user specifies a different project. version: 1.0.0

Vikunja Task Management Skill

This skill enables Claude to interact with your Vikunja task management system at todo.dobosprime.com.

Configuration Location

Credentials: ~/.claude-config/secrets/vikunja.json

{
  "apiUrl": "https://todo.dobosprime.com",
  "apiToken": "your_token_here",
  "defaultListId": null
}

Available Projects

Common project IDs:

• 3: Boosted (main SaaS project)
• 2: Home Lab
• 4: Web Dev
• 1: Home (personal)

Security

CRITICAL: NEVER expose the API token in command output or logs. Always use the helper script.

Helper Script

All Vikunja API operations should use the secure helper script:

Location: ~/.claude-config/plugins/personal/scripts/vikunja-api.sh

This script handles token retrieval internally and keeps it out of command history and output.

Common Operations

IMPORTANT: The script outputs pre-formatted text by default. DO NOT pipe to jq or other parsers. Use the output directly.

1. List Tasks in a Project

Single project:

~/.claude-config/plugins/personal/scripts/vikunja-api.sh list-tasks 3

Output format: ○ [22] finish onboarding (already formatted, ready to display)

All projects (recommended for "check my tasks"):

~/.claude-config/plugins/personal/scripts/vikunja-api.sh list-tasks all

Output format:

=== Boosted (9 open) ===
○ [22] finish onboarding
○ [23] check github

=== Home Lab (5 open) ===
○ [5] backup strat for proxmox

When to use all vs specific project:

• Generic "check my tasks" → Use all (1 command instead of 4+)
• "check my Boosted tasks" → Use 3
• "what do I need to do for home lab" → Use 2

2. Create a New Task

Without due date:

~/.claude-config/plugins/personal/scripts/vikunja-api.sh create-task 3 "Task title here" "Optional description"

With due date:

~/.claude-config/plugins/personal/scripts/vikunja-api.sh create-task 3 "Task title here" "Optional description" "2026-01-20"

Note: Due dates must be in YYYY-MM-DD format. The description parameter is required but can be empty ("") if you want to set a due date without a description.

3. Set or Update Due Date on Existing Task

~/.claude-config/plugins/personal/scripts/vikunja-api.sh set-due-date 90 "2026-01-20"

Note: This updates only the due date field. Date format must be YYYY-MM-DD.

4. Update a Task (Mark as Done)

~/.claude-config/plugins/personal/scripts/vikunja-api.sh update-task 22 true

5. List All Projects

~/.claude-config/plugins/personal/scripts/vikunja-api.sh list-projects

Output format: [3] Boosted (already formatted, ready to display)

6. Label Management

List all labels:

~/.claude-config/plugins/personal/scripts/vikunja-api.sh list-labels

Create a new label:

~/.claude-config/plugins/personal/scripts/vikunja-api.sh create-label "label-name" "Description" "hex_color"

Add label to task:

~/.claude-config/plugins/personal/scripts/vikunja-api.sh add-label <task_id> <label_id>

Remove label from task:

~/.claude-config/plugins/personal/scripts/vikunja-api.sh remove-label <task_id> <label_id>

Show labels on a task:

~/.claude-config/plugins/personal/scripts/vikunja-api.sh task-labels <task_id>

Standard Labels

The following labels are configured for priority and duration tracking:

Priority Labels

• [4] high-priority (red #e63946) - Critical tasks needing immediate attention
• [5] medium-priority (orange #f77f00) - Important but not urgent
• [6] low-priority (blue #457b9d) - Nice to have, do when time permits
• [9] blocking (dark red #d00000) - Tasks blocking other work

Duration Labels

• [7] multi-day (purple #9d4edd) - Tasks requiring multiple days to complete
• [8] quick-win (green #06d6a0) - Tasks that can be completed in under 1 hour

Task Response Format

Tasks are returned as JSON with these key fields:

• id: Unique task identifier
• title: Task title
• description: Detailed description
• done: Boolean completion status
• priority: 0-5 priority level
• project_id: Parent project ID
• due_date: Optional due date
• created: Creation timestamp

Best Practices

1. ALWAYS use the helper script - Never expose the API token in command output
2. Use the full path to the script: ~/.claude-config/plugins/personal/scripts/vikunja-api.sh
3. DO NOT pipe to jq or other parsers - The script already formats output in compact mode
4. For raw JSON - Use --json flag: vikunja-api.sh --json list-tasks 3
5. Provide context when listing tasks (show title, done status, ID)
6. Confirm actions before creating/updating tasks
7. Handle errors gracefully and inform the user if API calls fail

Example Workflows

Show all Boosted tasks

~/.claude-config/plugins/personal/scripts/vikunja-api.sh list-tasks 3

Output: Pre-formatted list like ○ [22] finish onboarding

Add task to Boosted project

~/.claude-config/plugins/personal/scripts/vikunja-api.sh create-task 3 "Finish landing page" "Add hero section and CTA"

Output: Confirmation with task ID

Add task with due date

~/.claude-config/plugins/personal/scripts/vikunja-api.sh create-task 10 "Mail packages" "Take to post office" "2026-01-20"

Output: Task created with due date displayed

Set due date on existing task

~/.claude-config/plugins/personal/scripts/vikunja-api.sh set-due-date 90 "2026-01-20"

Output: Task updated with due date

Mark task as complete

~/.claude-config/plugins/personal/scripts/vikunja-api.sh update-task 22 true

Output: Confirmation of completion

Intelligent Task Filtering

When the user asks "what should I do today", "what's on my todo list", or similar questions, follow this behavior:

1. Show today's due tasks (standard behavior)
2. Alert about upcoming multi-day tasks - If tasks are due in 2-5 days and tagged with multi-day label, show a warning to start them now
3. Highlight high-priority items - Even if not due today, if tagged high-priority, include them in the summary
4. Flag blocking tasks - Tasks with blocking label need immediate attention since they block other work
5. Suggest quick wins - If the user has downtime or asks "what's quick", show tasks tagged quick-win

Example Response Format

TODAY (Jan 21):
- [103] send amy setchels picture to walgreens (Home)

UPCOMING MULTI-DAY TASKS (start soon!):
- [95] Build CSV student import feature (Due: Jan 24) 🏷️ high-priority, multi-day, blocking

HIGH PRIORITY (not due today but important):
- [98] Fix broken /demo link (Due: Jan 22) 🏷️ high-priority, quick-win

When to Use This Skill

• User mentions Vikunja, tasks, or todo.dobosprime.com
• User wants to see their task list
• User asks "what should I do today", "what's next", "what should I work on"
• User wants to add, update, or complete tasks
• User asks about project management or tracking work
• Planning development sprints or tracking progress

Integration with Development Workflow

When working on projects (especially Boosted), proactively suggest:

• Adding completed work as done tasks
• Creating new tasks for identified work
• Checking existing tasks before suggesting new work
• Syncing TodoWrite tool with Vikunja tasks