New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Create Issue

by antiwork in antiwork/gumroad

Draft GitHub issues for the Gumroad codebase. An agent skill from antiwork/gumroad.

MITAuto-check passedTesting & QA

Install Create Issue

skills CLI
$ npx skills add antiwork/gumroad --skill create-issue -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install antiwork/gumroad create-issue --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/antiwork/gumroad.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/create-issue .claude/skills/create-issue && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
create-issue
GitHub stars
9.8k
Token cost
~747 tokens
SKILL.md length
388 words
Files
1
Skills in repo
6
Repo updated
First seen
Licence
MIT

At a glance

Draft GitHub issues for the Gumroad codebase. An agent skill from antiwork/gumroad.

  • Works in 4 steps: Understand the Problem → Decide: Single Issue or Parent +… → Write the Issue → …
  • Write a bug report
  • SKILL.md covers Workflow, Style and Important
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Create Issue is an agent skill from antiwork/gumroad. Draft GitHub issues for the Gumroad codebase. Outputs to an unstaged markdown file in the repo root. Never creates issues on GitHub. Triggers on: "create issue", "write issue", "draft issue", "write a bug report", "file an issue", "create a ticket", or when the user describes a problem or feature they want to turn into a GitHub issue.

Its SKILL.md is about 750 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering QA and bug reports. It works with GitHub. The licence is MIT.

When your agent uses it

  • Write a bug report
  • Create a ticket
  • The user describes a problem
  • Feature they want to turn into a GitHub issue

Example prompts

  • “create issue”
  • “write issue”
  • “draft issue”
  • “/create-issue”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Understand the Problem
  2. Decide: Single Issue or Parent + Sub-issues
  3. Write the Issue
  4. Output

What it can do on your machine

Read from SKILL.md and the folder at commit b195c51. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Create Issue loads about 747 tokens when it runs. Until then it costs about 87 tokens; SKILL.md has 388 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~87
When it runs · the whole SKILL.md, loaded when a task matches
~747

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from antiwork/gumroad at commit b195c51, republished under its MIT licence (© antiwork). 388 words, ~747 tokens.

