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.
85
Quality
81%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
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 skill description with strong trigger terms and clear when/what guidance. The explicit 'Use when...' clause with multiple natural trigger variations (convert, move, change) makes it easy for Claude to select appropriately. The main weakness is limited specificity in capabilities - it only mentions the core conversion action without detailing any additional features.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (GitHub issues to discussions) and the tool (agent-browser), but only describes one action (convert). Could list additional capabilities like selecting discussion categories or handling bulk conversions. | 2 / 3 |
Completeness | Clearly answers both what ('Convert GitHub issues to discussions using agent-browser') and when ('Use when asked to convert, move, or change an issue to a discussion'). Also includes helpful prerequisites about requirements. | 3 / 3 |
Trigger Term Quality | Includes natural trigger terms users would say: 'convert', 'move', 'change', 'issue to a discussion'. These are the exact phrases someone would use when needing this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche - GitHub issues to discussions conversion. Unlikely to conflict with other skills due to the specific platform (GitHub), specific action (issue-to-discussion conversion), and specific tool (agent-browser). | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%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. The workflow is well-structured with executable examples, but suffers from some redundancy between the detailed workflow and quick reference sections. The main weakness is missing error handling and validation steps for a multi-step browser automation process.
Suggestions
Add error handling guidance for common failure cases (e.g., 'Convert to discussion' button not found, dialog doesn't appear, user lacks permissions)
Remove or consolidate the Quick Reference section to eliminate duplication with the main workflow
Add a verification step in the workflow to confirm the conversion succeeded (check URL changed to /discussions/ or look for success indicator)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some redundancy - the workflow section and quick reference section largely duplicate the same commands. The category guidelines and some explanatory text could be tightened. | 2 / 3 |
Actionability | Provides fully executable bash commands throughout with specific examples of expected output (element refs, button text). Commands are copy-paste ready with clear placeholders for variable parts. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced and numbered, but lacks explicit validation/error handling. No guidance on what to do if the convert button isn't found, if the dialog doesn't appear, or if conversion fails. Step 8 explicitly skips verification. | 2 / 3 |
Progressive Disclosure | For a skill of this size (~100 lines), the structure is appropriate with clear sections (Prerequisites, Workflow, Quick Reference, Category Guidelines). No external references needed and content is well-organized for a single-purpose skill. | 3 / 3 |
Total | 10 / 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
355d067
- 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.