razbakov/skills/daily-review-suggest-plan
skills/daily-review-suggest-plan/SKILL.md
Read calendar, OKRs, yesterday's activity, and project list to propose today's schedule with task IDs. Part of the daily review workflow.
$ install --global
skillsauthnpx skillsauth add razbakov/skills skills/daily-review-suggest-planInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 18, 2026, 5:04 AM185.4s1 file scanned
SKILL.md
- description:
- Read calendar, OKRs, yesterday's activity, and project list to propose today's schedule with task IDs. Part of the daily review workflow.
- user_invocable:
- true
⚠️ 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.
Daily Review — Suggest Today's Plan (GTD Reflect + Engage)
Uses task IDs from the project sync step. Reorganizes tasks by objective, adds risks/unknowns, and picks what matters today.
Trigger
Invoked as part of /daily-review or independently via /daily-review-suggest-plan.
Context
- Working directory:
~/Projects/ikigai - Google account: From CLAUDE.md Personal Info
- Calendar tool:
gog cal - OKRs:
README.mdin ikigai workspace - Project list: Output from
/daily-review-sync-projects(numbered tasks with a/b/c IDs) - Yesterday's activity:
sessions/YYYY-MM-DD-browser.md,sessions/YYYY-MM-DD-ai-sessions.md
Process
1. Read today's calendar
gog cal ls --from today --to today
2. Read OKRs
Read README.md for current OKRs and focus areas.
3. Review yesterday's activity
From browser history, AI sessions, and app usage files — what had momentum?
4. Check contacts for pending commitments
Scan contacts/*/contact.md for deadlines or promises.
5. Present the OKR view
One section per objective, referencing task IDs from the project list:
## Yesterday
<2-3 sentence summary from browser + AI session + app usage files>
## Today's Calendar
<existing events>
## O1: <Objective name>
**Risks:** what could stop us from reaching the objective?
**Unknowns:** what should we figure out to avoid obstacles?
**Next Steps:**
- <id> — <project> — <task>
- <id> — <project> — <task>
## O2: <Objective name>
**Risks:** ...
**Unknowns:** ...
**Next Steps:**
- <id> — <project> — <task>
- <id> — <project> — <task>
### Proposed Schedule
| Time | Tasks |
|------|-------|
| HH:MM-HH:MM | <id>, <id> — <project> — <summary> |
| HH:MM-HH:MM | <id>, <id> — <project> — <summary> |
Format rules:
- Task IDs reference the project list (e.g., "2a" = project 2, task a)
- Each next step line format:
<id> — <project> — <task> - Tasks are defined once in the project list, only referenced here — no duplication
- Next Steps are ordered by priority within each objective, not by project number
- The schedule uses the same IDs so the user can trace back to the project
- Output headings should NOT include internal step numbers (no "Step 4", "Step 5")
Prioritization rules:
- Deadlines first (what's due soonest?)
- OKR alignment (does it move a key result?)
- Partner commitments (promises to Kirill, etc.)
- Momentum (what was in progress yesterday?)
- Avoid context switching — max 3 projects per day
6. Mention suggested agent tasks
If /suggest-tasks ran before this step (e.g., as part of daily-review step 6.5), include a section:
## Agent Tasks (Suggested)
N new tasks suggested in Notion Control Center:
- <task> → <Agent> (Priority)
- <task> → <Agent> (Priority)
To approve: review in Notion → drag "Suggested" → "To do" → run `/dispatch-approved`
If suggest-tasks did not run, skip this section.
7. Add meal suggestion to lunch/dinner blocks
When the proposed schedule includes a lunch or dinner block, invoke /meal-suggestion to populate it with inventory-checked meal options. The meal suggestion output goes into the calendar event description when syncing.
8. Check current time
Always check the system clock to avoid suggesting past time blocks.
9. Saturday reminder
If today is Saturday, remind about the weekly review + planning ritual (10:00-11:00).
Ask: "Does this plan work, or do you want to adjust?"
Output
The full OKR view with proposed schedule, printed to chat.
Related Skills
razbakov/skills/handoff
tools
VerifiedTrustedCommunity
--- 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
3SKILL.mdUpdated Jul 17, 2026
razbakov/summarize-youtube
documentation
VerifiedTrustedCommunity
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".
3SKILL.mdUpdated Jun 15, 2026
razbakov/skills/daily-digest
data-ai
VerifiedTrustedCommunity
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.
3SKILL.mdUpdated Jun 15, 2026
razbakov/instagram-launch-grid
development
VerifiedTrustedCommunity
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.
3SKILL.mdUpdated May 21, 2026