Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →remotion-dev/issue
Create or update GitHub issues with correct Remotion naming and safe multiline Markdown handling
Passed 4 of 10 test cases with the skill, and 2 of 10 without it.
and 7 more in the full report
5 fixed4 passed either way14 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
I need to post a detailed multi-line comment on Remotion issue #452 with new flame graph profiling output and benchmark tables. Provide the command to post this comment.
| Checked | Without skill | With skill |
|---|---|---|
| Writes the comment body to a Markdown file. | Missed | Passed |
| Passes the file path to gh issue comment using --body-file. | Passed | Passed |
The instructions your model reads when the skill loads.
Write a concise title that preserves the user's framing. An issue may describe a problem or give a directive; do not turn a problem into a prescribed solution unless the user supplied or explicitly requested one.
Prefix package-specific issues with the package name:
`@remotion/package`: Issue description
For broader areas, use the corresponding prefix:
Docs: Issue description
Studio: Issue description
Build: Issue description
CI: Issue description
Repo: Issue description
Avoid vague titles such as Bug, Fix issue, or Examples follow-up.
Never pass multiline Markdown inline through shell arguments. Write issue bodies and multiline comments to a temporary Markdown file, preferably with the write tool, and pass it with --body-file.
After creating or editing an issue, verify its title and body:
gh issue view <number> --json title,body
Confirm that the content is correct and multiline Markdown contains real newlines rather than literal \n sequences.
When the user provides an image or video, upload it with --attach on gh issue create, edit, or comment:
gh issue edit <number> --attach '/tmp/screenshot.png#Description of the screenshot'
test cases passed, vs 2 / 10 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.