flake

Track Remotion CI flakes in issue

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a lean, highly actionable runbook with executable gh commands, a clear sequenced workflow, and an explicit edit-verification loop, with no unnecessary padding or missing bundle files.

Dimension	Reasoning	Score
Conciseness	The body is lean and command-driven with no re-explanation of concepts Claude knows; each section earns its tokens, e.g. 'Prefer `gh` because the GitHub app may not expose all Actions logs or write permissions.' is a justified one-liner, not padding.	3 / 3
Actionability	Concrete, copy-paste-ready `gh` commands with real flags and JSON field lists (e.g. 'gh pr view <pr-number> --json number,title,headRefName,statusCheckRollup') plus a specified tracker table format and signature examples.	3 / 3
Workflow Clarity	The Goal section sequences the multi-step process and 'Update The Tracker' includes an explicit 'Verify after editing' feedback loop, so the destructive shared-issue edit is validated rather than capped at 2.	3 / 3
Progressive Disclosure	No bundle files exist and none are warranted; the single self-contained runbook is organized into clearly navigable sections (Goal, Find The Failure, Classify, Signature Rules, Update The Tracker, Rerun, Report Back), satisfying the well-organized-sections exception.	3 / 3
	Total	12 / 12 Passed

Description

82%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, distinctive, and uses natural trigger terms, but it omits an explicit 'Use when…' trigger clause, so completeness is capped at 2.

Suggestions

Add an explicit 'Use when…' clause, e.g. 'Use when a Remotion CI check fails and looks flaky, or when asked to run /flake.'

Mirror the body's trigger phrasing ('CI check fails and looks flaky', '/flake') into the description so the trigger is explicit, not implied.

Consider naming the workflow ('Install and Test') in the description to further sharpen distinctiveness.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Track Remotion CI flakes in issue #8375', 'increment repeated signatures', 'discover failed PR checks when no PR is given', and 'rerun flaky GitHub Actions jobs' — matching the score-3 anchor for several specific concrete actions.	3 / 3
Completeness	It clearly states what the skill does but lacks a 'Use when…' clause or equivalent explicit trigger guidance, leaving the 'when' only implied, which the guidelines cap at 2; not 3 because the trigger is not explicit, and not 1 because the 'what' is comprehensive.	2 / 3
Trigger Term Quality	Natural terms a user would actually say — 'CI flakes', 'PR checks', 'GitHub Actions jobs', 'rerun' — give good coverage; it is not merely technical jargon, so it is not the level-2 'missing common variations' anchor.	3 / 3
Distinctiveness Conflict Risk	Pinned to Remotion CI, issue #8375, and GitHub Actions reruns — a clear niche unlikely to trigger for the wrong skill.	3 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: remotion-dev/remotion
Path: .agents/skills/flake/SKILL.md
Commit: 1b58387

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

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.