CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

65

Quality

77%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./config/claude/skills/convert-github-issue-to-discussion/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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 a well-sequenced workflow. Its main weaknesses are the lack of error handling/validation for edge cases (missing button, permissions errors, already-converted issues) and some content duplication between the workflow and quick reference sections. The explicit skip of verification in step 8 is concerning for an irreversible operation.

Suggestions

Add error handling guidance for common failure cases: 'Convert to discussion' button not found (permissions, already converted), login timeout, or unexpected page state.

Either remove the Quick Reference section to reduce duplication or make it a true cheat-sheet that adds value beyond the workflow steps.

Add a brief verification step (e.g., check the redirected URL contains '/discussions/') instead of explicitly skipping validation for this irreversible operation.

Remove step 8 entirely since it says to do nothing — it wastes tokens and adds confusion.

DimensionReasoningScore

Conciseness

Generally efficient but has some redundancy — step 8 'Verify Conversion' says 'you don't need to verify, you are done now' which is a wasted step, and the Quick Reference section largely duplicates the workflow steps. The category guidelines and cleanup notes are brief and useful.

2 / 3

Actionability

Every step includes concrete, executable agent-browser commands with realistic examples of expected output (snapshot element references, combobox options). The commands are copy-paste ready with clear placeholders for dynamic values.

3 / 3

Workflow Clarity

Steps are clearly sequenced and cover the full process including login handling. However, there's no error recovery guidance — what if the 'Convert to discussion' button isn't found (permissions issue, already converted, etc.)? Step 8 explicitly skips verification, which is a missed validation checkpoint for a destructive/irreversible operation.

2 / 3

Progressive Disclosure

Content is reasonably organized with clear sections, but the Quick Reference section duplicates the workflow content inline rather than being separated. For a standalone skill with no bundle files, the structure is acceptable but the duplication hurts organization.

2 / 3

Total

9

/

12

Passed

Description

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 for a narrow-scope skill. It clearly states what it does, when to use it, and includes natural trigger terms covering common phrasings. The only minor weakness is that it describes a single action rather than multiple capabilities, but given the focused nature of the skill, this is appropriate.

DimensionReasoningScore

Specificity

Names the specific action ('Convert GitHub issues to discussions') and the tool ('agent-browser'), but only describes a single concrete action rather than listing multiple specific capabilities.

2 / 3

Completeness

Clearly answers both 'what' (convert GitHub issues to discussions using agent-browser) and 'when' (when asked to convert, move, or change an issue to a discussion), with explicit trigger guidance and even prerequisites.

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. Unlikely to conflict with other skills due to the narrow, well-defined scope and specific tooling requirement.

3 / 3

Total

11

/

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
freekmurze/dotfiles
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.