convert-github-issue-to-discussion

Convert GitHub issues to discussions using agent-browser. Use when asked to convert, move, or change an issue to a discussion. Requires agent-browser installed and user to log in via headed browser.

Quality

71%

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

Fix and improve this skill with Tessl

tessl review fix ./config/claude/skills/convert-github-issue-to-discussion/SKILL.md

Quality

Content

61%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 skill provides concrete, executable browser-automation steps in a clear sequence, but its key weakness is the explicit omission of verification for an irreversible operation, plus redundancy and an incomplete trailing section.

Suggestions

Add an explicit verification step after conversion (e.g., snapshot/check that the URL redirected to discussions and the issue no longer appears as an issue) rather than telling the user verification is unnecessary.

Remove the Quick Reference section or fold it into the workflow, since it duplicates the numbered steps; alternatively keep only the workflow and trim the duplicate commands.

Complete or remove the truncated "Looking for issues" section, which currently ends mid-sentence at "use gh".

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with brief command-focused steps, but the Quick Reference section substantially duplicates the numbered workflow and the Category Guidelines repeat inline, pulling it down from the efficient score-4 anchor.	3 / 5
Actionability	Concrete agent-browser commands are given throughout and the Quick Reference uses concrete refs (@e137, @e2, @e9), but the main workflow relies on placeholders (@<ref>, @<combobox-ref>) preventing fully copy-paste-ready execution expected at score 5.	4 / 5
Workflow Clarity	Steps are clearly sequenced, but converting an issue to a discussion is an irreversible operation and Step 8 explicitly omits verification ("You don't need to verify, you are done now."), so the destructive-operation cap at 3 applies despite the otherwise clear sequence.	3 / 5
Progressive Disclosure	Content is well-organized into clear sections with no external files needed, but the trailing "Looking for issues" section is cut off mid-sentence and some content is duplicated, keeping it below the cleanly organized score-5 anchor.	4 / 5
	Total	14 / 20 Passed

Description

82%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 well-constructed with a clear niche, explicit trigger guidance, and natural synonyms. Its main limitation is that it names only one concrete action rather than a comprehensive set.

Dimension	Reasoning	Score
Specificity	Names the domain and one concrete action ("Convert GitHub issues to discussions") but does not enumerate multiple specific actions, so it matches the anchor naming a domain with 1-2 actions rather than the comprehensive coverage of score 4-5.	3 / 5
Completeness	It explicitly states what it does ("Convert GitHub issues to discussions using agent-browser") and when to use it ("Use when asked to convert, move, or change an issue to a discussion") with concrete trigger phrases, matching the score-5 anchor.	5 / 5
Trigger Term Quality	"Use when asked to convert, move, or change an issue to a discussion" provides good natural keyword coverage with synonyms (convert/move/change), falling just short of fully comprehensive coverage expected at score 5.	4 / 5
Distinctiveness Conflict Risk	Converting GitHub issues to discussions via agent-browser is a clear niche with distinct triggers and minimal overlap risk with other skills, matching the score-5 anchor.	5 / 5
	Total	17 / 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: freekmurze/dotfiles
Path: config/claude/skills/convert-github-issue-to-discussion/SKILL.md
Commit: a7899fe

Reviewed: 3 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.