pengelbrecht

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.

Work with Ticks issue tracker and AI agent runner. Use when managing tasks or issues with tk commands, running AI agents on epics, breaking down requirements into ticks, or working in a repo with a .tick directory. Triggers on phrases like create ticks, tk, run ticks, epic, close the task, plan this, break this down.

Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.

Create professional SVG logos from descriptions and design specifications. Generates multiple logo variations with different layouts, styles, and concepts. Produces scalable vector graphics that can be used directly or exported to PNG. Use this skill when users ask to create logos, brand identities, icons, or visual marks for their designs.

Work with Ticks issue tracker and Ticker AI agent runner. Use when managing tasks or issues with tk commands, running AI agents on epics, creating ticks from a SPEC.md, or working in a repo with a .tick directory. Triggers on phrases like create ticks, tk, run ticker, epic, close the task, plan this, break this down.

Build professional slide decks from YAML and export to HTML or PDF. Use when users want to create presentations, slide decks, board decks, pitch decks, or quarterly reviews. Also use when users want to modify an existing Lucida deck, add slides, change themes, add logos, or export slides to PDF. Triggers on "create a deck", "make slides", "build a presentation", "quarterly review deck", "board deck", "pitch deck", "export slides to PDF", "lucida", or any task involving structured slide content.

Display rich content (markdown, code, diffs, mermaid diagrams) to users in a browser viewer. Use when you need to show complex content that benefits from rich rendering - reports, documentation, code with syntax highlighting, git diffs, or diagrams.

This skill should be used when debugging web applications, diagnosing page errors, inspecting console output, or capturing screenshots of pages. It provides Chrome DevTools Protocol (CDP) automation via the chromectl.py script for collaborative or automated browser debugging.