CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

issue

Create, edit, or comment on Remotion GitHub issues.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 content is an exemplary lean, instruction-only skill: specific commands, flag semantics Claude would not know, explicit verification steps, and clean sectioning. The only minor gap is the absence of a complete gh issue create/--body-file command example for the most common use case.

DimensionReasoningScore

Conciseness

The body is lean and dense with operational detail — title prefix templates, the --body-file pattern, flag semantics for attachments — with zero padding or explanation of concepts Claude already knows. Every token earns its place.

5 / 5

Actionability

Concrete, copy-paste-ready commands are given for verification (gh issue view --json title,body) and attachment (gh issue edit --attach '...#alt text'), plus explicit --body-file guidance. It is not a 5 because no complete command example is shown for the most common cases, gh issue create and gh issue comment.

4 / 5

Workflow Clarity

The workflow includes an explicit validation checkpoint after create/edit (verify title and body, confirm real newlines vs literal \n) and an error-recovery loop for partial attachment failures ("inspect the issue before retrying to avoid duplicates"), matching the top anchor.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references, and its four well-organized sections (Titles, Markdown bodies and comments, Attachments, Relationships) plus a clearly signaled one-level pointer to the issue-management skill match the simple-skill exception for a top score.

5 / 5

Total

19

/

20

Passed

Description

66%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 concise, specific, and clearly scoped to Remotion GitHub issues, but it entirely lacks a "Use when..." trigger clause, which caps completeness and weakens discoverability. Adding explicit trigger phrasing would raise it substantially.

Suggestions

Add a trigger clause, e.g. "Use when the user asks to file, update, or comment on issues in the Remotion GitHub repository."

Include natural trigger synonyms such as "file an issue", "open a bug report", or "respond to an issue" to broaden keyword coverage.

Mention attachment uploads or title conventions briefly if they are core capabilities users would request by name.

DimensionReasoningScore

Specificity

"Create, edit, or comment on Remotion GitHub issues" lists three concrete actions naming the domain, matching the 'several specific actions; minor gaps' anchor. It is not a 5 because capabilities the body actually covers (attachments, titles, issue relationships) are absent from the description.

4 / 5

Completeness

The "what" is clear (create, edit, comment on issues), but there is no "Use when..." clause or equivalent explicit trigger guidance — the "when" is only weakly implied by the domain itself, which caps this at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Natural terms users would say are present ("GitHub", "issues", "comment", "Remotion"), giving good keyword coverage. It falls short of 5 because common variations like "file an issue", "open a bug report", or "triage" are missing.

4 / 5

Distinctiveness Conflict Risk

"Remotion GitHub issues" carves a distinct niche unlikely to trigger the wrong skill. It is not 5 because minor overlap risk remains with closely related skills such as the sibling issue-management skill or generic GitHub/PR skills.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository

remotion-dev/remotion

Path

.agents/skills/issue/SKILL.md

Reviewed

Table of Contents

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.