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

Creating Issues

by opsmill in opsmill/infrahub

Turns a single feature idea, improvement, or bug into ONE well-structured GitHub issue.

Apache-2.0Auto-check passedProduct & Project Management

Install Creating Issues

skills CLI
$ npx skills add opsmill/infrahub --skill creating-issues -a claude-code

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

GitHub CLI
$ gh skill install opsmill/infrahub creating-issues --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/opsmill/infrahub.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/creating-issues .claude/skills/creating-issues && 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
creating-issues
GitHub stars
529
Token cost
~1.2k tokens
SKILL.md length
512 words
Files
1
Skills in repo
32
Repo updated
First seen
Licence
Apache-2.0

At a glance

Turns a single feature idea, improvement, or bug into ONE well-structured GitHub issue.

  • Works in 4 steps: Learn the repository's conventions → Classify → Draft (need-focused) → …
  • : the user wants to file/open/create an issue
  • SKILL.md covers User Input, What this does, Core principle and Workflow, plus 1 more section
  • Calls gh

What it does

Creating Issues is an agent skill from opsmill/infrahub. Turns a single feature idea, improvement, or bug into ONE well-structured GitHub issue. TRIGGER when: the user wants to file/open/create an issue, turn a feature idea or improvement into a ticket, or capture something missing or broken as a ticket. DO NOT TRIGGER when: breaking work into multiple issues or planning a body of work → a planning skill; writing a full Product Requirements Document → creating-prd; the idea is still fuzzy and unhardened → grilling-ideas first.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Requires GitHub access (gh CLI authenticated, or an equivalent GitHub MCP/API tool) and write access to the target repository.

It sits in Product & Project Management, covering PRD writing and Requirements gathering. It works with GitHub. The repository describes itself as: Infrahub is a graph-based data management platform with built-in version control, CI workflows, peer review, and API access. It’s purpose-built to power reliable infrastructure… The licence is Apache-2.0.

When your agent uses it

  • : the user wants to file/open/create an issue
  • Turn a feature idea
  • Improvement into a ticket
  • Capture something missing

Example prompts

  • “Use the creating-issues skill to turn a single feature idea, improvement, or bug into ONE well-structured GitHub issue”
  • “/creating-issues”

Requirements

  • Compatibility (from SKILL.md): Requires GitHub access (gh CLI authenticated, or an equivalent GitHub MCP/API tool) and write access to the target repository.

Workflow steps

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

  1. Learn the repository's conventions
  2. Classify
  3. Draft (need-focused)
  4. Get approval, then create

What it can do on your machine

Read from SKILL.md and the folder at commit af1c6c8. 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

    Shell commands in SKILL.md call:

    • gh

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

  • Network

    No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.

    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.

  • Compatibility

    Requires GitHub access (gh CLI authenticated, or an equivalent GitHub MCP/API tool) and write access to the target repository.

    From compatibility in the SKILL.md frontmatter.

Context cost

Creating Issues loads about 1.2k tokens when it runs. Until then it costs about 123 tokens; SKILL.md has 512 words of instructions outside code blocks.

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

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 opsmill/infrahub at commit af1c6c8, republished under its Apache-2.0 licence (© opsmill). 512 words, ~1,198 tokens.

