NextCloud Deck Tracker

Track OpenClaw tasks on NextCloud Deck board. Auto-add tasks to Queue, move through states.

This skill is internally inconsistent: its instructions require a 'deck' CLI and Nextcloud credentials (DECK_URL, DECK_USER, DECK_PASS) but the registry entry lists none. Before installing or providing secrets: 1) Do NOT export your real DECK_PASS until you verify the code. Use a limited-scope Nextcloud App Password. 2) Inspect the referenced GitHub repo (https://github.com/SkanderHelali/openclaw-deck-tracker) — review the 'deck' CLI code and monitor/notification implementation to confirm where notifications are sent. 3) Change the default notification target (the SKILL.md defaults to 'Skander') or disable notifications if you can't verify destination. 4) If you want to test, run the tool in an isolated environment (temporary VM or container) and use least-privilege credentials. 5) Ask the publisher to update registry metadata to declare required env vars and any install steps, and to explain the notification endpoint and monitor process in detail. If you can't verify these, treat the skill as high-risk and avoid giving it credentials.

Type: OpenClaw Skill Name: openclaw-deck-tracker Version: 0.1.1 The skill provides legitimate task management features for NextCloud Deck, requiring network access and the ability to spawn background processes (`deck monitor`). However, the 'AI Protocol: Complex Descriptions' in both `SKILL.md` and `README.md` instructs the AI agent to use a temporary file method for updating card descriptions. This involves writing arbitrary content to `/tmp/deck_desc_<id>.txt` and then using `$(cat /tmp/deck_desc_<id>.txt)` within a command. This pattern creates a significant prompt injection vulnerability, allowing an attacker to instruct the AI agent to write and execute arbitrary shell commands, leading to potential Remote Code Execution (RCE).