Tencent SkillHub · Developer Tools

Vikunja Kanban

Manage Vikunja kanban boards via API to read, create, move, and complete tasks across predefined buckets with integrated cron sync.

skill openclawclawhub Free

0 Downloads

0 Stars

0 Installs

0 Score

High Signal

Manage Vikunja kanban boards via API to read, create, move, and complete tasks across predefined buckets with integrated cron sync.

⬇ 0 downloads ★ 0 stars Unverified but indexed

Install for OpenClaw

Quick setup

Download the package from Yavira.
Extract the archive and review SKILL.md first.
Import or place the package into your OpenClaw setup.

Requirements

Target platform: OpenClaw
Install method: Manual import
Extraction: Extract archive
Prerequisites: OpenClaw
Primary doc: SKILL.md

Package facts

Download mode: Yavira redirect
Package format: ZIP package
Source platform: Tencent SkillHub
What's included: SKILL.md, scripts/vikunja-add-task.sh, scripts/vikunja-complete-task.sh, scripts/vikunja-move-task.sh, scripts/vikunja-status.sh

Validation

Use the Yavira download entry.
Review SKILL.md after the package is downloaded.
Confirm the extracted package contains the expected setup assets.

Install with your agent

Agent handoff

Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.

Download the package from Yavira.
Extract it into a folder your agent can access.
Paste one of the prompts below and point your agent at the extracted folder.

New install

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.

Upgrade existing

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.

Open Send to Agent page Open JSON manifest Open Markdown brief

Trust & source

Release facts

Source: Tencent SkillHub
Verification: Indexed source record
Version: 1.1.0

Provenance

Publisher: shad0wca7
Source page: View original listing
Canonical URL: Open canonical page

Documentation

ClawHub primary doc Primary doc: SKILL.md 18 sections Open source page

Vikunja Kanban Skill

Manage a Vikunja kanban board via API. Read status, create/move/complete tasks, and integrate with heartbeat and triage crons.

Config

Credentials stored in secrets/vikunja.env: VIKUNJA_URL=https://your-vikunja-instance VIKUNJA_TOKEN=${VIKUNJA_TOKEN} VIKUNJA_PROJECT_ID=1 VIKUNJA_VIEW_ID=4

Authentication

All scripts use a long-lived API token (expires 2030-01-01). No JWT login needed. Permissions: tasks (read_all, update, create, delete), projects (read_all, update, create) JWT login credentials kept in secrets/vikunja.env for reference only

Bucket IDs

IDNamePurpose1🔴 UrgentNeeds immediate attention2⏳ Waiting OnSent/requested, awaiting reply7⚠️ System IssuesInfra/system problems8🚧 Active ProjectsIn progress9📅 UpcomingScheduled/future10📥 InboxNew items, untriaged3✅ DoneCompleted

Scripts

All scripts are in the skill's scripts/ directory. Run from the skill root.

Read the board

bash scripts/vikunja-status.sh # All buckets bash scripts/vikunja-status.sh "Urgent" # Filter by bucket name

Add a task

bash scripts/vikunja-add-task.sh "Title" "Description" BUCKET_ID [PRIORITY] # Priority: 0=unset, 1=low, 2=medium, 3=high, 4=urgent # Example: bash scripts/vikunja-add-task.sh "Fix DNS" "Check records" 1 4

Move a task between buckets

bash scripts/vikunja-move-task.sh TASK_ID BUCKET_ID # Example: bash scripts/vikunja-move-task.sh 15 3 # Move to Done

Complete a task

bash scripts/vikunja-complete-task.sh TASK_ID

Heartbeat Integration

The heartbeat cron reads from Vikunja: bash scripts/vikunja-status.sh Check 🔴 Urgent for items aging >1h If Vikunja unreachable, fall back to scripts/nc-status-board.sh read

Email Triage Integration

Email triage adds Action Required items to the Inbox bucket: bash scripts/vikunja-add-task.sh "Email subject" "Brief description" 10 3

API Reference

Base URL: https://your-vikunja-instance/api/v1 Auth: POST /login with username/password → JWT token (short-lived) Tasks: PUT /projects/{id}/tasks (create), POST /tasks/{id} (update) Buckets: POST /projects/{id}/views/{view}/buckets/{bucket}/tasks (move task) Views: GET /projects/{id}/views/{view}/tasks (list tasks by bucket) Projects: POST /projects/{id} (update title/settings), GET /projects (list all) Sharing: PUT /projects/{id}/users {"username":"...", "right":N} (add user) Users: GET /users?s=query (search), POST /user/password (self-service password change)

Sharing permissions ignored on creation

PUT /projects/{id}/users ignores the right field — always creates with permission=0 (read-only). Workaround: Set permission directly in PostgreSQL: UPDATE users_projects SET permission = 2 WHERE user_id = X AND project_id = Y; Permission values: 0=read-only, 1=read+write, 2=admin

Default Inbox project cannot be deleted

Every new user gets an auto-created "Inbox" project. DELETE /projects/{id} returns error 3012. Workaround: Rename it: POST /projects/{id} with {"title":"New Name"}

Password change is self-service only

No admin endpoint to change another user's password. Must login as the target user: POST /api/v1/user/password with {"old_password":"...", "new_password":"..."}

API token creation needs both tasks AND projects permissions

Tokens with only tasks permissions cannot read kanban views (returns 401). Must include: "permissions":{"tasks":["read_all","update","create","delete"],"projects":["read_all","update","create"]}

Token creation endpoint

PUT /api/v1/tokens to create, GET /api/v1/tokens to list, DELETE /api/v1/tokens/{id} to remove. Required fields: title, expires_at (ISO-8601), permissions (object with permission groups).

Notes

Long-lived API token used (expires 2030) — no JWT login overhead Vikunja uses PUT for creation, POST for updates (unusual) Bucket IDs are specific to the Kanban view (view_id=4) Project name: "Kit Operations" (renamed from default "Inbox") Project shared: Kit (id:1, admin/owner), Alex (id:2, admin via DB fix) Token has tasks + projects permissions; covers all kanban operations Each user gets a default project that can't be deleted — rename to avoid confusion

Category context

Code helpers, APIs, CLIs, browser automation, testing, and developer operations.

Source: Tencent SkillHub

Largest current source with strong distribution and engagement signals.

Package contents

Included in package

4 Scripts1 Docs

SKILL.md Primary doc
scripts/vikunja-add-task.sh Scripts
scripts/vikunja-complete-task.sh Scripts
scripts/vikunja-move-task.sh Scripts
scripts/vikunja-status.sh Scripts