Use ao reproduzir um bug de UI ou verificar uma correção, dirigindo uma janela real do VS Code de ponta a ponta e capturando evidências. Escreve um arquivo de cenário, executa-o em uma build de desenvolvimento ou no Insiders instalado e produz um vídeo com legendas, capturas de tela por etapa, um trace do Playwright e um relatório HTML para anexar a um problema ou pull request.
Esta skill automatiza a validação de bugs de interface do usuário no VS Code, gerando evidências visuais detalhadas para reproduzir um problema ou verificar uma correção. Ela cria um arquivo de cenário que descreve os passos manuais, executa esse cenário em uma janela real do VS Code (seja usando uma build de desenvolvimento ou o VS Code Insiders instalado) e coleta evidências completas. O resultado inclui um vídeo com legendas de cada ação, capturas de tela individuais por etapa, um trace do Playwright para análise detalhada da interação e um relatório HTML consolidado. Essa skill é particularmente útil para desenvolvedores que precisam demonstrar bugs complexos de UI ou validar correções de forma reprodutível, fornecendo material rico para anexar a issues ou pull requests, eliminando a necessidade de gravações manuais ou descrições ambíguas. Suporta qualquer sistema operacional onde o VS Code e o Playwright possam ser executados.
npx skills add https://github.com/microsoft/vscode/tree/main/.github/skills/validate-ui-scenarioUse ao reproduzir um bug de UI ou verificar uma correção, dirigindo uma janela real do VS Code de ponta a ponta e capturando evidências. Escreve um arquivo de cenário, executa-o em uma build de desenvolvimento ou no Insiders instalado e produz um vídeo com legendas, capturas de tela por etapa, um trace do Playwright e um relatório HTML para anexar a um problema ou pull request.
This repo contains 10 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.
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.