agentleFS
smk-labssmk-labs/claude-config/skills/vikunja-vja/SKILL.md

vikunja-vja

Skill1 starsChanged 4 months agoMITView on GitHub

Manage Vikunja tasks, projects, and labels via the vja CLI. Use whenever the user mentions tasks, todos, Vikunja, due dates, priorities, or wants to create, list, edit, complete, or delete anything in their task manager.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Always pass --json for machine-readable output

    line 11

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Vikunja Tasks (vja CLI)

Interact with a Vikunja instance using the vja command-line tool.

Two rules that always apply:

  • Always pass --json for machine-readable output
  • Task titles are positional arguments — not --title

Tasks

Create

vja add "Task title"
vja add "Task title" -n "Description" -d "tomorrow" -p 3 -l urgent -A alice
vja add "Task title" -d "next monday at 9:00" -r "1h before due_date" -o "My Project"
FlagMeaning
-n / --noteDescription/body
-d / --dueDue date (natural language or ISO)
--start / --endStart/end dates
-p / --prioPriority: 1=low, 2=medium, 3=high, 4=urgent
-l / --labelLabel (repeat for multiple: -l bug -l backend)
-A / --assigneeUsername to assign
-r / --reminderReminder time ("in 3 days at 18:00", "1h before due_date")
-o / --projectProject name or ID
-f / --starMark as favorite
--force-createCreate the label if it doesn't exist

List & Filter

# Basic list
vja ls --json | jq '.tasks[] | {id, title, due_date, priority}'

# Common filters
vja ls --filter "done eq false" --json | jq '.tasks[] | {id, title}'
vja ls --filter "priority ge 3" --json | jq '.tasks[] | {id, title, priority}'
vja ls --filter "due_date before today" --json | jq '.tasks[] | {id, title, due_date}'
vja ls -l urgent --json | jq '.tasks[] | {id, title}'
vja ls -o "My Project" --json | jq '.tasks[] | {id, title}'
vja ls -u 3 --json | jq '.tasks[] | {id, title, urgency}'  # urgency score >= 3
vja ls --all --json | jq '.tasks[] | {id, title, done}'    # include completed
vja ls --sort "-priority,due_date" --json | jq '.tasks[] | {id, title}'

Filter operators: eq, ne, gt, lt, ge, le, before, after, contains Multiple --filter flags are ANDed together.

Show

vja show <task_id> --json | jq '{id, title, description, due_date, priority, assignees, labels}'

Edit

vja edit <task_id> -i "New title"
vja edit <task_id> -n "Updated description"
vja edit <task_id> -a "Appended note"         # append to existing description
vja edit <task_id> -d "next friday" -p 4
vja edit <task_id> -l bug -l backend          # replace labels
vja edit <task_id> -A alice                   # toggle assignee (adds if absent, removes if present)
vja edit <task_id> -c true                    # mark completed
vja edit <task_id> -f                         # star; use --no-star to unstar
vja edit <task_id> -o "Other Project"         # move to a different project

Other task commands

vja toggle <task_id>               # toggle done/undone
vja delete <task_id> -q            # delete quietly
vja defer <task_id> 2d             # push due date forward (also shifts reminders)
vja defer <task_id> 1h30m
vja clone <task_id> "New title"    # duplicate a task
vja open <task_id>                 # open in browser

Projects

vja project ls --json | jq '.[] | {id, title, parent_project_id}'
vja project show <project_id> --json | jq .
vja project add "Project name"
vja project add "Sub-project" -o "Parent Project"

Labels

vja label ls --json | jq '.[] | {id, title}'
vja label add "new-label"

User

vja user show --json | jq '{id, username, email}'

Workflow Examples

Daily review

# Overdue open tasks
vja ls --filter "due_date before today" --filter "done eq false" --json \
  | jq '.tasks[] | {id, title, due_date}'

# High-priority open tasks, sorted by urgency
vja ls --filter "priority ge 3" --filter "done eq false" --sort "-urgency" --json \
  | jq '.tasks[] | {id, title, priority, urgency, due_date}'

Create with full context in one shot

vja add "Review PR #42" -p 3 -d "today" -A alice -l review --force-create

Bulk-defer all overdue tasks by one day

vja ls --filter "due_date before today" --filter "done eq false" --json \
  | jq '.tasks[].id' \
  | xargs -I{} vja defer {} 1d -q

Mark complete and confirm

vja toggle <task_id> -v --json | jq '{id, title, done}'

Notes

  • Dates accept natural language via parsedatetime: "tomorrow", "next monday", "in 3 days at 9:00", "2025-12-31"
  • --json returns Vikunja API format; --jsonvja returns vja's internal format
  • Config lives at ~/.config/vja/config.rc (legacy: ~/.vjacli/vja.rc)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.