razbakov/skills/daily-review
skills/daily-review/SKILL.md
Daily Review (Meta-Skill) — orchestrates child skills: gather browser history, AI transcripts, app usage, process Telegram inbox, process Chrome bookmarks, snapshot portfolio DAU, sync all projects, suggest agent tasks, suggest today's plan, sync to calendar, and save the review.
$ install --global
skillsauthnpx skillsauth add razbakov/skills skills/daily-reviewInstall 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 26, 2026, 10:32 AM36.9s1 file scanned
SKILL.md
- description:
- Daily Review (Meta-Skill) — orchestrates child skills: gather browser history, AI transcripts, app usage, process Telegram inbox, process Chrome bookmarks, snapshot portfolio DAU, sync all projects, suggest agent tasks, suggest today's plan, sync to calendar, and save the review.
- 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 (Meta-Skill)
Run from the ikigai project directory. Gathers yesterday's activity, syncs all project next steps (with full git analysis), suggests today's plan, and adds approved plan to Google Calendar. Saves the review to sessions/YYYY-MM-DD-daily-review.md.
This meta-skill orchestrates the following child skills in order:
- daily-review-browser-history — Gather yesterday's Chrome browser history
- daily-review-ai-transcripts — Gather yesterday's AI session transcripts
- daily-review-app-usage — Query macOS app focus time
- process-inbox — Collect Telegram + process Notion "To do" cards (GTD full pipeline)
- daily-review-browser-bookmarks — Process Chrome bookmarks (GTD) 5.5. analytics-check — Snapshot portfolio DAU. Read by multiple agents daily: Viktor (tracking health, zero = bug), Luna (content/SEO levers), Kai (community/partnership levers for event-driven projects), project coordinators (own their KR).
- daily-review-sync-projects — Discover, pull, analyze all projects 6.5. suggest-tasks — Propose agent tasks with assignments (Viktor/Luna/Marco/Kai)
- daily-review-suggest-plan — Propose today's schedule with OKR view
- daily-review-calendar-sync — Create Google Calendar events
- daily-review-save-review — Save complete review to sessions file
Trigger
User says "daily review", "let's review projects", "daily check-in", or invokes /daily-review.
Context
- Working directory:
~/Projects/ikigai - Google account: From CLAUDE.md Personal Info
- Calendar tool:
gog cal - Projects directory:
~/Projects/ - Project inventory:
PROJECTS.mdin ikigai workspace - OKRs and focus:
README.mdin ikigai workspace - Session storage:
sessions/
Execution
Phase 1 — Gather Yesterday's Data (parallel)
Run steps 1-5 in parallel where possible to save time.
Step 1: Browser History
Invoke: //daily-review-browser-history
Captures: sessions/YYYY-MM-DD-browser.md
Step 2: AI Transcripts
Invoke: //daily-review-ai-transcripts
Captures: sessions/YYYY-MM-DD-ai-sessions.md
Step 3: App Usage
Invoke: //daily-review-app-usage
Depends on: Step 1 (appends to browser.md)
Captures: App usage section in sessions/YYYY-MM-DD-browser.md
Step 4: Process Inbox (Telegram + Notion)
Invoke: //process-inbox
Captures: Telegram export → Notion cards → agent dispatch. Saves inbox/YYYY-MM-DD-HH-MM.md, creates Control Center cards, dispatches agents for "To do" items.
Step 5: Browser Bookmarks
Invoke: //daily-review-browser-bookmarks
Captures: inbox/YYYY-MM-DD-HH-MM-bookmarks.md, updated project docs
Step 5.5: Portfolio DAU snapshot
Invoke: //analytics-check (portfolio mode, no save)
Captures: per-project DAU table in the daily review file. DAU is a shared organ — multiple agents read the snapshot daily to pull different levers:
- Viktor (CTO) — tracking health. Any project at 0 events or unexpected silence on a project claimed to be live = SDK bug, fix within 48h.
- Luna (Content & Growth) — content/SEO levers. Below-target DAU on a content-driven project = "what gets published or shared today to move it?"
- Kai (Community & Partnerships) — community/partnership levers for event-driven projects. Below-target DAU on event projects = "which Munich channel, IG account, or partner can route traffic today?"
- Project coordinators — own their project's KR; pull every lever available.
Keep the daily output short: one row per project with yesterday's DAU, a delta vs the 7-day baseline, and a flag column noting which agent should look at it (tracking gap → Viktor; flat above 0 → Luna or Kai based on project type; hitting target → nobody).
Phase 2 — Sync & Plan (sequential)
Step 6: Sync Projects
Invoke: //daily-review-sync-projects
Depends on: Steps 4-5 (Telegram and bookmark items may add tasks to projects)
Captures: Numbered project list with a/b/c task IDs, updated PROJECTS.md
User interaction: "Which projects do you want to focus on today?"
Step 6.5: Suggest Agent Tasks
Invoke: //suggest-tasks
Depends on: Step 6 (needs project list, PROJECTS.md, and Notion state)
Captures: "Suggested" cards in Notion Control Center with agent assignments (Viktor/Luna/Marco/Kai)
No user interaction needed — cards are created silently. The suggest-plan step (7) will mention how many agent tasks were suggested.
Step 7: Suggest Plan
Invoke: //daily-review-suggest-plan
Depends on: Steps 1-6 (needs yesterday's data + project list with task IDs)
Captures: OKR view with proposed schedule
User interaction: "Does this plan work, or do you want to adjust?"
Step 8: Calendar Sync
Invoke: //daily-review-calendar-sync
Depends on: Step 7 (needs approved schedule)
Captures: List of calendar events created
Step 9: Save Review
Invoke: //daily-review-save-review
Depends on: All previous steps
Captures: sessions/YYYY-MM-DD-daily-review.md
User interaction: Personal journaling prompt. (Scrum standup is handled separately by /daily-standup at 9am.)
Notes
- Each child skill can also be run independently via
/daily-review-{name} - If a step fails, fix the issue and re-run that specific child skill
- If the user says "skip yesterday" — jump straight to Step 6
- Steps 1, 2, 4, 5, and 5.5 have no dependencies on each other and should run in parallel
- Step 3 depends on Step 1 (appends to the same file)
- Sub-agents in Step 6 should run in parallel for speed — one agent per project
- If today is Saturday, Step 7 will remind about the weekly review
- Always print the full output (project list + OKR view) to chat. Saving to file is not a substitute for showing the user. This applies to BOTH interactive and automated/scheduled runs — the user reads the output after the fact
- Actionable items from Telegram inbox and bookmarks should be merged into the project list
- Automated runs: When running as a scheduled task without the user present, still execute ALL steps including full project sync (Step 6). Skip only steps that truly require real-time user input (plan approval, journaling). Always produce the complete report with git pull table + numbered project list + OKR view
- Project paths: Many repos are nested. Always read the Project Path Registry from CLAUDE.md — never assume
~/Projects/<name>/.git
Related Skills
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
razbakov/translate-blog-post
testing
VerifiedTrustedCommunity
Translate one English blog post into multiple target languages via parallel sub-agents, preserving frontmatter conventions, hero image, and brand voice. Use when the user shares a published English post URL or markdown path and says 'translate it', 'add other languages', 'publish in DE/ES/RU/UK', 'translate to 5 languages', or asks for localized versions of a specific post.
3SKILL.mdUpdated May 20, 2026
razbakov/press-kit-pack
development
VerifiedTrustedCommunity
Build a complete press kit for an event, product launch, or campaign — in multiple languages — and publish it as a shareable Google Drive folder ready to send to journalists, partners, or a delegate. Produces press releases (typically DE/EN/ES, or configurable), uploads press photos and flyers, creates an Overview document for at-a-glance briefing, and creates a Handover document with pending tasks, contacts, risks, and decisions so press distribution can be delegated. Use when the user says 'I need a press release', 'create a press kit', 'press release in X languages', 'set up a Drive folder for press', 'handover doc for someone else to run press', or has an upcoming announcement that needs to be sent to media. Trigger generously: even partial requests (just a press release, just a flyer folder) typically evolve into the full kit.
3SKILL.mdUpdated May 20, 2026
razbakov/concert-burndown
development
VerifiedTrustedCommunity
Track ticket sales for a live event (concert, festival, conference, workshop) with daily snapshots, generate a burndown chart comparing actual sales to ideal-linear targets and tier-cumulative milestones, and report whether the event is on pace. Use when the user asks how sales are going, wants to know if their event will sell out, asks for a daily sales report, wants to set up sales tracking for an upcoming event, or asks about ticket pace / velocity / projection. Trigger generously: phrases like 'how is concert sales going', 'burndown for my event', 'are we going to sell out', 'sales velocity', 'daily ticket chart', 'how many tickets do we need to sell', or any case where the user has a ticketed event with a fixed sales window and wants visibility on pacing.
3SKILL.mdUpdated May 20, 2026