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.
80
100%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
packages/docs/docs/mediabunny/webcodecs-bugs.mdx to understand the current table format.browser:control-in-app-browser skill.Chrome, WebKit Bugzilla issues are Safari, Mozilla Bugzilla issues are Firefox.musica-viva.de or dp@...@musica-viva.de → @VanilagyYes only for fixed or verified-fixed issues, No for open/new/assigned/unresolved issues, and Won't fix for explicitly rejected or wontfix resolutions.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.
After editing, inspect the diff and confirm the row has the right URL, product, filed-by value, and fixed state.
1b58387
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.