Generate branded Google Docs from Markdown with full formatting. Only use when the user explicitly asks to create a branded Google Doc, generate a Google Doc with branding, or says "branded gdoc".
This skill should be used when the user asks to "tidy up", "clean up the project", "organise files", "archive old files", "update the README", "prepare for handoff", or when a project needs documentation and file organisation before switching contexts.
Fetch LinkedIn posts and comments for any person or configured list of people. Uses the Voyager API via browser cookies (no stored credentials, no API costs). Use when you want to check what someone is posting on LinkedIn, research a person's recent activity, or run batch monitoring for newsletter curation, competitive intelligence, or partner briefings.
Run quality verification and review loop on session deliverables. Detects organisation from context and applies appropriate review standards. Manually invoked only.
Challenge design decisions, documents, and plans with 5-7 specific critiques across six categories
Manage your Google Calendar via Python API. Use when asked to: - Add flights from booking emails or text - Add travel blocks before/after flights - Query calendar for availability, conflicts, or upcoming events - Create reminders for car rentals, pickups, etc. Triggers: "add this flight", "check my calendar", "when am I free", "add travel blocks", "what's on my calendar", "find my flights"
Message the user on Telegram when you need input, want to report progress, or need real-time discussion. Use for completed tasks, blocking questions, or milestone celebrations.
Sync Markdown files to Google Docs, preserving a stable URL. Use when: - User says "sync to Google Docs", "push to gdocs", "update the Google Doc" - User wants a Markdown file available at a permanent Google Docs URL - After generating a context file or report that should be accessible via Google Docs - User asks to "create a Google Doc" from a Markdown file Creates new Google Docs on first run, updates the same document on subsequent runs. The document ID is stored in a JSON file alongside the source, so the URL never changes.