skills/dispatch-approved/SKILL.md
Dispatch all approved agent tasks from Notion Control Center. Picks up cards where Status='To do' and Assigned Agent is set, then launches each via the /inbox pattern (worktree + tmux). Always manual — never auto-runs.
npx skillsauth add razbakov/skills skills/dispatch-approvedInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
⚠️ Migration in progress (razbakov/ikigai#73): Control Center has moved from Notion to GitHub Issues + Project v2. When this skill references creating/reading/updating Notion cards or pages, translate to GitHub equivalents:
- Create card →
gh issue create --repo <project-repo> --title "<title>" --label agent:<name> --body "<S3 body>"thengh project item-add 5 --owner razbakov --url <issue-url>- Read cards →
gh issue list --repo <repo> --label agent:<name> --state open(or across repos viagh search issues "org:razbakov label:agent:<name> state:open")- Update card status → move on board:
gh project item-editwith the Status field, or close viagh issue close- Board columns: Inbox → To do → In progress → To review → Done
- Do not call any
notion-*MCP tools — the Notion MCP is disabled.
Picks up Notion Control Center cards that Alex has approved (moved from "Suggested" to "To do") and dispatches an AI agent for each one using the standard /inbox pattern.
User says /dispatch-approved, "dispatch approved tasks", "launch approved agents", or "run approved".
~/Projects/ikigaicollection://32b9a1fd-a351-809d-bd4d-000b0d579048/inbox skill exactly (worktree, tmux, Notion update)CLAUDE.md (maps project names to git repo paths)initiatives/agent-team.md (personas for Viktor/Luna/Marco/Kai)Search the Control Center for cards where:
notion-search(query: "To do", data_source_url: "collection://32b9a1fd-a351-809d-bd4d-000b0d579048", page_size: 25)
For each result, fetch the full card to read:
Filter to only cards that have "Assigned Agent" set — cards without an agent assignment were created by other skills (process-inbox, manual) and should be dispatched via /inbox directly.
If Assigned Agent = "Maya", these are operational tasks Maya handles directly (inbox processing, calendar sync, etc.). Skip them — they don't need agent dispatch.
For each agent, include their persona in the dispatch prompt:
Viktor (CTO): "You are Viktor, the CTO. Direct, technical, quality-focused. You own all engineering: write/review/ship code, tests, CI, deployments. Must create PRs for changes. Does not decide product direction or handle marketing."
Luna (Head of Content): "You are Luna, Head of Content & Growth. Creative, energetic, trend-aware. Turn ideas into published content: blog posts, social posts, SEO audits, visual assets, campaigns. Must reflect Alex's authentic voice. All content reviewed by Alex before publishing."
Marco (Head of Strategy): "You are Marco, Head of Strategy & Business. Analytical, structured, results-focused. OKRs, portfolio prioritization, business development, hypothesis validation, competitor analysis. Makes recommendations — Alex decides."
Kai (Community Manager): "You are Kai, Community & Partnerships Manager. Social, connector-minded, organized about people. Event prep, contact enrichment, partnership management, community channels, networking. Alex is the face — Kai never represents Alex externally."
For each approved card, follow the /inbox skill process exactly:
echo "$(date -Iseconds) | DISPATCHED | ${TASK_SLUG} | ${PROJECT} | [dispatch-approved] ${CARD_TITLE}" >> ~/Tasks/inbox.log
Look up the project in the Project Path Registry (CLAUDE.md). Use that path for the git worktree.
TASK_SLUG=$(echo "${CARD_TITLE}" | tr '[:upper:]' '[:lower:]' | tr ' ' '-' | tr -cd 'a-z0-9-' | head -c 40)
TASK_DIR=~/Tasks/${PROJECT}-${TASK_SLUG}
git -C <repo_path> worktree add ${TASK_DIR} -b agent/${TASK_SLUG} main
cd ${TASK_DIR} && bun install --frozen-lockfile 2>/dev/null || npm ci 2>/dev/null || true
Write ${TASK_DIR}/agent-prompt.md with:
SESSION_NAME="wf-${TASK_SLUG}"
tmux new-session -d -s "${SESSION_NAME}" -c "${TASK_DIR}" "/tmp/run-${TASK_SLUG}.sh"
notion-update-page(
page_id: "<card_id>",
command: "update_properties",
properties: { "Status": "In progress" }
)
Print to chat:
## Dispatched Agents
| # | Task | Project | Agent | tmux session |
|---|------|---------|-------|-------------|
| 1 | Fix Dropbox sync | sdtv | Viktor | wf-fix-dropbox-sync |
| 2 | Write blog post | razbakov.com | Luna | wf-write-blog-post |
Dispatched N agents. Use `/scrum` to check status.
Skipped M Maya-assigned tasks (operational, not dispatchable).
/dispatch-approved.tools
--- name: handoff description: Get an agent past a browser/UI wall it can't (or must not) cross on its own — a login-gated dashboard, a CAPTCHA, a 2FA prompt, an API that keeps rejecting the write, or an irreversible click that policy says a human must make. This skill is an ESCALATION LADDER, not a first move: it tells you to try the automated browser surfaces FIRST (Chrome-in-Claude, computer-use, an autonomous browser sub-agent) and only fall back to the Handoff app — a wrapper browser that h
documentation
Summarize one or more YouTube videos from their links. Use this whenever the user pastes a youtube.com or youtu.be URL (or several) and wants to know what it's about — phrasings like "summarize to telegram", "tldr these videos", "what do these say", "summary of this talk", or just dropping links with no instruction at all. Fetches each video's real transcript via yt-dlp (not the page text, which never contains the transcript), cleans the captions, and writes a per-video summary. Default delivery is Telegram; honor any other surface the user names ("to my notes", "just here in chat", "email it"). Trigger even when the user only pastes bare links — bare YouTube links almost always mean "tell me what's in these".
data-ai
Daily Digest — Chief-of-Staff role consolidates the six top-managers into one Telegram message to the Commander, instead of six. Implements the protocol from agent-proactivity.md.
development
Seed a new or empty Instagram account with a 9-post grid (3×3) so the profile looks established the moment a new visitor lands. Designed for festivals, new businesses, product launches, conferences, communities — any time an empty IG profile would hurt conversion from external traffic (QR scans, flyer drops, cross-promo). Generates assets via /image-from-gemini (per content-publishing rules — never HTML), writes captions with hashtag sets, and outputs a posting order + cadence plan. Trigger generously: phrases like '9 posts for instagram', 'fill my IG', 'starter grid', 'launch grid', 'instagram seed', '9-post grid', 'IG account not to look empty', 'first instagram posts', 'feed bootstrap', '3x3 grid', 'instagram launch content'. Even if the user mentions only one piece (just the images, just the captions, just the order), use this skill — the grid only works as an integrated bundle.