Review
apollographql/apollo-mcp-server
Review a GitHub pull request for a Rust codebase. An agent skill from apollographql/apollo-mcp-server.
Create GitHub issues for cuga-agent (bugs, features, epics, designs, and related work) against origin using gh, with epic → feature → issue hierarchy and GraphQL sub-issue linking.
Install Cuga GitHub Issues
$ npx skills add cuga-project/cuga-agent --skill cuga-github-issues -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cuga-project/cuga-agent cuga-github-issues --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/cuga-project/cuga-agent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.bob/skills/cuga-github-issues .claude/skills/cuga-github-issues && 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 "cuga-github-issues" agent skill from https://github.com/cuga-project/cuga-agent/tree/main/.bob/skills/cuga-github-issues into .claude/skills/cuga-github-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cuga-github-issues", 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/cuga-project/cuga-agent/tree/main/.bob/skills/cuga-github-issuesType 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 cuga-project/cuga-agent --skill cuga-github-issues -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cuga-project/cuga-agent cuga-github-issues --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cuga-project/cuga-agent.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.bob/skills/cuga-github-issues .agents/skills/cuga-github-issues && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cuga-github-issues" agent skill from https://github.com/cuga-project/cuga-agent/tree/main/.bob/skills/cuga-github-issues into .agents/skills/cuga-github-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cuga-github-issues", 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 cuga-project/cuga-agent --skill cuga-github-issues -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cuga-project/cuga-agent cuga-github-issues --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cuga-project/cuga-agent.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.bob/skills/cuga-github-issues .cursor/skills/cuga-github-issues && 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 "cuga-github-issues" agent skill from https://github.com/cuga-project/cuga-agent/tree/main/.bob/skills/cuga-github-issues into .cursor/skills/cuga-github-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cuga-github-issues", 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/cuga-project/cuga-agent.git --path .bob/skills/cuga-github-issues--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 cuga-project/cuga-agent --skill cuga-github-issues -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cuga-project/cuga-agent cuga-github-issues --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cuga-project/cuga-agent.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.bob/skills/cuga-github-issues .gemini/skills/cuga-github-issues && 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 "cuga-github-issues" agent skill from https://github.com/cuga-project/cuga-agent/tree/main/.bob/skills/cuga-github-issues into .gemini/skills/cuga-github-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cuga-github-issues", 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 cuga-project/cuga-agent cuga-github-issuesInstalls 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 cuga-project/cuga-agent --skill cuga-github-issues -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/cuga-project/cuga-agent.git skills-src && mkdir -p .github/skills && cp -r skills-src/.bob/skills/cuga-github-issues .github/skills/cuga-github-issues && 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 "cuga-github-issues" agent skill from https://github.com/cuga-project/cuga-agent/tree/main/.bob/skills/cuga-github-issues into .github/skills/cuga-github-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cuga-github-issues", 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 cuga-project/cuga-agent --skill cuga-github-issues -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install cuga-project/cuga-agent cuga-github-issues --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cuga-project/cuga-agent.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.bob/skills/cuga-github-issues .opencode/skills/cuga-github-issues && 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 "cuga-github-issues" agent skill from https://github.com/cuga-project/cuga-agent/tree/main/.bob/skills/cuga-github-issues into .opencode/skills/cuga-github-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cuga-github-issues", 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
cuga-github-issues- GitHub stars
- 893
- Token cost
- ~1.2k tokens
- SKILL.md length
- 616 words
- Files
- 3
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Create GitHub issues for cuga-agent (bugs, features, epics, designs, and related work) against origin using gh, with epic → feature → issue hierarchy and GraphQL sub-issue linking.
- Works in 6 steps: Use upstream origin (not a fork-only… → Run gh label list for that repo. Only… → No promotional footers (“Made with… → …
- The user says create new issues
- SKILL.md covers Shared rules, Detect intent, Hierarchy placement and Create epic, plus 4 more sections
- Calls gh
What it does
Cuga GitHub Issues is an agent skill from cuga-project/cuga-agent. Create GitHub issues for cuga-agent (bugs, features, epics, designs, and related work) against origin using gh, with epic → feature → issue hierarchy and GraphQL sub-issue linking. Use when the user says create new issues, report a bug, file a bug, feature request, new feature, create an epic, GitHub issue, sub-issue, or parent epic.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `github_commands.md` and `templates.md`).
It sits in Backend & APIs, covering User stories, GraphQL and Literature review. It works with GitHub, GraphQL and Model Context Protocol. The repository describes itself as: CUGA is an open-source generalist agent harness for the enterprise, supporting complex task execution on web and APIs, OpenAPI/MCP integrations, composable architecture…
When your agent uses it
- The user says create new issues
- Feature request
Example prompts
- “/cuga-github-issues”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Use upstream origin (not a fork-only default). Pass --repo owner/name when needed.
- Run gh label list for that repo. Only use label names that exist. Never invent labels.
- No promotional footers (“Made with Cursor”, etc.).
- Hierarchy depth is only: Epic → Feature → Issue. Never nest under a leaf issue. Never Feature → Feature. Never deeper than three levels.
- When parented: put Part of #. at the top of the body, create the issue, then link with GraphQL addSubIssue. Body text alone is not enough…
- Do not use unsupported gh issue edit --set-parent.
What it can do on your machine
Read from SKILL.md and the folder at commit c289e8b. 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.
Context cost
Cuga GitHub Issues loads about 1.2k tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 616 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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 616 words (~1,228 tokens).
“File issues against origin upstream with gh. Read companions as needed:”
- name
- cuga-github-issues
Files
SKILL.md and 2 other files in .bob/skills/cuga-github-issues of cuga-project/cuga-agent.
- SKILL.md
- github_commands.md
- templates.md
Open the folder on GitHubat commit c289e8b
Compare with similar skills
Cuga GitHub 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Cuga GitHub Issues this skillcuga-project/cuga-agent | 893 | — | ~1.2k | Automated safety check: Pass | Custom licence | |
| Reviewapollographql/apollo-mcp-server | 311 | — | ~2.9k | Automated safety check: Pass | MIT | |
| Spider Kingaoyunyang/spider-king-skill | 507 | — | ~7.3k | Automated safety check: Pass | MIT | |
| SpikardGoldziher/spikard | 123 | — | ~799 | Automated safety check: Pass | MIT | |
| Executor Usagejeremyosih/pi-executor | 104 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Linearkaranhudia/borg-ui | 1.7k | — | ~1.7k | Automated safety check: Pass | AGPL-3.0 |
Similar skills
Spider King
aoyunyang/spider-king-skill
Pure-web protocol reverse skill: turn hostile browser clients into browser-free Python collectors.
Spikard
Goldziher/spikard
Scaffold Spikard projects and generate code from OpenAPI, AsyncAPI, OpenRPC, GraphQL, and Protobuf schemas using the Spikard CLI or its MCP server.
Executor Usage
jeremyosih/pi-executor
Load this skill before using the execute tool. An agent skill from jeremyosih/pi-executor.
Linear
karanhudia/borg-ui
Use Symphony's lineargraphql client tool for raw Linear GraphQL operations such as comment editing and upload flows.
Distilled SDK
alchemy-run/distilled
Build or update a distilled SDK for an API provider — sourcing its OpenAPI/Smithy/GraphQL/discovery description, adding the spec mirror that feeds it, generating packages/<provider, listing it on…
More from cuga-project/cuga-agent
Cuga Contributor Workflows
cuga-project/cuga-agent
Run CUGA contributor workflows: Conventional Commits, create pull requests against origin with gh and PR templates, and ruff check/format via uv.
Related
Works with
Categories
Questions about Cuga GitHub Issues
What does Cuga GitHub Issues do?
Create GitHub issues for cuga-agent (bugs, features, epics, designs, and related work) against origin using gh, with epic → feature → issue hierarchy and GraphQL sub-issue linking. Cuga GitHub Issues is an agent skill from cuga-project/cuga-agent. Create GitHub issues for cuga-agent (bugs, features, epics, designs, and related work) against origin using gh, with epic → feature → issue hierarchy and GraphQL sub-issue linking.
When should I use Cuga GitHub Issues?
Cuga GitHub Issues fits situations like: the user says create new issues; feature request.
How do I install Cuga GitHub Issues in Claude Code?
Run `npx skills add cuga-project/cuga-agent --skill cuga-github-issues -a claude-code`. Or copy the skill folder (.bob/skills/cuga-github-issues in cuga-project/cuga-agent) into .claude/skills/cuga-github-issues in your project. Claude Code loads it when a task matches its description.
How do I install Cuga GitHub Issues in Codex?
Run `npx skills add cuga-project/cuga-agent --skill cuga-github-issues -a codex`. Or copy the skill folder (.bob/skills/cuga-github-issues in cuga-project/cuga-agent) into .agents/skills/cuga-github-issues in your project. Codex loads it when a task matches its description.
Can I use Cuga GitHub 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 cuga-project/cuga-agent --skill cuga-github-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/cuga-github-issues, .gemini/skills/cuga-github-issues, .github/skills/cuga-github-issues and .opencode/skills/cuga-github-issues in your project.
What does Cuga GitHub Issues need to run?
Going by SKILL.md and its folder, Cuga GitHub Issues needs the command-line tools its instructions call (gh).
Does Cuga GitHub 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 Cuga GitHub 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 Cuga GitHub Issues use?
Cuga GitHub Issues has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Cuga GitHub Issues use?
About 1.2k tokens (SKILL.md is roughly 4.9k 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 Cuga GitHub Issues?
Skills that share tags, products or a category with Cuga GitHub Issues: Review (apollographql/apollo-mcp-server, 311 stars), Spider King (aoyunyang/spider-king-skill, 507 stars), Spikard (Goldziher/spikard, 123 stars) and Executor Usage (jeremyosih/pi-executor, 104 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Cuga GitHub Issues?
cuga-project (a GitHub organization) maintains it in cuga-project/cuga-agent, which has 893 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 6, 2026.
Source: cuga-project/cuga-agent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.