CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

migrate-issues

migrate GitHub issues from one repository to another

Quality

72%

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

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/migrate-issues/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

76%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 an exceptionally concrete, actionable instruction set with copy-paste templates, explicit correct/wrong examples, and a worked transformation — actionability is essentially maxed for an instruction-only skill. Its weaknesses are workflow-level: no validate/fix/retry feedback loop for a batch, destructive operation, no post-migration verification, and small coherence defects (duplicate section numbering, an internal contradiction about closing originals).

Suggestions

Add post-migration verification with an error-recovery loop, e.g. 'After creating each issue, verify mentions are backticked and references resolve; if any ping or mislink, edit the issue/comment immediately and re-verify.'

Fix the duplicate '### 5.' numbering and reconcile the contradiction between 'Close the original issue as not_planned' and the checklist item 'Decide whether to close original issues after migration' — either make closing conditional in both places or mandatory in both.

Trim redundancy by folding the checklist's verification items into the requirements they mirror, or convert the checklist into a run-through sequence so it adds ordering value rather than repetition.

DimensionReasoningScore

Conciseness

The body is directive throughout — exact templates, correct/incorrect contrasts, and a worked example — with no explanations of concepts Claude already knows. Minor over-explanation exists: the 'Checklist Before Migration' repeats requirements 3-4 ('Verify all `@mentions` are wrapped in backticks', 'Verify all `#NUMBER` references are converted to full URLs') and the Example Transformation largely restates those same rules. Fits anchor 4 ('efficient; minor instances that could be trimmed') rather than anchor 5.

4 / 5

Actionability

Fully copy-paste-ready guidance: exact markdown templates ('_Transferred from {SOURCE_REPO}#{ORIGINAL_ISSUE_NUMBER}_', '_`@{COMMENT_AUTHOR}` commented:_'), explicit correct/incorrect examples ('✅ Correct: `https://github.com/microsoft/vscode-copilot/issues/12345`', '❌ Wrong: `#12345`'), a complete worked before/after transformation, and a concrete close state ('not_planned'). Per the rubric's instruction-skill note, the absence of gh CLI commands is not penalized since the transformation guidance is fully executable.

5 / 5

Workflow Clarity

This is a batch and destructive operation ('All matching issues will be migrated', 'Close the original issue as not_planned'), and while a pre-flight checklist exists, there is no feedback loop (no validate-after-creation, fix, and retry guidance) and no post-migration verification — the rubric caps batch/destructive skills without feedback loops at 3. Coherence is also weakened by duplicate '### 5.' section numbering and a contradiction between 'Close the original issue as not_planned' (requirement) and the checklist's 'Decide whether to close original issues after migration'.

3 / 5

Progressive Disclosure

No bundle files exist and the ~170-line body is well organized into clearly headed sections (Input Methods, Task, Requirements, Example Transformation, Checklist) with no nested or buried references. It sits below anchor 5 because the skill exceeds 50 lines and content like the Example Transformation or the query-filter table could plausibly live in a reference file, and the duplicate '### 5.' numbering is a minor organization gap.

4 / 5

Total

16

/

20

Passed

Description

53%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 and clearly states what the skill does with an unambiguous niche, but it is bare-bones: no trigger guidance ('Use when...'), no synonyms or natural variations, and no enumeration of the concrete sub-actions the body actually performs. It reads as a minimal title rather than a discovery-optimized description.

Suggestions

Add an explicit 'when' clause, e.g. 'Use when the user asks to move, transfer, or copy GitHub issues to another repository.'

Enumerate 2-3 concrete sub-actions to raise specificity, e.g. 'migrate GitHub issues (body, comments, labels) between repositories, converting mentions and cross-references so nothing pings users or links to the wrong repo.'

Include natural synonyms users would say — 'move', 'transfer', 'copy issues' — to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

"migrate GitHub issues from one repository to another" names the domain and a single concrete action with clear source/target scope, but does not list the sub-actions the skill performs (comment migration, mention escaping, link reformatting, closing originals). Not anchor 2 because 'from one repository to another' is more concrete than the generic 'Processes PDF files'; not anchor 4 because coverage of capabilities is not 'several specific actions'.

3 / 5

Completeness

The description has a clear 'what' but contains no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Anchor 4 requires both 'what' and an explicit 'when', which is entirely absent here.

3 / 5

Trigger Term Quality

Natural keywords 'migrate', 'GitHub issues', and 'repository' are present and match what a user would say, but common variations and synonyms ('move', 'transfer', 'copy issues', 'issue transfer') are missing. Fits anchor 3 ('some relevant keywords but missing common variations') rather than anchor 4's fuller coverage.

3 / 5

Distinctiveness Conflict Risk

"migrate GitHub issues from one repository to another" carves a clear niche (cross-repo issue migration) that is unlikely to trigger for the wrong skill. It falls short of anchor 5's fully-specified what-plus-when example, but is clearly above anchor 3's overlap-prone phrasing.

4 / 5

Total

13

/

20

Passed

Validation

100%

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

microsoft/vscode

Path

.github/skills/migrate-issues/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.