Zed open discussion

Skill g-kartik/agent-skills/skills/zed-open-discussion

CLI AI Agents Skills Repository

Install

npx -y skills add g-kartik/agent-skills --skill zed-open-discussion

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Open a feature request discussion on the zed-industries/zed GitHub repo following the official template and guidelines. Use when the user wants to propose a feature or improvement for the Zed editor.

SKILL.md

2.0 KB, 450 tokens by cl100k_base, as published. Nobody here has run it

You are opening a feature request discussion on the zed-industries/zed GitHub repository.

Constants

Repository ID: MDEwOlJlcG9zaXRvcnkzNDA1NDc1MjA=
Feature Requests category ID: DIC_kwDOFExXwM4CmTuW

Steps

Confirm gh is authenticated (gh auth status). Stop and tell the user if not.
Ask the user for the feature idea if not already described. Clarify until you have enough to fill the template.
Compose the discussion body using the official template sections — no other structure:

# What are you proposing?

<High-level description of the feature, improvement, or change.>

# Why does this matter?

<What problem does this solve? What becomes easier or possible?>

# Are there any examples or context?

<Screenshots, workflows, or examples from other tools — omit this section if nothing relevant.>

# Possible approach

<If the user has ideas about implementation, include them here — otherwise omit this section.>

Show the composed title and body to the user for confirmation before posting.
After confirmation, post via GraphQL:

gh api graphql -f query='
mutation {
  createDiscussion(input: {
    repositoryId: "MDEwOlJlcG9zaXRvcnkzNDA1NDc1MjA="
    categoryId: "DIC_kwDOFExXwM4CmTuW"
    title: "<TITLE>"
    body: "<BODY>"
  }) {
    discussion { url number title }
  }
}'

Return the discussion URL.

Rules

No emojis anywhere in the title or body.
Keep the body concise — avoid padding, filler phrases, and restating the title.
Omit optional sections ("Are there any examples" / "Possible approach") if the user has nothing meaningful to add.
Do not include the user's private examples or internal project details unless they explicitly ask.
The title should be short and specific: <Component>: <imperative description>.