Install any skill in seconds. Free to start, no credit card required.
Get Started Free →remotion-dev/flake
Track Remotion CI flakes in issue
Passed 11 of 16 test cases with the skill, and 9 of 16 without it.
and 4 more in the full report
5 fixed10 passed either way5 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
After updating tracker issue #8375 on remotion-dev/remotion with a new flaky failure signature, what command should be executed to verify that the table formatting was preserved correctly?
| Checked | Without skill | With skill |
|---|---|---|
| The response uses gh issue view 8375 to fetch the issue body. | Passed | Passed |
| The response uses the jq parser flag to output raw body content. | Missed | Passed |
The instructions your model reads when the skill loads.
Use this skill when a Remotion CI check fails and looks flaky, or when asked to run /flake.
Tracker issue: https://github.com/remotion-dev/remotion/issues/8375
Record flaky CI failures in issue #8375 and get the affected suite running again.
For every confirmed or likely flake:
Count.1, workflow/job, first-seen date, and evidence URL.Prefer gh because the GitHub app may not expose all Actions logs or write permissions.
If the user gave a PR:
gh pr view <pr-number> --repo remotion-dev/remotion --json number,title,headRefName,statusCheckRollup
gh pr checks <pr-number> --repo remotion-dev/remotion --watch=false
If the user gave a workflow run or job URL:
gh run view <run-id> --repo remotion-dev/remotion --json databaseId,attempt,displayTitle,event,headBranch,headSha,status,conclusion,workflowName,createdAt,updatedAt,url,jobs
gh api repos/remotion-dev/remotion/actions/jobs/<job-id>/logs
If there is no PR context, inspect recent open PRs and recent failed runs:
gh pr list --repo remotion-dev/remotion --state open --limit 30 --json number,title,headRefName,statusCheckRollup
test cases passed, vs 9 / 16 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.