Download SKILL.mdSave it as .claude/skills/create-issue/SKILL.md (or your agent's skills folder).
name
create-issue
description
Draft GitHub issues for the Gumroad codebase. Outputs to an unstaged markdown file in the repo root. Never creates issues on GitHub. Triggers on: "create issue", "write issue", "draft issue", "write a bug report", "file an issue", "create a ticket", or when the user describes a problem or feature they want to turn into a GitHub issue.

Issue Drafting

Draft well-structured GitHub issues. Output to an unstaged .md file — never post to GitHub.

Workflow

1. Understand the Problem

Gather context from the user. Ask clarifying questions if needed:

  • What's happening vs what should happen?
  • Who's affected and how often?
  • Any workarounds in use?
  • Is there data that quantifies the impact?

If the user points to code, trace the relevant paths to understand the root cause. Include aggregated, anonymized data that quantifies the impact when available (e.g., "99 purchases across 82 sellers are in this state"). Never include PII — no emails, names, IDs, or payment details.

2. Decide: Single Issue or Parent + Sub-issues

Before writing, assess the scope:

Single issue when:

  • One clear problem with one solution path
  • The fix would be one PR (~100 LOC per CONTRIBUTING.md)
  • No independent workstreams

Parent + sub-issues when:

  • The solution has multiple independently shippable parts
  • Different parts could be worked on in parallel or by different people
  • The total scope would exceed one reasonably-sized PR
  • There's a logical sequence (e.g., API integration → webhook fix → backfill)

If suggesting sub-issues, number the solution parts clearly and note which can be done independently vs which depend on each other. Write the parent issue as the full document, then note where to split.

Show full SKILL.md (181 more words)Show less
3. Write the Issue

Follow the structure in CONTRIBUTING.md.

Title — Carries most of the weight. Specific and actionable.

## What What needs to change. Be concrete — current vs desired behavior, who is affected, checkbox task list for multiple deliverables.

## Why Why this matters — business rationale or user impact, root cause if it's a bug, links to related issues or prior discussions.

4. Output

Write to gh-issue-draft.md in the repo root. Do NOT stage or commit.

If the issue should be split into sub-issues, write the parent issue first, then add a ## Sub-issues section at the end listing each sub-issue with a one-line summary. The user can split them manually.

Style

Follow CONTRIBUTING.md for terminology and tone. Additionally:

  • Concise and direct. No jargon, no filler.
  • Ground claims in data or code references.
  • Reference code by area or concept ("the dispute webhook handler"), not by file:line.
  • The issue is public (open source). Self-contained for OSS contributors with no access to internal tools.

Important

  • Use gh read-only only. Never create issues via CLI.
  • The user reviews and posts manually — just write the best possible draft.

© antiwork, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/create-issue of antiwork/gumroad.

Open the folder on GitHubat commit b195c51

Compare with similar skills

Create Issue next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Create Issue compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Create Issue this skillantiwork/gumroad9.8k—~747Automated safety check: PassMIT
Weavebench Cua ReproduceAMAP-ML/LongHorizon-Harness1.7k—~1.6kAutomated safety check: PassMIT
Evidence-Driven Testingmichaelshimeles/skills1.3k1 repos~3.9kAutomated safety check: PassNone
Create GitHub IssueNVIDIA/OpenShell15k—~1.7kAutomated safety check: PassApache-2.0
Triage IssuesClickHouse/clickhouse-java1.6k—~904Automated safety check: PassApache-2.0
Gentle AI Issue CreationGentleman-Programming/gentle-shell1.2k—~2.5kAutomated safety check: PassApache-2.0

Similar skills

  • Weavebench Cua Reproduce

    AMAP-ML/LongHorizon-Harness

    Reproduce CUA-Harness experiments on WeaveBench from a GitHub checkout.

    1.7k GitHub stars~1.6k tokensUpdated 1 mo ago
    Testing & QAAuto-check passed

  • Evidence-Driven Testing

    michaelshimeles/skills

    Records an annotated screen recording of the agent testing an app hands-on, then posts the video and a results summary to the PR and tracker issue.

    1.3k GitHub starsUsed in 1 repo~3.9k tokens
    Testing & QAAuto-check passed

  • Create GitHub Issue

    NVIDIA/OpenShell

    Official

    Create GitHub issues using the gh CLI. An agent skill from NVIDIA/OpenShell.

    15k GitHub stars~1.7k tokensUpdated today
    Testing & QAAuto-check passed

  • Triage Issues

    ClickHouse/clickhouse-java

    Analyzes a single GitHub issue at a time. An agent skill from ClickHouse/clickhouse-java.

    1.6k GitHub stars~904 tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Gentle AI Issue Creation

    Gentleman-Programming/gentle-shell

    Create and triage GitHub issues from repository evidence. An agent skill from Gentleman-Programming/gentle-shell.

    1.2k GitHub stars~2.5k tokensUpdated today
    Testing & QAAuto-check passed

  • Termio Bug Report

    termio-sh/termio

    Diagnose a termio hang, beachball, crash, or 'it froze again' from the evidence macOS and termio actually leave behind — live process samples, crash and CPU-burn reports, the unified log, the…

    540 GitHub stars~1.9k tokensUpdated yesterday
    Testing & QAAuto-check passed

More from antiwork/gumroad

  • Gumroad Prod Console

    antiwork/gumroad

    Execute read-only Ruby/Rails commands against Gumroad's production database for debugging and investigation.

    9.8k GitHub stars~2.9k tokensUpdated today
    Auto-check: notes

  • Review PR

    antiwork/gumroad

    Review GitHub pull requests for the Gumroad codebase against project guidelines, code quality, and correctness.

    9.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Email Blast

    antiwork/gumroad

    Send one-off email blasts to Gumroad creators directly via production console, no PR or deploy needed.

    9.8k GitHub stars~1.4k tokensUpdated today
    Auto-check passed

  • Commit

    antiwork/gumroad

    Stage and commit changes with a clear, concise commit message.

    9.8k GitHub stars~503 tokensUpdated today
    Auto-check passed

  • Test Confidence

    antiwork/gumroad

    AI-driven test execution. An agent skill from antiwork/gumroad.

    9.8k GitHub stars~738 tokensUpdated today
    Auto-check: notes

Works with

Categories

Questions about Create Issue

What does Create Issue do?

Draft GitHub issues for the Gumroad codebase. An agent skill from antiwork/gumroad. Create Issue is an agent skill from antiwork/gumroad. Draft GitHub issues for the Gumroad codebase.

When should I use Create Issue?

Create Issue fits situations like: write a bug report; create a ticket; the user describes a problem; feature they want to turn into a GitHub issue.

How do I install Create Issue in Claude Code?

Run `npx skills add antiwork/gumroad --skill create-issue -a claude-code`. Or copy the skill folder (.agents/skills/create-issue in antiwork/gumroad) into .claude/skills/create-issue in your project. Claude Code loads it when a task matches its description.

How do I install Create Issue in Codex?

Run `npx skills add antiwork/gumroad --skill create-issue -a codex`. Or copy the skill folder (.agents/skills/create-issue in antiwork/gumroad) into .agents/skills/create-issue in your project. Codex loads it when a task matches its description.

Can I use Create Issue in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add antiwork/gumroad --skill create-issue -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/create-issue, .gemini/skills/create-issue, .github/skills/create-issue and .opencode/skills/create-issue in your project.

What does Create Issue need to run?

SKILL.md names no scripts, command-line tools or credentials: Create Issue is instructions for the agent only.

Does Create Issue access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Create Issue safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Create Issue use?

Create Issue is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Create Issue use?

About 747 tokens (SKILL.md is roughly 3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Create Issue?

Skills that share tags, products or a category with Create Issue: Weavebench Cua Reproduce (AMAP-ML/LongHorizon-Harness, 1.7k stars), Evidence-Driven Testing (michaelshimeles/skills, 1.3k stars), Create GitHub Issue (NVIDIA/OpenShell, 15k stars) and Triage Issues (ClickHouse/clickhouse-java, 1.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Create Issue?

antiwork (a GitHub organization) maintains it in antiwork/gumroad, which has 9,786 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 7, 2026.

Source: antiwork/gumroad on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.