find-unplanned-issues

Audit and clean the Remotion GitHub masterplan hierarchy. Use when finding open issues that lack a masterplan ancestor, identifying orphaned issues that need a parent, or recursively removing closed issues from the masterplan rooted at issue #9081.

Quality

93%

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

93%Weight 40%Scale 1-5

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

The body is lean, executable, and safety-conscious, with clear command examples and explicit verification guidance for a destructive operation. The only gap is an explicit error-recovery feedback loop for the prune workflow.

Suggestions

Add an explicit feedback loop for the prune operation: state what to do when a relationship verification fails (fix the relationship and re-verify before continuing) so the validate→fix→retry cycle is spelled out.

Clarify the post-apply verification as a discrete step with its own command or checklist rather than a clause within the apply instructions.

Dimension	Reasoning	Score
Conciseness	Lean body that assumes Claude's competence; every line is operational detail (flags, behavior distinctions, safety warnings) rather than explanation of concepts Claude already knows.	5 / 5
Actionability	Provides copy-paste-ready `bun` commands covering the common cases (default, --repo, --json, --check, --root, --apply) with complete executable invocations rather than pseudocode.	5 / 5
Workflow Clarity	Clear sequenced workflow with explicit validation ('verify every relationship after changing it', dry-run default, deepest-first processing, move open children first), but lacks an explicit validate→fix→re-verify feedback loop for the destructive prune operation.	4 / 5
Progressive Disclosure	Well-organized into two clear sections with one-level-deep references to real bundled scripts (find-unplanned-issues.ts, prune-closed-masterplan-issues.ts) signaled as the primary commands; no nested references.	5 / 5
	Total	19 / 20 Passed

Description

92%Weight 40%Scale 1-5

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 third-person, concise, and clearly states both the capability and concrete trigger conditions with multiple specific actions. It is highly specific and distinctive, with only minor room to add synonym trigger phrasings.

Dimension	Reasoning	Score
Specificity	Names the domain ('Remotion GitHub masterplan hierarchy') and lists multiple concrete actions — 'finding open issues that lack a masterplan ancestor', 'identifying orphaned issues that need a parent', 'recursively removing closed issues' — covering both audit and clean comprehensively.	5 / 5
Completeness	Explicitly answers both what ('Audit and clean the Remotion GitHub masterplan hierarchy') and when ('Use when finding open issues that lack a masterplan ancestor, identifying orphaned issues that need a parent, or recursively removing closed issues from the masterplan rooted at issue #9081').	5 / 5
Trigger Term Quality	Good natural-phrase coverage ('finding open issues that lack a masterplan ancestor', 'orphaned issues that need a parent', 'removing closed issues from the masterplan'), but no synonyms or variant phrasings beyond the single formulation per action.	4 / 5
Distinctiveness Conflict Risk	Highly specific niche tied to the Remotion masterplan rooted at issue #9081 with distinct triggers, making conflict with other skills minimal.	5 / 5
	Total	19 / 20 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/find-unplanned-issues/SKILL.md
Commit: eca4063

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.