skills

Use when any task involves the user's personal Telegram — reading messages, checking unreads, listing chats, searching history, or sending/replying to messages. Covers requests like "check my telegram", "what's new in <chat>", "search telegram for X", "reply to <person>", "send a telegram message". Also use for agent-to-agent (A2A) coordination with other people's agents in a shared Telegram group, and when setting up Telegram access on a new machine.

Record narrated, captioned screen recording videos of web applications. Use this skill whenever the user wants to create a video demo, screencast, walkthrough, or recording of a web app — whether local (localhost) or public. Triggers on phrases like "record a demo", "make a video of this feature", "create a walkthrough", "screencast with voiceover", "demo video for a PR", "narrated recording", "generate a video demo", "show me how this works on video", or any request involving recording a web app with spoken narration and subtitles. Also trigger when users want to attach video evidence to pull requests, generate onboarding walkthroughs, or create feature demos for stakeholders. Even if the user just says "make a video" or "record this" in the context of a web app, use this skill.

Make a project expose the same functionality across CLI, MCP, and REST — one core, N projections, drift caught mechanically. Use this skill whenever a project needs agent access: "add an MCP server", "build a CLI for this", "expose this to agents", "should this be CLI or MCP?", or when surfaces already exist and misbehave: "keep CLI/MCP/REST in sync", "my MCP and CLI behave differently", "the API has features the CLI doesn't". Also use it for the operational half of shipping a CLI: distribution ("how do users install this?"), in-place upgrades ("self-update", "version check"), and auth for agent surfaces (OAuth for MCP, device-code login for CLI, API keys). Trigger even when the project has neither a CLI nor an MCP server yet — designing the first surface correctly is the cheapest moment to apply this skill.

Research a topic from the last 30 days on Reddit + X + Web, become an expert, and write copy-paste-ready prompts for the user's target tool.

Build and maintain a living, agent-first knowledge base for a git repo — a "repo-wiki" of architecture, decisions, constraints, product context, and glossary that stays trustworthy because staleness is detected by git and tacit knowledge is captured from chats. Use this skill whenever a project's docs are sprawling or out of date, when onboarding context lives only in people's heads, or when the user wants to "set up a knowledge base", "document the architecture", "write an ADR / decision record", "capture why we did X", "stop the docs from rotting", "keep docs in sync with the code", or "create a repo wiki". Also trigger when an agent needs durable project context across sessions, when CLAUDE.md / AGENTS.md has become a junk drawer, or after a substantial design discussion whose reasoning would otherwise be lost. Even a vague "our docs are a mess" or "how do we keep track of decisions" should pull this in.

Write, review, refactor, and explain TypeScript code that uses the Effect library. Use when working with Effect, Effect.gen, yield*, pipe, Layer, Context services, typed errors, retries, spans, dependency injection, or when converting Promise/async/await or imperative TypeScript into readable Effect code. Triggers on "Effect", "effect-ts", "Effect.gen", "yield*", ".pipe", "Layer", "Context.Tag", "catchTag", "withSpan", "retry", "typed errors", or requests to make Effect code easier to read or adopt.

How to query Metricly correctly to answer analytical questions. Use when the user is asking analytical/business questions, when an agent is connected to a Metricly MCP server, when running `metricly query ...` from the terminal, or when scripting against Metricly's REST API. Covers all three surfaces (MCP, CLI, REST) — same principles, different invocations.

Conventions for writing dbt YAML descriptions and the org's business_context doc. Use when editing dbt/models/**.yml, dbt/context/business_context.md, or any file that feeds Metricly's semantic layer or org context.

Break large engineering tasks into planned, validated missions executed by specialized agents. Use this skill whenever the user wants to tackle a task that is too large or complex for a single session — multi-feature work, full-stack buildouts, large refactors, or any project that benefits from structured planning, parallel execution, and independent validation. Triggers on phrases like "start a mission", "plan a mission", "mission to build X", "break this into milestones", "I need a structured plan for X", "orchestrate building X", "multi-step project", or any request that implies decomposing large work into validated stages. Also triggers on "/missions".

Interactive Claude Code tutor that teaches power-user workflows through hands-on exercises and quizzes. Covers foundations (mental model, context, prompting, skills, external systems), coding workflows (project bootstrap, features, browser-driven dev, code quality, data, deployment), non-coding power moves (research, presentations, business analysis, browser automation, content creation), and advanced patterns (multi-agent, skill building, hooks, sessions). Use whenever someone says "teach me Claude Code", "tutor me", "learn Claude Code", "claude code tutorial", "show me how to use this", "how should I use Claude Code", or any request to learn Claude Code workflows, tips, or best practices. Also trigger when users seem new to Claude Code and would benefit from guided learning, even if they don't explicitly ask for a tutorial.

Create polished, professional Google Slides presentations using the gws CLI. Use this skill whenever the user wants to create, update, or improve a Google Slides presentation — whether from scratch, from an outline, or by fixing an ugly existing deck. Triggers on phrases like "make a presentation", "create slides", "build a deck", "fix my slides", "make these slides look better", "presentation about X", "slide deck for X", "pitch deck", "keynote-style slides", "investor deck", "update my Google Slides", or any request involving Google Slides authoring. Also triggers when users mention gws slides, batchUpdate, or Slides API in the context of creating visual content.

Reverse-engineer and clone any website into production-ready Astro 6 code. Extracts assets, exact CSS, content, and behaviors section-by-section, writes component specs, then dispatches parallel builder agents in worktrees. Use when user asks to: clone website, vibe clone, replicate landing page, copy website design, rebuild this site, recreate this page, clone specific sections (hero, pricing, footer, etc). Triggers: "clone this website", "vibe clone [url]", "replicate this landing page", "rebuild this site in Astro", "clone the hero section from [url]", "copy this design".