Weavebench Cua Reproduce
AMAP-ML/LongHorizon-Harness
Reproduce CUA-Harness experiments on WeaveBench from a GitHub checkout.
Create GitHub issues using the gh CLI. An agent skill from NVIDIA/OpenShell.
Install Create GitHub Issue
$ npx skills add NVIDIA/OpenShell --skill create-github-issue -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install NVIDIA/OpenShell create-github-issue --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/NVIDIA/OpenShell.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/create-github-issue .claude/skills/create-github-issue && rm -rf skills-srcUse ~/.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/
Install the "create-github-issue" agent skill from https://github.com/NVIDIA/OpenShell/tree/main/.agents/skills/create-github-issue into .claude/skills/create-github-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-github-issue", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/NVIDIA/OpenShell/tree/main/.agents/skills/create-github-issueType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add NVIDIA/OpenShell --skill create-github-issue -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install NVIDIA/OpenShell create-github-issue --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/OpenShell.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/create-github-issue .agents/skills/create-github-issue && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "create-github-issue" agent skill from https://github.com/NVIDIA/OpenShell/tree/main/.agents/skills/create-github-issue into .agents/skills/create-github-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-github-issue", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add NVIDIA/OpenShell --skill create-github-issue -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install NVIDIA/OpenShell create-github-issue --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/OpenShell.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/create-github-issue .cursor/skills/create-github-issue && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "create-github-issue" agent skill from https://github.com/NVIDIA/OpenShell/tree/main/.agents/skills/create-github-issue into .cursor/skills/create-github-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-github-issue", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/NVIDIA/OpenShell.git --path .agents/skills/create-github-issue--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add NVIDIA/OpenShell --skill create-github-issue -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install NVIDIA/OpenShell create-github-issue --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/OpenShell.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/create-github-issue .gemini/skills/create-github-issue && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "create-github-issue" agent skill from https://github.com/NVIDIA/OpenShell/tree/main/.agents/skills/create-github-issue into .gemini/skills/create-github-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-github-issue", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install NVIDIA/OpenShell create-github-issueInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add NVIDIA/OpenShell --skill create-github-issue -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/NVIDIA/OpenShell.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/create-github-issue .github/skills/create-github-issue && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "create-github-issue" agent skill from https://github.com/NVIDIA/OpenShell/tree/main/.agents/skills/create-github-issue into .github/skills/create-github-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-github-issue", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add NVIDIA/OpenShell --skill create-github-issue -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install NVIDIA/OpenShell create-github-issue --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/OpenShell.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/create-github-issue .opencode/skills/create-github-issue && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "create-github-issue" agent skill from https://github.com/NVIDIA/OpenShell/tree/main/.agents/skills/create-github-issue into .opencode/skills/create-github-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-github-issue", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
create-github-issue- GitHub stars
- 15k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 531 words
- Files
- 1
- Skills in repo
- 23
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Create GitHub issues using the gh CLI. An agent skill from NVIDIA/OpenShell.
- The user wants to create a new issue
- SKILL.md covers Prerequisites, Issue Templates, Useful Options and After Creating
- Calls gh and git; reaches github.com
- Request a feature
What it does
Create GitHub Issue is an agent skill from NVIDIA/OpenShell, published by the product's own GitHub organization. Create GitHub issues using the gh CLI. Use when the user wants to create a new issue, report a bug, request a feature, or create a task in GitHub. Trigger keywords - create issue, new issue, file bug, report bug, feature request, github issue.
Its SKILL.md is about 1.7k 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 repository describes itself as: OpenShell is the safe, private runtime for autonomous AI agents. The licence is Apache-2.0.
When your agent uses it
- The user wants to create a new issue
- Request a feature
- Create a task in GitHub
- Keywords - create issue
Example prompts
- “/create-github-issue”
What it can do on your machine
Read from SKILL.md and the folder at commit 834b79a. 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:
ghgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
github.com
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 GitHub Issue loads about 1.7k tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 531 words of instructions outside code blocks.
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 NVIDIA/OpenShell at commit 834b79a, republished under its Apache-2.0 licence (© NVIDIA). 531 words, ~1,677 tokens.
Download SKILL.mdSave it as
.claude/skills/create-github-issue/SKILL.md (or your agent's skills folder).- name
- create-github-issue
- description
- Create GitHub issues using the gh CLI. Use when the user wants to create a new issue, report a bug, request a feature, or create a task in GitHub. Trigger keywords - create issue, new issue, file bug, report bug, feature request, github issue.
- metadata.internal
- true
Create GitHub Issue
Create issues on GitHub using the gh CLI. Issues must conform to the project's issue templates.
Prerequisites
The gh CLI must be authenticated (gh auth status).
Issue Templates
This project uses YAML form issue templates. When creating issues, match the template structure so the output aligns with what GitHub renders.
Bug Reports
Do not add a type label automatically. Confirm that the human operator personally uses OpenShell and directly encountered the problem or needs the feature for a specific use case. If that first-hand attestation or concrete use case is missing, ask for it before creating the issue. Frame the issue entirely in terms of OpenShell. The body must include a User Story, Problem Statement, Impact / Why This Matters, and Acceptance Criteria, followed by bug-specific reproduction steps using only OpenShell deployments and environment details. Do not install third-party tools to demonstrate reproducibility. Logs are optional and must be concise and redacted. If the issue suggests a change to configuration, CLI, SDK, or other user experience, include a notional example of the proposed interaction for human review. Inspect current repository labels before applying any; use only labels whose meaning is clear.
gh issue create \
--title "bug: <concise description>" \
--body "$(cat <<'EOF'
## User Story
I use OpenShell for <specific use case>. I directly encountered or need <specific behavior> so that <outcome>.
## Problem Statement
<Summarize what is broken or missing in OpenShell's current behavior and when the issue occurs>
## Impact / Why This Matters
<Explain the consequences for users, the current workaround, and why that workaround is insufficient>
## Acceptance Criteria
- [ ] <observable outcome that demonstrates the bug is fixed>
## Reproduction Steps
1. <step>
2. <step>
## Environment
- OpenShell: <version>
- OS: <os>
- Runtime, deployment, or integration: <relevant details>
## Suggested UX (if applicable)
<Notional OpenShell CLI, configuration, SDK, or other interaction>
## Logs
<Optional minimal, redacted output>
EOF
)"Feature Requests
Do not add a type label automatically. Confirm that the human operator personally uses OpenShell and directly encountered the problem or needs the feature for a specific use case. If that first-hand attestation or concrete use case is missing, ask for it before creating the issue. Frame the issue entirely in terms of OpenShell. The body must include a User Story, Problem Statement, Impact / Why This Matters, Proposed Design, Acceptance Criteria, and Alternatives Considered. The proposed design should define the user-facing workflow and externally observable behavior without prescribing internal implementation. Agent investigation is optional. If the issue suggests a change to configuration, CLI, SDK, or other user experience, include a notional example of the proposed interaction for human review. Inspect current repository labels before applying any; use only labels whose meaning is clear.
gh issue create \
--title "feat: <concise description>" \
--body "$(cat <<'EOF'
## User Story
I use OpenShell for <specific use case>. I directly encountered or need <specific behavior> so that <outcome>.
## Problem Statement
<Summarize the capability or behavior missing from OpenShell today>
## Impact / Why This Matters
<Explain what users must do today, why it is insufficient, and the operational cost, risk, blocked workflow, or adoption barrier>
## Proposed Design
<The desired user-facing workflow and externally observable behavior, without prescribing internal implementation>
## Suggested UX (if applicable)
<Notional OpenShell CLI, configuration, SDK, or other interaction>
## Acceptance Criteria
- [ ] <specific, observable outcome>
## Alternatives Considered
<Other OpenShell workflows considered, including relevant middleware, interceptors, providers, or other extension points, and why the proposal better serves the use case. Prefer an applicable extension when it satisfies the use case; running another service alone is not a reason to dismiss it.>
## Agent Investigation
<Optional findings from codebase exploration>
EOF
)"Show full SKILL.md (203 more words)Show less
Tasks
For internal tasks that do not fit bug/feature templates, still obtain the operator's first-hand OpenShell use case before creating the issue:
gh issue create \
--title "<type>: <description>" \
--body "$(cat <<'EOF'
## User Story
<I personally use OpenShell for this specific case and directly need this work because...>
## Description
<Clear description of the work>
## Context
<Any dependencies, related issues, or background>
## Definition of Done
- [ ] <criterion>
EOF
)"GitHub built-in issue types (Bug, Feature, Task) should come from the matching issue template when possible, or be set manually afterward. Do not try to emulate them through labels.
Creating an issue does not accept it. Follow Label Discovery in CONTRIBUTING.md to retrieve every page of current state:* label definitions and resolve unclear meanings, then follow its triage → validation → human acceptance process. Agents may assess facts, but only humans decide whether to accept work or place it on the roadmap. A direct user request authorizes the requested planning or implementation phase without changing issue disposition.
Useful Options
| Option | Description |
|---|---|
--title, -t | Issue title (required) |
--body, -b | Issue description |
--label, -l | Add label (can use multiple times) |
--milestone, -m | Add to milestone |
--project, -p | Add to project |
--web | Open in browser after creation |
After Creating
The command outputs the issue URL and number.
Display the URL using markdown link syntax so it's easily clickable:
Created issue [#123](https://github.com/OWNER/REPO/issues/123)Use the issue number to:
- Reference in signed-off Conventional Commits:
git commit --signoff -m "fix(cli): validate empty requests (fixes #123)" - Create a branch following Branch Names in
CONTRIBUTING.md.
© NVIDIA, 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/create-github-issue of NVIDIA/OpenShell.
Open the folder on GitHubat commit 834b79a
Compare with similar skills
Create GitHub 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Create GitHub Issue this skillNVIDIA/OpenShell | 15k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Weavebench Cua ReproduceAMAP-ML/LongHorizon-Harness | 1.7k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Evidence-Driven Testingmichaelshimeles/skills | 1.3k | 1 repos | ~3.9k | Automated safety check: Pass | None | |
| Triage IssuesClickHouse/clickhouse-java | 1.6k | — | ~904 | Automated safety check: Pass | Apache-2.0 | |
| Gentle AI Issue CreationGentleman-Programming/gentle-shell | 1.2k | — | ~2.5k | Automated safety check: Pass | Apache-2.0 | |
| Termio Bug Reporttermio-sh/termio | 540 | — | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
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.
Triage Issues
ClickHouse/clickhouse-java
Analyzes a single GitHub issue at a time. An agent skill from ClickHouse/clickhouse-java.
Gentle AI Issue Creation
Gentleman-Programming/gentle-shell
Create and triage GitHub issues from repository evidence. An agent skill from Gentleman-Programming/gentle-shell.
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…
Filing User Bug Reports
damus-io/damus
Process conversations or chat logs to identify reported bugs, search for existing GitHub issues, update existing issues when new undocumented details are discovered, and create new issues for…
More from NVIDIA/OpenShell
All 23 skills in this repo- Official
Build Openshell Mxc Windows
NVIDIA/OpenShell
Maintain and validate OpenShell's build-only Windows MSVC lane for x64 and ARM64.
- Official
Create GitHub PR
NVIDIA/OpenShell
Create GitHub pull requests using the gh CLI. An agent skill from NVIDIA/OpenShell.
- Official
Debug Inference
NVIDIA/OpenShell
Debug inference clients that use an attached provider and its native endpoint, including hosted APIs and host-local Ollama, vLLM, SGLang, TRT-LLM, LM Studio, or NIM.
- Official
Debug Openshell Cluster
NVIDIA/OpenShell
Debug why an OpenShell gateway deployment is unhealthy, unreachable, or unable to create sandboxes.
- Official
Gator Gate
NVIDIA/OpenShell
Validate and monitor OpenShell GitHub issues and PRs using the gator: state machine.
- Official
Helm Dev Environment
NVIDIA/OpenShell
Start up, tear down, and configure the local Kubernetes development environment for OpenShell.
Related
Works with
Categories
Questions about Create GitHub Issue
What does Create GitHub Issue do?
Create GitHub issues using the gh CLI. An agent skill from NVIDIA/OpenShell. Create GitHub Issue is an agent skill from NVIDIA/OpenShell, published by the product's own GitHub organization. Create GitHub issues using the gh CLI.
When should I use Create GitHub Issue?
Create GitHub Issue fits situations like: the user wants to create a new issue; request a feature; create a task in GitHub; keywords - create issue.
How do I install Create GitHub Issue in Claude Code?
Run `npx skills add NVIDIA/OpenShell --skill create-github-issue -a claude-code`. Or copy the skill folder (.agents/skills/create-github-issue in NVIDIA/OpenShell) into .claude/skills/create-github-issue in your project. Claude Code loads it when a task matches its description.
How do I install Create GitHub Issue in Codex?
Run `npx skills add NVIDIA/OpenShell --skill create-github-issue -a codex`. Or copy the skill folder (.agents/skills/create-github-issue in NVIDIA/OpenShell) into .agents/skills/create-github-issue in your project. Codex loads it when a task matches its description.
Can I use Create GitHub 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 NVIDIA/OpenShell --skill create-github-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-github-issue, .gemini/skills/create-github-issue, .github/skills/create-github-issue and .opencode/skills/create-github-issue in your project.
What does Create GitHub Issue need to run?
Going by SKILL.md and its folder, Create GitHub Issue needs the command-line tools its instructions call (gh and git).
Does Create GitHub Issue access the network?
SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Create GitHub 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 GitHub Issue use?
Create GitHub Issue 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 Create GitHub Issue use?
About 1.7k tokens (SKILL.md is roughly 6.7k 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 GitHub Issue?
Skills that share tags, products or a category with Create GitHub Issue: Weavebench Cua Reproduce (AMAP-ML/LongHorizon-Harness, 1.7k stars), Evidence-Driven Testing (michaelshimeles/skills, 1.3k stars), Triage Issues (ClickHouse/clickhouse-java, 1.6k stars) and Gentle AI Issue Creation (Gentleman-Programming/gentle-shell, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Create GitHub Issue?
NVIDIA (a GitHub organization, an official publisher) maintains it in NVIDIA/OpenShell, which has 15,188 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on October 7, 2026.
Source: NVIDIA/OpenShell on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.