CtrlK
BlogDocsLog inGet started
Tessl Logo

issue

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

65

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/issue/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%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 exemplar of a lean, executable instruction skill: concrete gh commands, explicit verification steps, a feedback loop, and a final checklist, all within a well-organized single file.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, with no padding or explanation of GitHub/Markdown basics; every section earns its place.

5 / 5

Actionability

Commands are fully executable and copy-paste ready (`gh issue create --body-file`, `gh issue view --json body --jq .body`), with concrete temp-file patterns covering the common cases.

5 / 5

Workflow Clarity

Create/edit flows are numbered with an explicit validation checkpoint (view the rendered body and confirm real newlines), a feedback loop on literal `\n`, and a final verification checklist.

5 / 5

Progressive Disclosure

The skill is short and single-purpose with well-organized section headers and no need for external references, qualifying for the simple-skill exception of a 5 on progressive disclosure.

5 / 5

Total

20

/

20

Passed

Description

58%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 conveys a clear, specific capability set tied to a distinct niche, but it omits any 'Use when...' trigger guidance, which caps completeness and limits trigger-term coverage.

Suggestions

Add an explicit 'Use when...' clause naming concrete user triggers, e.g. 'Use when creating, editing, or commenting on GitHub issues for Remotion packages.'

Include common synonyms/variations users might say (e.g. 'GitHub issues', 'bug report', 'comment on an issue') to broaden trigger-term coverage.

Consider naming the package-scope prefixes (Docs/Studio/Build/CI/Repo) to sharpen distinctiveness from a generic issue skill.

DimensionReasoningScore

Specificity

Names the GitHub-issue domain plus three concrete actions (create/update issues, Remotion naming, safe multiline Markdown handling), fitting 'several specific actions; minor gaps' rather than the 1-2 actions of a score 3.

4 / 5

Completeness

The 'what' is clear but there is no 'Use when...' clause or explicit trigger guidance, and the rubric caps completeness at 3 when that clause is missing.

3 / 5

Trigger Term Quality

Includes natural terms like 'GitHub issues' and 'Markdown' but lacks synonyms, file extensions, or varied user phrasings, matching 'some relevant keywords but missing common variations.'

3 / 5

Distinctiveness Conflict Risk

The Remotion-naming and safe-multiline-Markdown scope gives it a clear niche with only minor overlap risk against a generic issue/PR skill.

4 / 5

Total

14

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 suspicious

Warning

Total

15

/

16

Passed

Repository
remotion-dev/remotion
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.