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 hands the human a checklist beside the live page and reports a machine-readable "done" back — when those genuinely hit a wall. Reach for it on "I'm blocked and need a human to do X in the browser", "add this DNS record / approve this deploy / accept these terms and tell me when done", "the API 422'd, over to the human", "I can't get past this login/CAPTCHA/2FA", or any moment you'd otherwise paste a paragraph of manual steps and hope the human follows them. It auto-installs the Handoff app on first use.
Turn a product's landing/marketing pages into a prioritized, gap-analyzed backlog. Use this whenever the user wants to audit what a site promises vs. what is actually built, convert marketing/landing copy into user stories, map work to Critical User Journeys (CUJs) and Jobs-To-Be-Done (JTBDs), score a backlog with WSJF, or populate an issue tracker (Linear, Jira, GitHub Issues) plus a tracking spreadsheet from a product's promises — even if they don't say the word "backlog" or "skill". Reach for it on requests like "audit our landing pages", "promise vs reality / what do we promise that we haven't built", "turn the marketing into a backlog", "make user stories from the site", "build a CUJ/JTBD map", "prioritize this with WSJF", or "get our promises into Linear/Jira". Also use it to maintain such a backlog after it exists.
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".
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.
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.
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.
Take a long stream-of-thought transcript (voice memo, video reflection, text dump) and turn it into a cluster of 5-20 publishable blog essays. Clusters ideas by theme, drafts each essay via parallel sub-agents, generates Gemini hero images, batch-commits, and (optionally) sends a grouped link list via the user's preferred messaging surface. Use when the user shares a transcript and says 'turn this into essays', 'write a series', 'split into posts', 'draft all of them', or pastes a long stream of ideas they want shipped.
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.