elviskahoro

Redeploy the Beacon telemetry launch agents (sidecar collector + traces bridge) with fresh Infisical credentials from dotfiles/beacon.env, TCC-safely.

[Warp terminal app ONLY] Add MCP servers to Warp's MCP config files (~/.warp/.mcp.json or {repo}/.warp/.mcp.json). Trigger ONLY when the user is configuring MCP for the Warp terminal app specifically. Do NOT trigger for Claude Code, Cursor, Zed, Continue, Cline, or any other tool's MCP configuration — those have different config paths and formats. If the user just says 'add an MCP server' without naming Warp, ask which tool before invoking this skill.

[Bundled with the Warp terminal app] Build, debug, and optimize Claude API / Anthropic SDK apps. Apps built with this skill should include prompt caching. Also handles migrating existing Claude API code between Claude model versions (4.5 → 4.6, 4.6 → 4.7, retired-model replacements). TRIGGER ONLY when: code imports `anthropic`/`@anthropic-ai/sdk`; the user explicitly asks for the Claude API, Anthropic SDK, or Anthropic Managed Agents; user adds/modifies/tunes a Claude-specific feature (caching, thinking, compaction, tool use, batch, files, citations, memory) or model (Opus/Sonnet/Haiku) in an Anthropic SDK file; questions about prompt caching / cache hit rate in an Anthropic SDK project. SKIP for: file imports `openai`/other-provider SDK, filename like `*-openai.py`/`*-generic.py`, provider-neutral code, general programming/ML, or any task that does not specifically involve Anthropic's API.

[Bundled with the Warp terminal app] Create or modify agent skill packages (SKILL.md files with frontmatter, plus their scripts/references). Trigger ONLY when the user explicitly wants to author, edit, evaluate, or benchmark an agent skill — meaning a skill in the SKILL.md / agent-skill format used by Warp, Claude Code, or Anthropic agents. Do NOT trigger for general code authoring, writing utility functions, refactoring, creating CLI tools, or any task that the user has not specifically framed as 'building/editing a skill'.

[Warp terminal app ONLY] Create new Warp tab config TOML files (Warp's terminal-tab layout files in ~/.warp/tab_configs/). Trigger ONLY when the user is creating a layout for the Warp terminal app specifically. Do NOT trigger for tmux configs, iTerm/Terminal.app profiles, VS Code/JetBrains workspace layouts, browser tabs, or any non-Warp 'tab' or 'layout' concept. If the user just says 'tab config' or 'tab layout' without naming Warp, ask which tool before invoking.

[Warp terminal app ONLY] Turn rough feedback about the Warp terminal app into a filed GitHub issue (or duplicate-issue response) on the `warpdotdev/warp` repo. Trigger ONLY when the user is reporting a bug, regression, UX issue, or feature gap specifically about the Warp terminal app and wants it filed against warpdotdev/warp. Do NOT trigger for: feedback about other apps/tools, generic 'I have feedback' messages, complaints about Claude/this assistant, requests to file issues against other repos, or general bug reporting workflows. If the target app/repo is unclear, ask before invoking.

[Warp terminal app ONLY] View or modify Warp terminal application settings using Warp's bundled JSON schema. Trigger ONLY when the user is changing settings of the Warp terminal app specifically. Do NOT trigger for: Claude Code settings.json, shell rc files (.zshrc/.bashrc), git config, IDE/editor settings, OS preferences, or any other application's configuration. If the user just says 'change a setting' without naming Warp, ask which app before invoking.

[Warp terminal app ONLY — Warp's Oz cloud agent platform] Use Warp's Oz REST API and CLI to spawn, schedule, configure, and inspect Warp cloud agents and their environments/secrets. Trigger ONLY when the user is working with Warp's Oz cloud agent platform specifically. Do NOT trigger for: Claude Code agents, Anthropic Managed Agents, GitHub Actions, generic 'cloud agents', other agent platforms, or any non-Warp scheduling/automation. If 'cloud agent' is mentioned without naming Warp/Oz, ask before invoking.

[Warp terminal app ONLY] Fetch GitHub PR review comments for the current branch and display them via Warp's `insert_code_review_comments` tool. Trigger ONLY inside the Warp terminal where the `insert_code_review_comments` tool is available. Do NOT trigger in Claude Code, Cursor, or any other environment — `insert_code_review_comments` does not exist there, so this skill cannot complete. For generic PR-comment fetching outside Warp, use `gh pr view` / `gh api` directly instead of this skill.

[Warp terminal app ONLY] Canonical reference for Warp tab config TOML schema, validation rules, and examples (Warp's terminal-tab layout files in ~/.warp/tab_configs/). Trigger ONLY when working with Warp tab configs specifically, or when the `create-tab-config` / `update-tab-config` skills need this shared schema reference. Do NOT trigger for tmux, iTerm, VS Code, browser tabs, or any non-Warp 'tab' concept.

[Warp terminal app ONLY] Update existing Warp tab config TOML files (Warp's terminal-tab layout files in ~/.warp/tab_configs/) from natural-language edit requests. Trigger ONLY when modifying a Warp tab config specifically, or when editing a Warp tab config file already open. Do NOT trigger for tmux configs, iTerm/Terminal.app profiles, VS Code/JetBrains workspace layouts, browser tabs, or any other 'tab' or 'layout' concept.

Download a video from a LinkedIn post URL using yt-dlp at the highest quality possible, rename it concisely, and save to ~/Downloads/videos/ with a timestamped prefix.

Rename files to follow a consistent naming convention. Use this skill whenever the user wants to rename files to be lowercase with underscores replacing spaces, hyphens as delimiters between concepts, no leading numbers, and no spaces. Examples of the target format: todo-name_of_spec-version_of_spec.md, project-component_name-feature_description.py. Always show a preview of the rename mapping before executing changes.

Parse a VS Code fork's live settings and keybindings, then propagate changes into the shared generic config and editor-specific overrides in the dotfiles repo.