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.
82
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./config/claude/skills/convert-github-issue-to-discussion/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted description that clearly defines a narrow task with explicit trigger guidance and natural keywords. Its main weakness is that it describes only a single action, which limits the specificity score, but for a single-purpose skill this is appropriate. The inclusion of prerequisites (agent-browser, headed browser login) adds useful context for skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the specific action ('Convert GitHub issues to discussions') and the tool ('agent-browser'), but only describes a single action rather than listing multiple concrete capabilities. | 2 / 3 |
Completeness | Clearly answers both 'what' (convert GitHub issues to discussions using agent-browser) and 'when' (explicitly states 'Use when asked to convert, move, or change an issue to a discussion'). Also includes prerequisite information about agent-browser and login. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'convert', 'move', 'change', 'issue', 'discussion', 'GitHub'. These cover the common variations a user would naturally say when requesting this task. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche: converting GitHub issues to discussions via agent-browser. This is unlikely to conflict with other skills due to the narrow, well-defined scope and distinct trigger terms. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides clear, actionable browser automation commands for converting GitHub issues to discussions, with good concrete examples of expected snapshot output. Its main weaknesses are the duplicated content between the workflow and quick reference sections, and the lack of error handling or validation steps for what is an irreversible operation. The explicit decision to skip verification in Step 8 is a notable gap.
Suggestions
Remove or significantly condense the Quick Reference section since it duplicates the workflow steps—or replace the detailed workflow with just the quick reference if brevity is preferred.
Add error handling guidance: what to do if 'Convert to discussion' button is not found (e.g., issue already converted, insufficient permissions), and verify the URL redirects to a discussion page after conversion.
Remove Step 8 entirely since it says 'you don't need to verify'—or replace it with an actual verification step like checking the resulting URL contains '/discussions/'.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but has some redundancy—the detailed step-by-step workflow and the quick reference section largely duplicate each other. Step 8 ('Verify Conversion') says 'you don't need to verify, you are done now' which is a wasted step. Some explanatory text like 'The --headed flag shows the browser window so the user can log in' is mildly unnecessary. | 2 / 3 |
Actionability | Every step includes concrete, executable bash commands with the exact agent-browser CLI syntax. The snapshot output examples show what to look for (button refs, combobox refs), making it copy-paste ready with only placeholder substitution needed. | 3 / 3 |
Workflow Clarity | The multi-step process is clearly sequenced with numbered steps and includes a login check. However, there are no validation checkpoints or error recovery steps—what if the 'Convert to discussion' button isn't found? What if the click fails? Step 8 explicitly skips verification, which is a gap for a destructive/irreversible operation. | 2 / 3 |
Progressive Disclosure | The content is reasonably structured with sections (workflow, quick reference, category guidelines, cleanup), but everything is inline in one file. The quick reference duplicates the workflow, and the category guidelines and cleanup sections could be more tightly integrated. For a skill of this length (~80 lines of content), the organization is adequate but the duplication hurts. | 2 / 3 |
Total | 9 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- freekmurze/dotfiles
- Commit
2c6f6e8
- 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.