skills

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.

Re-ground a session/meeting summary (and every artifact built on it) against the raw transcript, when the summary was written first and the transcript became available later. Use whenever a raw transcript becomes accessible after a summary-based artifact exists, whenever the user pushes back on a fact in a summary, whenever you notice a downstream contradiction, or whenever you're about to edit a contact/reflection/issue that was built on a pre-transcript summary. Do not skip this even if the summary "seems fine" — summaries written from memory or from an AI auto-summary routinely contain speaker mis-attributions, framing drift, missed threads, and inverted consents, and every downstream artifact silently inherits those errors until somebody pulls the tape. This applies to any transcription source (Jamie, Fireflies, Otter, Granola, Rev, manual recording) and any artifact system (markdown sessions, CRM contacts, coaching journals, issue trackers).

Drive two running UIs through matching states, capture side-by-side screenshots at a locked viewport, and produce a markdown + PDF report with per-screen diff notes. Use whenever the user asks to compare a prototype against a port, staging vs production, before vs after a refactor, "does the live site match the design", pixel-fidelity sign-off, visual regression check, or 1:1 parity audit — even if they don't say "audit". Strongly prefer this over ad-hoc screenshotting whenever two versions of the same UI need visual comparison.

Produce a print-ready Event Pack for a SPECIFIC upcoming event (has a date, venue, URL) using Gemini for the design and a real QR overlay. Builds 5+ assets — A6 flyer front/back, A4 4-up home-printable, DJ tent card, 1080×1920 Instagram story — by prompting Gemini to render each full asset (title, date, venue, price, dresscode, and QR *placeholder*) and then compositing a real scannable QR over the placeholder. Use when the user has a concrete event to promote (party, workshop, gig, pop-up, launch) and needs physical + digital promo together. For brand-only cards or single posters without an event, use brand-poster instead.

Generate QR codes with URLs and UTM tracking. Exports PNG/SVG with captions. Supports styled QR codes with custom module shapes (rounded, circle, gapped, bars), colors, gradients (radial, square, horizontal, vertical), and logo overlay. Use for single codes, batch generation, or marketing campaigns with tracking parameters.

Verify a Netlify-hosted form is registered and accepting submissions BEFORE distributing any offline asset (flyer, QR code, business card, print ad, physical signage) that points at the form. Catches the silent failure mode where Netlify only indexes forms seen during a build with form-detection enabled — submissions made before the form is registered hit the static 404 and are irrecoverable. Use this skill whenever the user is about to print/distribute QR codes, flyers, business cards, or any offline material that drives leads to a Netlify-hosted form; whenever a form "works in prod but no submissions are showing up"; whenever the user says "I enabled forms but can't see anything"; or proactively after merging any PR that ships a new Netlify-forms-backed lead capture page. Also covers verifying email notifications are wired so leads are not silently sitting in a dashboard nobody checks.

Process a meeting or call transcript into structured project artifacts — session notes, contact profiles, action items routed to the right destination (markdown / Google Calendar / Google Doc / GitHub issue), and doc updates. Fetches from Jamie (meetjamie.ai) automatically when the user references a recent call they recorded. Use when the user pastes a call transcript, says "process the last Jamie call", "process my call", "extract from meeting", or when a transcript with speaker labels appears in the conversation.

Recover lost registrations after a signup/lead form has been silently broken — diagnose via the Resend email log, classify real users vs tests, re-submit missing contacts to HubSpot via the public Forms API (no auth token needed), and produce a personal follow-up list. Use when the user says "backfill dropped signups", "the registration form was broken", "we lost signups", "check what registrations came through", "recover lost leads", or any variation where a form-to-CRM pipeline has been failing and needs reconciliation. Also use proactively after fixing any registration form bug to check whether real users were lost before the fix.

Turn a markdown operational document (runbook, checklist, SOP, playbook, host script) into a styled print-ready PDF and upload it to a specific Google Drive folder, idempotently — so you can edit the source and regenerate without breaking the Drive link. Use when a user wants a markdown doc rendered as a PDF in Drive, when they ask to "make this printable", "put this in the team folder", "update the PDF in Drive", or whenever an ops doc needs a physical/printable artifact with a stable shareable link. Composes the `latex-pdf` skill (LaTeX template) and the `google-drive` skill (gog CLI) — use this one instead of calling those directly, because it handles the storage convention, the Unicode gotchas, and the re-upload-without-breaking-the-link pattern that you will get wrong by default.

Fire-and-forget agent dispatch. Use when user says '/inbox: <task>' or 'inbox <task>'. Spawns a Claude agent in a tmux session with git worktree isolation. Logs everything for retry. Does NOT wait or check on the agent.

Generate images using Google Gemini API. Use when the user asks to generate, create, or make an image, illustration, poster design, mockup, thumbnail, or any visual asset using AI. Supports uploading reference photos for poster/flyer generation with real people. Also trigger when the user mentions Gemini image generation or asks to visualize something as an image.

Export and share AI chat sessions from Claude Code, Cursor, or Conductor. Lists sessions across providers, exports to markdown, publishes as a GitHub Gist. Use when the user asks to export, share, backup, or review chat history.

Use when a software project under ~/Projects should become a separate organization under ~/Orgs, or when governance files are mixed into a code repo and need to be split into a dedicated org workspace.

Design your organization's governance, roles, and coordination. Use when multiple people or AI agents need clear accountability and decision-making.

