issue

Create or update GitHub issues with correct Remotion naming and safe multiline Markdown handling

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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 reference: concrete `gh` commands, numbered workflows with explicit validation, and a final checklist, with appropriate delegation to the issue-management skill. It avoids explaining concepts Claude already knows and keeps all core guidance appropriately inline.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it never explains what GitHub or Markdown is, and each section earns its tokens with concrete guidance; the only explanatory line (literal \n risk) directly justifies a non-obvious rule.	3 / 3
Actionability	It provides fully executable, copy-paste-ready `gh` commands with real flags (`gh issue create ... --body-file`, `gh issue edit ... --body-file`, `gh issue view ... --json body --jq .body`) and concrete title-format examples rather than vague direction.	3 / 3
Workflow Clarity	Creating and editing workflows are numbered with explicit validation checkpoints (view the rendered body, confirm real newlines vs literal \n) and capped by a final verification checklist, satisfying the feedback-loop and checkpoint anchor.	3 / 3
Progressive Disclosure	The single SKILL.md is well-organized into clear sections and delegates relationship handling to the sibling issue-management skill via a one-level-deep link, with no nested or dangling references.	3 / 3
	Total	12 / 12 Passed

Description

67%

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 concise and concrete with a clear Remotion-specific niche, but it lacks an explicit "Use when" trigger clause and only partial natural-term coverage. These gaps cap completeness and trigger-term quality at the midpoint.

Suggestions

Add an explicit trigger clause such as "Use when creating, editing, or commenting on GitHub issues for the Remotion project" to lift completeness to the top anchor.

Broaden trigger-term coverage with natural variants users would say (e.g. "bug report", "feature request", "file an issue", "issue comment").

Clarify the boundary with the issue-management skill in the description itself (e.g. "for issue relationships, use issue-management") to further reduce overlap risk.

Dimension	Reasoning	Score
Specificity	"Create or update GitHub issues with correct Remotion naming and safe multiline Markdown handling" lists multiple concrete capabilities (create/update issues, Remotion naming, multiline Markdown handling) rather than vague language, matching the multi-action anchor.	3 / 3
Completeness	The description clearly answers what the skill does, but there is no "Use when..." clause or equivalent explicit trigger guidance; per the judging guidelines a missing trigger clause caps completeness at 2.	2 / 3
Trigger Term Quality	It includes natural terms like "GitHub issues" and "Markdown" but omits common variations a user might say (e.g. bug report, feature request, file an issue) and provides no trigger context, fitting the "some relevant keywords but missing common variations" anchor.	2 / 3
Distinctiveness Conflict Risk	The Remotion-specific naming convention and multiline Markdown handling carve a clear niche, and relationship work is explicitly delegated to the issue-management skill, making conflict with sibling skills unlikely.	3 / 3
	Total	10 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 2 suspicious	Warning

	Total	15 / 16 Passed

Repository: remotion-dev/remotion
Path: .agents/skills/issue/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.