Utilizar al reproducir un error de interfaz de usuario o verificar una corrección controlando una ventana real de VS Code de principio a fin y capturando evidencia. Escribe un archivo de escenario, lo ejecuta contra una versión de desarrollo o Insiders instalado, y produce un video con subtítulos, capturas de pantalla por paso, un rastro de Playwright y un informe HTML para adjuntar a un problema o solicitud de extracción.
Este skill está diseñado para ayudar a desarrolladores y agentes de IA a reproducir errores de interfaz de usuario en VS Code, verificando correcciones mediante la ejecución automatizada de escenarios en una ventana real de VS Code. Es especialmente útil al reportar problemas o revisar solicitudes de extracción, ya que genera evidencia visual completa: un video con subtítulos sincronizados, capturas de pantalla detalladas por cada paso, un rastro de Playwright para depuración, y un informe HTML resumido. Funciona escribiendo un archivo de escenario (`scenario.json`) que define pasos como abrir archivos, ejecutar comandos, escribir texto o tomar decisiones en diálogos. Luego, el skill ejecuta este escenario contra una compilación de desarrollo o la versión Insiders de VS Code, esperando que la ventana esté abierta y tenga la extensión 'VSCode E2E Test Helper' instalada. El resultado se guarda en una carpeta con marca de tiempo, lista para adjuntar a un issue o PR. Es compatible con todo el ecosistema VS Code y mejora la comunicación entre desarrolladores al aportar evidencia concreta y reproducible.
npx skills add microsoft/vscodeUtilizar al reproducir un error de interfaz de usuario o verificar una corrección controlando una ventana real de VS Code de principio a fin y capturando evidencia. Escribe un archivo de escenario, lo ejecuta contra una versión de desarrollo o Insiders instalado, y produce un video con subtítulos, capturas de pantalla por paso, un rastro de Playwright y un informe HTML para adjuntar a un problema o solicitud de extracción.
This repo contains 11 individual skills — each has its own dedicated page.
Primary accessibility skill for VS Code. REQUIRED for new feature and contribution work, and also applies to updates of existing UI. Covers accessibility help dialogs, accessible views, verbosity settings, signals, ARIA announcements, keyboard navigation, and ARIA labels/roles.
Agents workbench layout — covers the fixed layout structure, grid configuration, part visibility, editor modal, titlebar, sidebar footer, and implementation requirements. Use when implementing features or fixing issues in the Agents workbench layout.
Identify all files a specific author contributed to on a branch vs its upstream, tracing code through renames. Use when asked who edited what, what code an author contributed, or to audit authorship before a merge. This skill should be run as a subagent — it performs many git operations and returns a concise table.
Use when validating Azure DevOps pipeline changes for the VS Code build. Covers queueing builds, checking build status, viewing logs, and iterating on pipeline YAML changes without waiting for full CI runs.
Guidelines for fixing unhandled errors from the VS Code error telemetry dashboard. Use when investigating error-telemetry issues with stack traces, error messages, and hit/user counts. Covers tracing data flow through call stacks, identifying producers of invalid data vs. consumers that crash, enriching error messages for telemetry diagnosis, and avoiding common anti-patterns like silently swallowing errors.
Use when making code changes to ensure they pass VS Code's hygiene checks. Covers the pre-commit hook, unicode restrictions, string quoting rules, copyright headers, indentation, formatting, ESLint, and stylelint. Run the hygiene check before declaring work complete.
Audit code for memory leaks and disposable issues. Use when reviewing event listeners, DOM handlers, lifecycle callbacks, or fixing leak reports. Covers addDisposableListener, Event.once, MutableDisposable, DisposableStore, and onWillDispose patterns.
Agents window architecture — covers the agents-first app, layering, folder structure, chat widget, menus, contributions, entry points, and development guidelines. Use when implementing features or fixing issues in the Agents window.
Ensure renamed built-in tool references preserve backward compatibility. Use when renaming a toolReferenceName, tool set referenceName, or any tool identifier. Run on ANY change to tool registration code. Covers legacyToolReferenceFullNames for tools and legacyFullNames for tool sets.
Download screenshot baselines from the latest CI run and commit them. Use when asked to update, accept, or refresh component screenshot baselines from CI, or after the screenshot-test GitHub Action reports differences. This skill should be run as a subagent.
Use when reproducing a UI bug or verifying a fix by driving a real VS Code window end to end and capturing evidence. Writes a scenario file, runs it against a dev build or installed Insiders, and produces a captioned video, per-step screenshots, a Playwright trace, and an HTML report to attach to an issue or pull request.
Extract frames or short clips from videos using ffmpeg.
Summarize or transcribe URLs, YouTube/videos, podcasts, articles, transcripts, PDFs, and local files.
Use when testing, fixing, or extending the OpenClaw Control UI GUI with Vitest + Playwright end-to-end checks, mocked Gateway WebSocket flows, mocked dashboard runs, screenshots/videos, or agent-verifiable browser proof.
Obra superpowers agent skills.
See, Understand, Act on video and audio. See- ingest from local files, URLs, RTSP/live feeds, or live record desktop; return realtime context and playable stream links. Understand- extract frames, build visual/semantic/temporal indexes, and search moments with timestamps and auto-clips. Act- transcode and normalize (codec, fps, resolution, aspect ratio), perform timeline edits (subtitles, text/image overlays, branding, audio overlays, dubbing, translation), generate media assets (image, audio...
End-to-end marketing campaign planning and execution. Covers audience research, positioning, campaign angle definition, landing page copy, email sequences, social posts, ad copy, short-form video scripts, and content calendars. Use as the orchestration layer for multi-channel product launches. Use when planning or executing a multi-channel product launch, or producing landing page, email, social, or ad copy.