notion-sync
notion-sync
Sync a task to the laniameda Notion kanban board. Use this whenever you create or update a task.md file in any pm/todos/ folder.
When to use
- After creating a new task folder + task.md
- After updating the Status of an existing task
- After completing a task (status → Done)
- When asked to update the board
Config
NOTION_KEY=$(cat ~/.config/notion/api_key)
DB_ID="316e9215-3d4b-8145-b6c7-c468224f2391"
Sync a task (create or update by name)
python3 /root/.openclaw/workspace/skills/notion-sync/sync.py \
--name "Task name" \
--status "In Progress" \
--agent "Lani" \
--priority "High" \
--department "Operations" \
--area "Infrastructure" \
--notes "Short context note"
Status values
Idea | Research | In Progress | Review | Done
Agent values
Lani | Meda | Persey | Michael | All
Priority values
High | Medium | Low
Department values (in priority order)
Marketing | Dev | Operations
Area values
Infrastructure | laniameda.gallery | RunMusic | Content & Marketing | Agent System | Website | AI Creator OS
Notes
- Script upserts by name — updates existing task if found, creates new one if not
- Always call this after writing to a task.md file
- Department is the most important field — Marketing is always top priority
More from michailbul/laniameda-skills
instagram-extract
Extract text, links, and key takeaways from Instagram/Threads posts (especially carousels) and LinkedIn posts using an already-logged-in Brave/Chrome tab via OpenClaw Browser Relay. Use when the user pastes an Instagram/Threads/LinkedIn URL (or forwards screenshots) and asks something generic like “save it”, “capture this”, “summarize and store”, or “put this in the vault” — you should decide what’s worth saving, classify it into the right pillar, save it to the local KB and/or ingest prompts via the laniameda-kb skill, and also emit a compact JSON payload into a media-agent inbox file for downstream reuse.
12carousel-designer
>
11andromeda-messages
>
10deepgram-transcribe
>
10repo-kanban-pm
Install and enforce a lightweight product-management workflow inside a code repo: feature-as-kanban boards, ROADMAP status tracking, branch/PR conventions, and an optional daily OpenClaw cron PM review. Use this skill when (1) starting work in a NEW repository/project that does not yet have a ROADMAP+feature-KANBAN system, (2) you are delegated to spin up a new project and want multi-agent coordination from day one, or (3) you are asked to fix/restructure an existing repo and introduce an organized backlog/feature tracking system. Also use when adding a daily PM audit loop (cron) to keep code + docs + PRs in sync.
10supadata
>
10