Mole CLI Release Flow
tw93/Mole
Runbook for assessing and executing a Mole CLI release: distribution channels, pre-flight checks, capital-V tags, build artifacts and the handoff to curated release notes.
Analyze closed GitHub issues to create troubleshooting case studies with root cause analysis and lessons learned.
Install GitHub Issue Summary
$ npx skills add ascend-ai-coding/awesome-ascend-skills --skill github-issue-summary -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ascend-ai-coding/awesome-ascend-skills github-issue-summary --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/ascend-ai-coding/awesome-ascend-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/agent-tools/github-issue-summary .claude/skills/github-issue-summary && 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 "github-issue-summary" agent skill from https://github.com/ascend-ai-coding/awesome-ascend-skills/tree/main/skills/agent-tools/github-issue-summary into .claude/skills/github-issue-summary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-issue-summary", 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/ascend-ai-coding/awesome-ascend-skills/tree/main/skills/agent-tools/github-issue-summaryType 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 ascend-ai-coding/awesome-ascend-skills --skill github-issue-summary -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ascend-ai-coding/awesome-ascend-skills github-issue-summary --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ascend-ai-coding/awesome-ascend-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/agent-tools/github-issue-summary .agents/skills/github-issue-summary && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "github-issue-summary" agent skill from https://github.com/ascend-ai-coding/awesome-ascend-skills/tree/main/skills/agent-tools/github-issue-summary into .agents/skills/github-issue-summary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-issue-summary", 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 ascend-ai-coding/awesome-ascend-skills --skill github-issue-summary -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ascend-ai-coding/awesome-ascend-skills github-issue-summary --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ascend-ai-coding/awesome-ascend-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/agent-tools/github-issue-summary .cursor/skills/github-issue-summary && 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 "github-issue-summary" agent skill from https://github.com/ascend-ai-coding/awesome-ascend-skills/tree/main/skills/agent-tools/github-issue-summary into .cursor/skills/github-issue-summary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-issue-summary", 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/ascend-ai-coding/awesome-ascend-skills.git --path skills/agent-tools/github-issue-summary--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 ascend-ai-coding/awesome-ascend-skills --skill github-issue-summary -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ascend-ai-coding/awesome-ascend-skills github-issue-summary --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ascend-ai-coding/awesome-ascend-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/agent-tools/github-issue-summary .gemini/skills/github-issue-summary && 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 "github-issue-summary" agent skill from https://github.com/ascend-ai-coding/awesome-ascend-skills/tree/main/skills/agent-tools/github-issue-summary into .gemini/skills/github-issue-summary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-issue-summary", 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 ascend-ai-coding/awesome-ascend-skills github-issue-summaryInstalls 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 ascend-ai-coding/awesome-ascend-skills --skill github-issue-summary -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ascend-ai-coding/awesome-ascend-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/agent-tools/github-issue-summary .github/skills/github-issue-summary && 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 "github-issue-summary" agent skill from https://github.com/ascend-ai-coding/awesome-ascend-skills/tree/main/skills/agent-tools/github-issue-summary into .github/skills/github-issue-summary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-issue-summary", 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 ascend-ai-coding/awesome-ascend-skills --skill github-issue-summary -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ascend-ai-coding/awesome-ascend-skills github-issue-summary --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ascend-ai-coding/awesome-ascend-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/agent-tools/github-issue-summary .opencode/skills/github-issue-summary && 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 "github-issue-summary" agent skill from https://github.com/ascend-ai-coding/awesome-ascend-skills/tree/main/skills/agent-tools/github-issue-summary into .opencode/skills/github-issue-summary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-issue-summary", 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
github-issue-summary- GitHub stars
- 174
- Token cost
- ~1.4k tokens
- SKILL.md length
- 188 words
- Files
- 4 (incl. scripts, references)
- Skills in repo
- 70
- Repo updated
- First seen
- Licence
- None found
At a glance
Analyze closed GitHub issues to create troubleshooting case studies with root cause analysis and lessons learned.
- Works in 4 steps: Fetch Issue Data — Retrieve issue… → Analyze Timeline — Extract key events,… → Generate Summary — Create structured… → …
- Summarizing resolved issue troubleshooting process
- SKILL.md covers Workflow, Quick Start, Case Study Template and Lessons Learned, plus 4 more sections
- Runs Python scripts from its folder; calls gh and curl; reaches github.com and api.github.com; needs GITHUB_TOKEN
What it does
GitHub Issue Summary is an agent skill from ascend-ai-coding/awesome-ascend-skills. Analyze closed GitHub issues to create troubleshooting case studies with root cause analysis and lessons learned. Use when: (1) summarizing resolved issue troubleshooting process, (2) creating issue case studies, (3) documenting problem-solving methodology, (4) extracting lessons from closed issues, (5) building knowledge base from issue history. Triggers: "summarize this issue", "create case study from issue", "issue resolution summary", "troubleshooting case", "postmortem analysis".
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts and reference files (for example `references/analysis-patterns.md`, `references/case-template.md` and `scripts/fetch_issue.py`).
It sits in Development, covering Root cause analysis, Runbooks and postmortems and Knowledge bases. It works with GitHub. The repository describes itself as: A comprehensive knowledge base for Huawei Ascend NPU development, structured as distributed Agent Skills. https://ascend-ai-coding.github.io/awesome-ascend-skills/.
When your agent uses it
- Summarizing resolved issue troubleshooting process
- Creating issue case studies
- Documenting problem-solving methodology
- Extracting lessons from closed issues
Example prompts
- “summarize this issue”
- “create case study from issue”
- “issue resolution summary”
- “/github-issue-summary”
Requirements
- Python 3
- A credential in GITHUB_TOKEN
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Fetch Issue Data — Retrieve issue details from GitHub
- Analyze Timeline — Extract key events, comments, and resolution steps
- Generate Summary — Create structured case study document
- Save Output — Write to docs/issue-cases/ (configurable)
What it can do on your machine
Read from SKILL.md and the folder at commit 62a4ecb. 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
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
ghcurl
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.comapi.github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
GITHUB_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
GitHub Issue Summary loads about 1.4k tokens when it runs, and up to ~3.4k if it reads all its reference files. Until then it costs about 128 tokens; SKILL.md has 188 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); the scripts in this folder are not scanned.
SKILL.md
Without a licence we can't republish the file, so here is its outline and opening line. It has 188 words (~1,439 tokens).
“Analyze closed GitHub issues and generate structured troubleshooting case studies documenting the problem-solving process, root cause, and lessons learned.”
- name
- github-issue-summary
Files
SKILL.md and 3 other files (scripts, references) in skills/agent-tools/github-issue-summary of ascend-ai-coding/awesome-ascend-skills.
- SKILL.md
- references/analysis-patterns.md
- references/case-template.md
- scripts/fetch_issue.py
Open the folder on GitHubat commit 62a4ecb
Compare with similar skills
GitHub Issue Summary 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 |
|---|---|---|---|---|---|---|
| GitHub Issue Summary this skillascend-ai-coding/awesome-ascend-skills | 174 | — | ~1.4k | Automated safety check: Pass | None | |
| Mole CLI Release Flowtw93/Mole | 70k | — | ~2.6k | Automated safety check: Pass | GPL-3.0 | |
| Qiaomu Meta Skilljoeseesun/qiaomu-meta-skill | 383 | — | ~2.8k | Automated safety check: Pass | MIT | |
| Root-Cause Analysis Writerassafkip/kipi-system | 112 | — | ~796 | Automated safety check: Pass | MIT | |
| gh-aw Workflow Diagnosisgithub/gh-aw | 5.4k | — | ~4.6k | Automated safety check: Pass | MIT | |
| Releasenubjs/nub | 4.4k | — | ~7.6k | Automated safety check: Pass | MIT |
Similar skills
Qiaomu Meta Skill
joeseesun/qiaomu-meta-skill
Research, create, improve, migrate, evaluate, package, install-check, govern, and safely publish qiaomu-flavored agent skills from workflows, prompts, transcripts, docs, SOPs, runbooks, scripts, or…
Root-Cause Analysis Writer
assafkip/kipi-system
Writes a structured, blameless root-cause analysis for a defect that escaped a test or gate, separating surface from structural causes and linting the result.
- Official
gh-aw Workflow Diagnosis
github/gh-aw
Guides your agent through diagnosing failed GitHub Agentic Workflows by downloading run logs, auditing individual runs and reading the artifacts they leave behind.
Release
nubjs/nub
Cut a Nub patch release end-to-end in one invocation. An agent skill from nubjs/nub.
Brendangregg Use Tsa
sickn33/agentic-awesome-skills
Methodical performance troubleshooting and root-cause analysis with Brendan Gregg's USE and TSA methods, plus evidence-backed RCA and postmortem reports.
More from ascend-ai-coding/awesome-ascend-skills
All 70 skills in this repoAscend Dmi
ascend-ai-coding/awesome-ascend-skills
当用户需要对华为昇腾 NPU 进行硬件层面的管理、测试或诊断时使用此 skill。典型场景： - 查看 NPU 卡的状态、温度、利用率 - 测试内存带宽（h2d/d2h/d2d/p2p） - 跑算力/功耗基准测试（TFLOPS、TOPS） - 诊断 NPU 硬件故障或做健康检查 - 对 NPU 卡做压力测试（aicore、内存） - 复位/恢复卡住或异常的 NPU 卡 典型用户问题（即使不提…
Ascendc
ascend-ai-coding/awesome-ascend-skills
End-to-end AscendC custom operator development for Ascend NPU in an ascend-kernel (csrc/ops + build.sh + torchnpu PyTorch custom op) project.
Atc Model Converter
ascend-ai-coding/awesome-ascend-skills
Complete toolkit for Huawei Ascend NPU model conversion and end-to-end inference adaptation.
External Cannbot Ops Pypto Op Develop
ascend-ai-coding/awesome-ascend-skills
当需要编写 PyPTO 算子实现时使用此 skill。基于需求规格、设计方案和参考实现，生成完整可运行的 PyPTO 算子实现与配套测试、文档。Triggers: 实现算子、写 kernel、编写实现、写 impl、算子编码、开始编码、code the op、写 test、生成测试、写实现代码、op develop、kernel 实现。
External Gitcode Ascend Megatron Change Analyzer
ascend-ai-coding/awesome-ascend-skills
Analyze official Megatron-LM commits, PRs, and branch change sets to identify feature evolution, candidate breaking changes, and migration-relevant events.
External Gitcode Ascend Megatron Commit Tracker
ascend-ai-coding/awesome-ascend-skills
Track and normalize change requests against the official Megatron-LM repository by branch, PR, commit, commit range, or time window.
Related
Works with
Categories
Questions about GitHub Issue Summary
What does GitHub Issue Summary do?
Analyze closed GitHub issues to create troubleshooting case studies with root cause analysis and lessons learned. GitHub Issue Summary is an agent skill from ascend-ai-coding/awesome-ascend-skills. Analyze closed GitHub issues to create troubleshooting case studies with root cause analysis and lessons learned.
When should I use GitHub Issue Summary?
GitHub Issue Summary fits situations like: summarizing resolved issue troubleshooting process; creating issue case studies; documenting problem-solving methodology; extracting lessons from closed issues.
How do I install GitHub Issue Summary in Claude Code?
Run `npx skills add ascend-ai-coding/awesome-ascend-skills --skill github-issue-summary -a claude-code`. Or copy the skill folder (skills/agent-tools/github-issue-summary in ascend-ai-coding/awesome-ascend-skills) into .claude/skills/github-issue-summary in your project. Claude Code loads it when a task matches its description.
How do I install GitHub Issue Summary in Codex?
Run `npx skills add ascend-ai-coding/awesome-ascend-skills --skill github-issue-summary -a codex`. Or copy the skill folder (skills/agent-tools/github-issue-summary in ascend-ai-coding/awesome-ascend-skills) into .agents/skills/github-issue-summary in your project. Codex loads it when a task matches its description.
Can I use GitHub Issue Summary 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 ascend-ai-coding/awesome-ascend-skills --skill github-issue-summary -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/github-issue-summary, .gemini/skills/github-issue-summary, .github/skills/github-issue-summary and .opencode/skills/github-issue-summary in your project.
What does GitHub Issue Summary need to run?
Going by SKILL.md and its folder, GitHub Issue Summary needs Python for the scripts in its folder, the command-line tools its instructions call (gh and curl) and credentials named GITHUB_TOKEN. Our summary lists: Python 3; A credential in GITHUB_TOKEN.
Does GitHub Issue Summary access the network?
SKILL.md names 2 domains. In commands or code: github.com and api.github.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.
Is GitHub Issue Summary 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does GitHub Issue Summary use?
No licence was found for GitHub Issue Summary or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does GitHub Issue Summary use?
About 1.4k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2k tokens, read only when the agent opens those files.
What are the alternatives to GitHub Issue Summary?
Skills that share tags, products or a category with GitHub Issue Summary: Mole CLI Release Flow (tw93/Mole, 70k stars), Qiaomu Meta Skill (joeseesun/qiaomu-meta-skill, 383 stars), Root-Cause Analysis Writer (assafkip/kipi-system, 112 stars) and gh-aw Workflow Diagnosis (github/gh-aw, 5.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains GitHub Issue Summary?
ascend-ai-coding (a GitHub organization) maintains it in ascend-ai-coding/awesome-ascend-skills, which has 174 GitHub stars. The repository holds 70 skills in this directory. The repository was last updated on October 9, 2026.
Source: ascend-ai-coding/awesome-ascend-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.