Transform video/image lighting, backgrounds, and environments using Beeble SwitchX API. Use this skill when the user wants to relight a video, replace a video background, improve lighting in footage, make a clip look more cinematic or professional, add studio lighting to a recording, or do any video-to-video visual effects transformation. Also trigger when the user mentions Beeble, SwitchX, or wants VFX on short clips.

Set up LiteLLM AI Gateway proxy with Docker Compose for Claude Code Max subscription. Use when the user wants to route Claude Code through LiteLLM for cost tracking, budget controls, or usage monitoring. Also trigger when user mentions "litellm", "AI gateway", "proxy for Claude Code", "track Claude usage", "Claude Code billing", or wants to set up a local proxy between Claude Code and Anthropic API.

Process a livestream transcript into publishable content: blog post (all languages), YouTube metadata with chapters, thumbnail, hero image, and publish. TRIGGER when: user shares a livestream transcript, mentions processing a livestream, says "process stream", references a YouTube live stream recording they want to publish, or pastes a transcript with timestamps. DO NOT TRIGGER for: pre-recorded video editing, podcast episodes without video, or general YouTube video uploads without a transcript.

Scan Gmail for subscription and purchase receipts, extract amounts, categorize spending, and produce a markdown tracker with optional Notion database sync. Use this skill whenever the user wants to: audit subscriptions, review recurring charges, check purchase history, analyze spending, find what they're paying for, cancel unused services, track monthly expenses, check burn rate, review SaaS costs, look at email receipts/invoices, update a subscription tracker, or do any kind of expense review based on email data. Even if the user just says something casual like "what am i paying for" or "check my spending" or "how much do my subscriptions cost" — this is the right skill. Also use when the user wants to sync subscription data to Notion or create a spending breakdown by category.

Add internationalization (i18n) to a Nuxt 3 project — install @nuxtjs/i18n, extract hardcoded strings from components into locale JSON files, configure routing strategy, create a language switcher component, and fix hosting config for SSR locale routes. Use this skill whenever the user wants to translate a Nuxt site, add multiple languages, add a language switcher, localize content, or migrate a monolingual Nuxt site to multilingual. Also triggers when adding specific languages (e.g., "add German to my site") or when the user mentions i18n, localization, or translation in a Nuxt context.

Produce AI avatar YouTube videos using the Julia McCoy method: write scripts with Claude, generate avatar with HeyGen, clone voice with ElevenLabs. Use when the user wants to create YouTube content at scale using AI avatars, plan an avatar video pipeline, write video scripts, or audit readiness for AI-powered video production. Triggers: 'create avatar video', 'julia mccoy method', 'AI YouTube pipeline', 'avatar content plan', 'write video script for avatar', 'scale YouTube with AI'.

Interact with Atlassian Jira and Confluence from the terminal. Search, create, and update Jira tickets; read, search, create, and update Confluence pages. Use when the user mentions Jira tickets, issues, work items, sprints, Confluence pages, documentation, or Atlassian in general.

Write BDD scenarios grounded in existing UI/UX implementation. Researches pages, components, types, and mock data before writing any scenario. Use when generating .feature files for a product that already has a working app or prototype.

Onboard a new Claude Code user — set up their ~/.claude/CLAUDE.md, install relevant skills, and start a structured learning program covering best practices. Use when setting up Claude Code for the first time, onboarding someone to Claude Code, or continuing a learning session.

Generate poster images. Use when the user asks to create a poster, flyer, print material, social media graphic, or any visual marketing asset

AI content and SEO agent that audits sites, fixes indexing issues, writes blog posts aligned with OKRs, generates YouTube metadata, and produces monthly analytics reports. Use when asked to run SEO audit, write a blog post, create content calendar, fix indexing, generate YouTube descriptions, or produce an analytics report.

Daily SEO health check for dancegods + razbakov.com. Checks indexing status, sitemap, meta tags, and structured data. Reports findings and flags issues for the daily review pipeline. Use when running the morning SEO check or when asked for an SEO status report.

Runs dependency vulnerability scans and produces a complete report with exact installed versions, reason for risk, and remediation priority for each finding. Use when the user asks for dependency scan, npm audit, bun audit, package vulnerabilities, CVE review, or security status of dependencies.

Design Sprint Facilitation — guide any idea through a structured 6-phase sprint. Use when the user says 'design sprint', 'sprint my idea', 'facilitate a sprint', 'run a design sprint', or wants structured ideation with decision checkpoints.

Use when the user says "develop PP-XYZ" or asks to work on, develop, or implement a ticket, issue, or story referenced by ID

Connect a Telegram bot to any Claude Code agent for collaborative group chats. Use when the user wants to set up a Telegram chat where external people (co-founders, partners, clients) can interact with an AI agent. Triggers include "connect bot to agent", "set up group chat with agent", "add person to agent chat", "envoy connect", or when creating collaborative Telegram groups with AI agents.

Estimate the effort of user stories, tasks, bugs, or raw requirements using story points. Use when the user asks to estimate, size, or score a ticket, story, feature, or piece of work.

Use when ordering groceries from Flink, adding items to Flink cart, or reordering from a previous shopping list. Requires user logged into goflink.com in Chrome.

Search a freelance platform for jobs matching user's skills, verify each listing is live with actual budget, and create a project with verified opportunities and draft proposals.