Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Track OpenClaw tasks on NextCloud Deck board. Auto-add tasks to Queue, move through states.
Track OpenClaw tasks on NextCloud Deck board. Auto-add tasks to Queue, move through states.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
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. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Track tasks on a NextCloud Deck board.
This skill assumes a board with 4 stacks (columns): StackDefault IDPurposeQueue1New incoming tasksIn Progress2Currently working onWaiting3Blocked/waiting for userDone Today4Completed tasks
Set the following environment variables (e.g. in your .bashrc or OpenClaw config): export DECK_URL="https://your-nextcloud.com/index.php/apps/deck/api/v1.0" export DECK_USER="your_username" export DECK_PASS="your_app_password" # Use an App Password! export BOARD_ID=1 If your stack IDs differ from the defaults (1, 2, 3, 4), override them: export STACK_QUEUE=10 export STACK_PROGRESS=11 export STACK_WAITING=12 export STACK_DONE=13
deck list
deck add "Task title" "Optional description" Options: --progress: Automatically move the new card to "In Progress" immediately. --stack <id>: Create in a specific stack ID (default: Queue). Example with auto-start: deck add "Urgent Fix" "Fixing production bug" --progress
deck move <card_id> <queue|progress|waiting|done>
deck get <card_id>
deck update <card_id> [--title "New title"] [--description "New desc"]
deck log <card_id> <status> "Message" Statuses: progress, success, error, warning, info.
deck monitor <card_id> [target_id] Spawns a background process that appends a "Still working..." log entry every 60 seconds. Additionally, it sends a chat notification to the specified target_id (defaults to Skander) every 120 seconds. The process terminates automatically when the card is moved out of the "In Progress" stack (to Done or Waiting). Use for tasks expected to take >2 minutes.
deck dump-done Outputs the JSON payload for all cards in "Done Today". Useful for memory synthesis.
deck archive-done Moves all cards in "Done Today" to the archived state. Useful for daily cleanup via cron.
deck delete <card_id>
New task arrives → deck add "Title" "Rich Initial Description" (Use --progress to start immediately). Detailed Descriptions: Start descriptions with Objective, Plan, and Constraints. Log updates → deck log <id> progress "Finished step 1". Closing Task: Use deck update <id> --description "Rich Summary" to include Technical Summary, Operations Performed, and Outcome. Memory Synthesis: Before archiving, use deck dump-done to parse the day's work and reinforce long-term memory. Daily cleanup → deck archive-done.
When updating cards with multi-line markdown descriptions, ALWAYS use the temp file method to prevent shell expansion errors: # 1. Write rich description to temp file cat > /tmp/deck_desc_<id>.txt << 'EOF' [Rich Markdown] EOF # 2. Update deck using the temp file deck update <id> --description "$(cat /tmp/deck_desc_<id>.txt)"
Messaging, meetings, inboxes, CRM, and teammate communication surfaces.
Largest current source with strong distribution and engagement signals.