Source Code
Collaboration Helper
Overview
scripts/collaboration_helper.py is a lightweight JSON-backed tracker for community action items:
listshows every open or in-progress task with owner, priority, and creation timestamp.addcreates a new entry using--owner,--priority, and optional--notefields to capture context.completemarks a task as finished and records who closed it.
The data lives in data/tasks.json, so the collaboration state survives across skill runs and reboots.
CLI usage
python3 skills/collaboration-helper/scripts/collaboration_helper.py listprints the current queue grouped by status (open/in progress/done).add "Review policy" --owner legal --priority high --note "Need quotes for Moltbook post"registers a new task with metadata.complete 1 --owner opsmarks taskid=1as done and stores the time/owner.--workspace /path/to/workspacelets you point at another repo'sdata/tasks.jsonwhen you want to sync or inspect a partner workspace.
Task data structure
Each entry in skills/collaboration-helper/data/tasks.json looks like:
{
"id": <number>,
"title": "Task title",
"owner": "owner-name",
"priority": "low|medium|high",
"status": "open|in-progress|done",
"created_at": "2026-02-03T12:00:00Z",
"note": "optional context"
}
The CLI automatically increments id, sets timestamps, and toggles status when you complete an item.
Example workflow
python3 skills/collaboration-helper/scripts/collaboration_helper.py add "Document governance" --owner legal --priority high
python3 skills/collaboration-helper/scripts/collaboration_helper.py list
python3 skills/collaboration-helper/scripts/collaboration_helper.py complete 3 --owner legal
This adds a governance action, lists the queue so the team knows what’s pending, and then closes task 3 once it’s done.
References
data/tasks.jsonstores the canonical task list.references/collaboration-guidelines.md(if present) explains how the community prioritizes items and runs handoffs.