Download SKILL.mdSave it as .claude/skills/creating-issues/SKILL.md (or your agent's skills folder).
name
creating-issues
description
Turns a single feature idea, improvement, or bug into ONE well-structured GitHub issue. TRIGGER when: the user wants to file/open/create an issue, turn a feature idea or improvement into a ticket, or capture something missing or broken as a ticket. DO NOT TRIGGER when: breaking work into multiple issues or planning a body of work → a planning skill; writing a full Product Requirements Document → creating-prd; the idea is still fuzzy and unhardened → grilling-ideas first.
compatibility
Requires GitHub access (gh CLI authenticated, or an equivalent GitHub MCP/API tool) and write access to the target repository.
argument-hint
Feature, improvement, or bug to turn into a GitHub issue
metadata.version
0.1.0
metadata.author
OpsMill

Create GitHub Issue

User Input

text
$ARGUMENTS

Treat $ARGUMENTS as the thing to file. If empty, ask the user what they want to capture before starting.

What this does

Turn a feature idea, improvement, or bug into a single well-structured GitHub issue that matches the repository's own conventions. Keep it small and centred on the need — what is missing or broken, who it affects, and why it matters. Do not propose a solution and do not write acceptance criteria for features — leave the "how" to whoever picks the issue up. Always show the draft and get explicit approval before creating anything.

Core principle

An issue states the need, not the answer. The person (or agent) who implements it decides the approach. For a feature or improvement that means no design, no task breakdown, no acceptance criteria — just a clear problem and its context. For a bug, the "need" is the misbehaviour itself, so reproduction details belong in the issue.

Workflow

1. Learn the repository's conventions

Probe whatever context the repo actually provides — don't assume a fixed layout:

  • Read context docs if present: AGENTS.md, CLAUDE.md, CONTEXT.md, README, or a dev/ directory.
  • Check for issue templates in .github/ISSUE_TEMPLATE/ and honour them if they exist.
  • List the repo's labels (gh label list) and a few recent issues (gh issue list) to match title style, labels, and tone.

If the repo provides an issue template, honour its structure as-is — the fields are there deliberately. The only thing to hold back is prescribing a solution: fill the template's sections with the need and context, not with a design.

2. Classify

Decide whether this is a feature / improvement or a bug. When unsure, ask the user.

3. Draft (need-focused)

Feature / improvement — keep it lean:

markdown
## Need

[What's missing or could be better, who it affects, and why it matters now.]

## Context

[Only what's needed to understand the need: relevant area of the product, links to related discussion, constraints. No design.]

## References

- Related issue: #[number]
- Documentation / discussion: [url]

Bug — capture the misbehaviour:

markdown
## What happens

[Observed behaviour.]

## What should happen

[Expected behaviour.]

## Steps to reproduce

1. ...
2. ...

## Environment

[Version, OS, configuration, or other relevant context.]

## References

- Related issue: #[number]
- Logs / screenshots: [link or `<details>` block]

Draft a clear, searchable title using the repo's convention (e.g. feat:, fix:, or whatever recent issues use), and pick labels from the repo's existing set.

Show full SKILL.md (197 more words)Show less
4. Get approval, then create

By default, present the full draft (title, labels, body) to the user and wait for explicit approval before creating the issue — even when you have permission to create it directly. The gate exists to stop silent creation from mere permission; it is not meant to override a direct instruction.

If the user has explicitly told you to file it without review (e.g. "just file it, don't ask"), honour that — but still echo the final title, labels, and body in your reply before (or as) you create it, so there's a record of what went out.

Create the issue with the available tooling, for example:

bash
gh issue create --title "[TITLE]" --body "[BODY]" --label "[LABELS]"

--label takes a comma-separated list (--label 'bug,enhancement') — a space-separated value is treated as a single label name.

Or the equivalent GitHub MCP call. Return the issue URL.

Guardrails

  • Prefer clarity over completeness — a short, sharp issue beats a padded one.
  • Resist scope creep: one need per issue. If the input contains several, surface that and ask whether to split.
  • Don't invent labels, milestones, or assignees that don't exist in the repo.
  • Don't smuggle a solution into the "Need" or "Context" — if you catch yourself describing how, cut it.

© opsmill, Apache-2.0. 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/creating-issues of opsmill/infrahub.

Open the folder on GitHubat commit af1c6c8

Compare with similar skills

Creating Issues 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.

Creating Issues compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Creating Issues this skillopsmill/infrahub529—~1.2kAutomated safety check: PassApache-2.0
Ouroboros PM InterviewQ00/ouroboros6.2k—~5.7kAutomated safety check: PassMIT
RalphTheCraigHewitt/skills156—~1kAutomated safety check: PassMIT
ShapeTheCraigHewitt/skills156—~1.7kAutomated safety check: PassMIT
CCPM Project Managementautomazeio/ccpm8.4k—~1.1kAutomated safety check: PassMIT
User Alignment and Agent-Ready PRDstryproduck/produck-skills511—~5.3kAutomated safety check: PassApache-2.0

Similar skills

  • Ouroboros PM Interview

    Q00/ouroboros

    Runs a guided product-manager interview that classifies each question automatically and produces a Product Requirements Document.

    6.2k GitHub stars~5.7k tokensUpdated yesterday
    Product & Project ManagementAuto-check passed

  • Ralph

    TheCraigHewitt/skills

    Autonomous PRD implementation loop — turns GitHub issues into shipped code using TDD, code review gates, and Docker sandbox isolation.

    156 GitHub stars~1k tokensUpdated 4 mo ago
    Product & Project ManagementAuto-check passed

  • Shape

    TheCraigHewitt/skills

    A skill your agent uses when you have a rough product idea and want a complete PRD without sitting through an interactive grilling.

    156 GitHub stars~1.7k tokensUpdated 4 mo ago
    Product & Project ManagementAuto-check passed

  • CCPM Project Management

    automazeio/ccpm

    Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.

    8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed

  • User Alignment and Agent-Ready PRDs

    tryproduck/produck-skills

    Turns a vague feature request into a written spec with scope, phases, acceptance criteria and do-not-do limits that a coding agent can follow without guessing.

    511 GitHub stars~5.3k tokensUpdated 1 mo ago
    Product & Project ManagementAuto-check passed

  • Feature Forge

    Jeffallan/claude-skills

    Runs a structured requirements interview to produce a feature specification with EARS requirements, acceptance criteria and an implementation checklist.

    12k GitHub stars~1.1k tokensUpdated 4 days ago
    Product & Project ManagementAuto-check passed

More from opsmill/infrahub

All 32 skills in this repo

  • Analyzing CI Flakiness

    opsmill/infrahub

    Analyzes recent CI failures on pull requests to identify flaky tests, using retry outcomes (failed attempt → green re-run) and cross-PR recurrence as evidence, and maintains a local longitudinal…

    529 GitHub stars~2k tokensUpdated today
    Auto-check passed

  • Audit Docs

    opsmill/infrahub

    Audits internal (dev/) and external (docs/) documentation completeness for a feature, subject, or set of existing docs, maps changes indicated by the user, across Infrahub's documentation layers…

    529 GitHub stars~1.5k tokensUpdated today
    Auto-check passed

  • Commit

    opsmill/infrahub

    Stages and commits the current changes onto a safe working branch, enforcing branch discipline and optionally pushing upstream.

    529 GitHub stars~2.8k tokensUpdated today
    Auto-check: notes

  • Creating Changelog Entries

    opsmill/infrahub

    A skill your agent uses when you've fixed a bug, added a feature, or made any user-facing change in a project that uses Towncrier and need to record it for the changelog — before committing or…

    529 GitHub stars~1.9k tokensUpdated today
    Auto-check passed

  • Creating Prd

    opsmill/infrahub

    Synthesises the current conversation context into a Product Requirements Document and publishes it to GitHub (as a comment on a referenced issue, or a new issue).

    529 GitHub stars~4k tokensUpdated today
    Auto-check passed

  • Grilling Ideas

    opsmill/infrahub

    Stress-tests a fuzzy or vague feature idea before any PRD, spec, or ticket is written.

    529 GitHub stars~3.8k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Creating Issues

What does Creating Issues do?

Turns a single feature idea, improvement, or bug into ONE well-structured GitHub issue. Creating Issues is an agent skill from opsmill/infrahub. Turns a single feature idea, improvement, or bug into ONE well-structured GitHub issue.

When should I use Creating Issues?

Creating Issues fits situations like: : the user wants to file/open/create an issue; turn a feature idea; improvement into a ticket; capture something missing.

How do I install Creating Issues in Claude Code?

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

How do I install Creating Issues in Codex?

Run `npx skills add opsmill/infrahub --skill creating-issues -a codex`. Or copy the skill folder (.agents/skills/creating-issues in opsmill/infrahub) into .agents/skills/creating-issues in your project. Codex loads it when a task matches its description.

Can I use Creating Issues 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 opsmill/infrahub --skill creating-issues -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/creating-issues, .gemini/skills/creating-issues, .github/skills/creating-issues and .opencode/skills/creating-issues in your project.

What does Creating Issues need to run?

Going by SKILL.md and its folder, Creating Issues needs the command-line tools its instructions call (gh). Compatibility (from SKILL.md): Requires GitHub access (gh CLI authenticated, or an equivalent GitHub MCP/API tool) and write access to the target repository..

Does Creating Issues access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Creating Issues 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 Creating Issues use?

Creating Issues is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Creating Issues use?

About 1.2k tokens (SKILL.md is roughly 4.8k 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 Creating Issues?

Skills that share tags, products or a category with Creating Issues: Ouroboros PM Interview (Q00/ouroboros, 6.2k stars), Ralph (TheCraigHewitt/skills, 156 stars), Shape (TheCraigHewitt/skills, 156 stars) and CCPM Project Management (automazeio/ccpm, 8.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Creating Issues?

opsmill (a GitHub organization) maintains it in opsmill/infrahub, which has 529 GitHub stars. The repository holds 32 skills in this directory. The repository was last updated on October 7, 2026.

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