Add Webcodecs Bug Agent Skill
Add a browser WebCodecs bug to the Remotion Mediabunny WebCodecs bugs docs page. Use when given a Chromium, WebKit, or Firefox issue URL that should be tracked in packages/docs/docs/mediabunny/webcodecs-bugs.mdx, especially when needing to look up the issue title, filing date, reporter, and resolution state before editing the MDX table.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/remotion-dev/remotion --skill add-webcodecs-bugThe instruction itself
3 sections, as written by the authorAdd WebCodecs Bug
Workflow
- Read
packages/docs/docs/mediabunny/webcodecs-bugs.mdxto understand the current table format. - Open the provided issue URL with the
browser:control-in-app-browserskill. - On the issue page, verify:
- issue title
- created or filed date
- reporter or filed-by identity
- current status and resolution state
- Map the browser tracker to the table fields:
- Product: Chromium issues are
Chrome, WebKit Bugzilla issues areSafari, Mozilla Bugzilla issues areFirefox. - Filed by: use the known handle from the task when the tracker only exposes a redacted email. Known reporter mappings:
musica-viva.deordp@[email protected]→@Vanilagy- Fixed?: use
Yesonly for fixed or verified-fixed issues,Nofor open/new/assigned/unresolved issues, andWon't fixfor explicitly rejected or wontfix resolutions. - Add one Markdown table row to
packages/docs/docs/mediabunny/webcodecs-bugs.mdx.
Preserve the existing table columns and wording. Do not add a date column unless the docs file already has one or the user explicitly asks for it.
Verification
After editing, inspect the diff and confirm the row has the right URL, product, filed-by value, and fixed state.
Other skills for the same job
different authors, same section of the catalogue
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementing any feature or bugfix, before writing implementation code
Use when you have a spec or requirements for a multi-step task, before touching code
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
| Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
Official Opentrons Protocol API for OT-2 and Flex robots. Use when writing protocols specifically for Opentrons hardware with full access to Protocol API v2 features. Best for production Opentrons protocols, official API compatibility. For multi-vendor automation or broader equipment control use pylabrobot.
How to use it
Take remotion-dev/add-webcodecs-bug from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.