Explainer
Explain a GitHub issue or pull request at 100, 200, and 300 level. Verifies every claim against the code, then writes a markdown and a self-contained HTML version into .scratchpad/issue-NNNN/ or .scratchpad/pr-NNNN/ and opens it for preview. Starts no server; offers a command for anyone who wants one. Use when asked to explain, write up, or produce an explainer for an issue or PR.
Install
npx skills add agentic-community/mcp-gateway-registry --skill explainergit clone --depth 1 https://github.com/agentic-community/mcp-gateway-registry.git /tmp/mcp-gateway-registry
mkdir -p ~/.claude/skills
cp -r /tmp/mcp-gateway-registry/.claude/skills/explainer ~/.claude/skills/explainerPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Explainer Skill Turn a GitHub issue or pull request into an explainer a colleague can read at whatever depth they need. Three levels, one document: 100 for anyone, 200 for how it works, 300 for the code. Apply the [writing](../writing/SKILL.md) skill to every word of prose. Invoke it, then run its revision pass before you write the file. No emojis and no em-dashes anywhere, per the repo rules. ## Inputs Accept any of these and resolve to a number plus a kind: - A full URL: `https://github.com/agentic-community/mcp-gateway-registry/issues/1832` - A PR URL: `.../pull/1711` - A bare reference: `#1832`, `1832`, `owner/repo#1832` A URL containing `/pull/` is a PR. Everything else needs a check, because `gh issue view` succeeds on PRs too. Run `gh pr view <n> --json number` and treat a clean exit as a PR. Write output to `.scratchpad/issue-NNNN/` or `.scratchpad/pr-NNNN/`. Create it with `mkdir -p`. `.scratchpad/` is gitignored, so nothing you write here can be committed. ## Step 1: gather For an issue: ```bash gh issue view <n> --json number,title,state,labels,author,createdAt,body,comments ``` For a PR, get the discussion and the diff: ```bash gh pr view <n> --json number,title,state,author,createdAt,body,comments,files,additions,deletions,baseRefName,headRefName gh pr diff <n> ``` Record the commit you verified against, and use it to pin every code link: ```bash git rev-parse --short HEAD ``` ## Step 2: verify before you explain
Details
- Skill name
explainer- Repository
- agentic-community/mcp-gateway-registry
- Path
.claude/skills/explainer/SKILL.md- License
- Apache-2.0
- Repo updated
- 18 November 2026
FAQ
What does the Explainer skill do?
Explain a GitHub issue or pull request at 100, 200, and 300 level. Verifies every claim against the code, then writes a markdown and a self-contained HTML version into .scratchpad/issue-NNNN/ or .scratchpad/pr-NNNN/ and opens it for preview. Starts no server; offers a command for anyone who wants one. Use when asked to explain, write up, or produce an explainer for an issue or PR.
How do I install the Explainer skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add agentic-community/mcp-gateway-registry --skill explainer. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Explainer popular?
It lives in agentic-community/mcp-gateway-registry, which has 1,052 GitHub stars and 263 forks.
Related skills
Agentcore Register
1.1kagentic-community/mcp-gateway-registry
Given an MCP server URL, probe the server via curl to discover its metadata and tools, then generate a markdown file with copy-pasteable content for each field in the Amazon Bedrock AgentCore "Create record" form.
Benchmark Report
1.1kagentic-community/mcp-gateway-registry
Generate a benchmark report from stress test results (registration, API performance, search concurrency). Reads JSON result files and produces a markdown report suitable for docs/benchmarks/.
Create Milestone
1.1kagentic-community/mcp-gateway-registry
Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.
PR Review
1.1kagentic-community/mcp-gateway-registry
Review a GitHub pull request using multiple expert personas. Takes a PR URL as input, analyzes the changes, and generates comprehensive review feedback from different perspectives (Merge Specialist, Frontend, Backend, Security, DevOps, AI/Agent, SRE, Chief Architect).
Comprehensive Review PR Enhance
2krmyndharis/antigravity-skills
Create high-quality pull requests with comprehensive descriptions, automated review checks, and a size and structure that keep them easy to review. Use when preparing or improving a pull request.
Springboot Verification
2kxu-xiang/everything-claude-code-zh
Spring Boot 项目的验证循环:构建、静态分析、带有覆盖率的测试、安全扫描以及发布或 PR 前的差异审查。
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.