CO

convert-github-issue-to-discussion

Converts GitHub issues to discussions via browser automation when CLI tools are insufficient.

Install

mkdir -p .claude/skills/convert-github-issue-to-discussion && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2802" && unzip -o skill.zip -d .claude/skills/convert-github-issue-to-discussion && rm skill.zip

Installs to .claude/skills/convert-github-issue-to-discussion

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

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.
198 chars✓ has a “when” trigger
Intermediate

Key capabilities

  • Navigate GitHub issue pages
  • Automate button interaction for conversion
  • Select discussion categories
  • Confirm conversion via browser automation

How it works

It opens a headed browser to the issue, waits for user authentication, and uses browser automation to click the conversion button and select a category.

Inputs & outputs

You give it
GitHub issue URL
You get back
Confirmation of issue conversion to discussion

When to use convert-github-issue-to-discussion

  • Convert feature request issues to ideas
  • Move support tickets to Q&A discussions
  • Clean up issue trackers

About this skill

Convert GitHub Issue to Discussion

Convert GitHub issues to discussions using browser automation when the gh CLI doesn't support this operation.

Prerequisites

  • agent-browser installed
  • User must log in to GitHub when prompted

Workflow

1. Open Browser in Headed Mode

agent-browser open "https://github.com/<owner>/<repo>/issues/<number>" --headed

The --headed flag shows the browser window so the user can log in.

2. Wait for User Login

Take a snapshot to check if logged in:

agent-browser snapshot -i

If you see "Sign in" in the elements, the user needs to log in. Let them know and wait for confirmation.

3. Navigate to the Issue

After login, go to the issue page:

agent-browser open "https://github.com/<owner>/<repo>/issues/<number>"

4. Find the Convert Button

Take a snapshot and look for "Convert to discussion":

agent-browser snapshot -i

Look for a button like:

- button "Convert to discussion" [ref=e137]

5. Click Convert to Discussion

agent-browser click @<ref>

6. Select Discussion Category

A dialog will appear with category options:

agent-browser snapshot -i

You'll see options like:

- combobox "Category for new discussion" [ref=e2]
- option "General" [ref=e3] [selected]
- option "Ideas" [ref=e4]
- option "Q&A" [ref=e6]
- button "I understand, convert this issue" [ref=e9]

Select appropriate category (Q&A for support questions, Ideas for feature requests):

agent-browser select @<combobox-ref> "Q&A"

7. Confirm Conversion

agent-browser click @<confirm-button-ref>

8. Verify Conversion

You don't need to verify, you are done now.

Quick Reference

# Open issue page with visible browser
agent-browser open "https://github.com/owner/repo/issues/123" --headed

# Wait for user to log in, then get elements
agent-browser snapshot -i

# Click convert button (ref from snapshot)
agent-browser click @e137

# Wait for dialog, get new elements
agent-browser wait 1000 && agent-browser snapshot -i

# Select category and confirm
agent-browser select @e2 "Q&A"
agent-browser click @e9

# Verify - should redirect to discussions
agent-browser wait 2000 && agent-browser get url

Category Guidelines

  • Q&A: Support questions, debugging help, how-to questions
  • Ideas: Feature requests needing discussion
  • General: General conversation, announcements
  • Show and tell: Project showcases

Cleanup

You do not have to close the browser, as we'll use the login state again to convert other issues to discussions

Looking for issues

When you are asked to find for more good issues to convert to discussions, use gh

When not to use it

  • When the GitHub CLI supports the operation directly
  • When the user cannot log in via a headed browser

Prerequisites

agent-browser installedGitHub account access

Limitations

  • Requires headed browser for authentication
  • Requires manual user login

How it compares

It performs UI-based automation for tasks unsupported by the GitHub CLI.

Compared to similar skills

convert-github-issue-to-discussion side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
convert-github-issue-to-discussion (this skill)16moReviewIntermediate
tmux202moReviewIntermediate
jira116moNo flagsBeginner
triaging-issues52moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry