# Github Issues

> Read, summarize, and triage GitHub issues and pull requests for a repository using the authenticated GitHub MCP server. Invoke whenever the user asks about open issues, wants a repo's issues summarized or triaged, asks to find issues by label or author, or asks to draft an issue.

- **Type:** Skill
- **Install:** `agentstack add skill-curie-eng-curie-github-issues`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [curie-eng](https://agentstack.voostack.com/s/curie-eng)
- **Installs:** 0
- **Category:** [Cloud & Infrastructure](https://agentstack.voostack.com/c/cloud-infrastructure)
- **Latest version:** 0.1.0
- **License:** Apache-2.0
- **Upstream author:** [curie-eng](https://github.com/curie-eng)
- **Source:** https://github.com/curie-eng/curie/tree/main/examples/github-issues/skills/github-issues
- **Website:** https://www.curietech.ai

## Install

```sh
agentstack add skill-curie-eng-curie-github-issues
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# GitHub issue triage

## When to run
The user asks about a repository's issues or pull requests — to list open
issues, summarize them, find ones by label/assignee/author, or draft a new
issue for review.

## How to answer
1. Identify the repository (`owner/repo`). Ask if the user did not name one.
2. Call the `github` server's tools:
   - list/search issues to pull the current open set,
   - fetch a single issue when the user asks about one in particular.
3. Summarize plainly: title, number, author, labels, and a one-line gist.
   Group by label or priority when triaging.
4. When asked to draft an issue, write the title and body and show it for the
   user to confirm — do not create it unless the user explicitly says to.

## Notes
`github` is the off-the-shelf `@modelcontextprotocol/server-github` stdio MCP
server, declared in this bundle's `.mcp.json`. It authenticates with a GitHub
personal access token read from `GITHUB_PERSONAL_ACCESS_TOKEN` in the sandbox
environment. That token is NOT in the bundle: you forward it at launch with
`curie skill up --secret GITHUB_PERSONAL_ACCESS_TOKEN` (see the README), which
passes the variable by name into the container the same way model credentials
are forwarded. A read-scoped token is enough for listing and reading; creating
an issue needs `repo`/`issues` write scope.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [curie-eng](https://github.com/curie-eng)
- **Source:** [curie-eng/curie](https://github.com/curie-eng/curie)
- **License:** Apache-2.0
- **Homepage:** https://www.curietech.ai

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-curie-eng-curie-github-issues
- Seller: https://agentstack.voostack.com/s/curie-eng
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.