Vikunja Kanban

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

Before installing or using this skill: - Treat the VIKUNJA_TOKEN as sensitive. The scripts expect it but the registry metadata does not declare it — the token is long-lived and has wide permissions. Create a least-privilege token (narrow permissions, shorter expiry) and do not reuse high-privilege tokens. - Inspect and update the scripts to point VIKUNJA_URL to your own Vikunja instance (the included scripts currently hardcode https://kanban.pigpen.haus). Do not use that remote host unless you explicitly trust and control it. - Remove any hardcoded identifiers (PROJECT_ID, VIEW_ID, BUCKET IDs) or confirm they match your environment. Hardcoded IDs may perform operations in an unintended project. - Avoid storing the token in the repository. Keep secrets/vikunja.env locally in a secure secrets store and ensure it’s gitignored. - The SKILL.md suggests editing the PostgreSQL DB to change permissions — this is an out-of-band, high-risk operation. Prefer using the API or proper admin procedures; do not run SQL provided by third-party skills unless you fully trust the source and understand the DB schema and implications. - If you need stronger assurance, ask the publisher for: (1) an explanation why metadata omits required env vars, (2) a configurable script variant that reads VIKUNJA_URL from env, and (3) confirmation who controls kanban.pigpen.haus. Without those fixes, treat the skill as suspicious and do not supply production credentials.

Type: OpenClaw Skill Name: vikunja-kanban Version: 1.1.0 The skill is classified as suspicious primarily due to a critical prompt injection vulnerability in `SKILL.md`. The documentation provides a 'workaround' that instructs the AI agent to execute direct SQL commands (`UPDATE users_projects SET permission = 2 ...`) for privilege escalation, which is a severe security risk if the agent has database access. Additionally, all shell scripts (`scripts/*.sh`) use `curl -sk`, disabling SSL certificate validation and making API communication vulnerable to Man-in-the-Middle attacks. The `scripts/vikunja-add-task.sh` script also directly inserts user-supplied arguments into a JSON payload without proper escaping, creating a JSON injection vulnerability. The hardcoded API endpoint `https://kanban.pigpen.haus` is noted as an IOC.