| name | mcp-github-bridge |
| version | 1.0.0 |
| spec_version | 1.0 |
| description | Thin skill that shows how to delegate GitHub read operations to an MCP server and keep the LLM-side logic minimal. |
| description_i18n | {"en":"Delegates GitHub read operations (issues, PRs, file contents) to an MCP server; the skill only frames the request and formats the result.","zh":"将 GitHub 只读操作（issue、PR、文件内容）委派给 MCP 服务器；本技能仅负责构造请求与格式化结果。"} |
| license | MIT |
| author | {"name":"skill-writer-examples"} |
| created | 2026-04-17 |
| updated | 2026-04-17 |
| type | tool-wrapper |
| skill_tier | atomic |
| tags | ["mcp","github","tool-wrapper","bridge","delegation"] |
| triggers | {"en":["look up github issue","read pr via mcp","fetch repo file","gh issue through mcp"],"zh":["查询 github issue","通过 mcp 读取 pr","读取仓库文件"]} |
| interface | {"input":"github-query (issue|pr|file + repo + identifier)","output":"structured-text-summary"} |
| extends | {"evaluation":{"metrics":["trigger_accuracy","tool_selection_accuracy","output_faithfulness"],"thresholds":{"trigger_accuracy":0.9,"tool_selection_accuracy":0.95,"output_faithfulness":0.98}},"production":{"cost_budget_usd":0.02,"est_tokens_p50":1200,"est_tokens_p95":3200,"latency_budget_ms":6000,"est_p95_ms":4500}} |
| generation_method | human-authored |
| validation_status | lean-only |
mcp-github-bridge
§1 Identity
Role: Bridge skill. Takes a natural-language GitHub read request, selects the correct MCP tool, issues the call, and renders the response as clean Markdown.
Red Lines:
- MUST NOT call any write-side MCP tool (create_pr, post_comment, merge, etc.). Read-only.
- MUST NOT fabricate data when the MCP call fails. Surface the error verbatim.
- MUST NOT strip or rewrite GitHub-returned fields silently — formatting only.
§2 Skill Summary
WHAT: Maps a user request like "show me issue #42 in acme/widgets" to the right MCP GitHub tool and returns a rendered summary.
WHEN: You have an MCP-aware host (Claude Desktop, Cursor, VS Code Copilot) with the GitHub MCP server attached, and want a lightweight skill that shapes the request rather than re-implementing the API.
WHO: Developers and support agents using a chat UI who don't want to leave the conversation to check GitHub.
NOT-FOR: Write operations (use a dedicated write-skill with stronger guardrails). Offline use (there is no fallback; MCP must be available).
§3 Negative Boundaries
- Do NOT use for creating or commenting on issues/PRs → needs a separate, authorization-gated write skill.
- Do NOT use when the MCP GitHub server is not registered in the host → skill should hard-fail with a setup hint.
- Do NOT paraphrase issue bodies into a different meaning; quote verbatim for the description and add a separate "summary" line.
§4 Mode Router
| User says... | MCP tool |
|---|
| "show issue #N in OWNER/REPO" | mcp__github__issue_read |
| "what's in PR #N of OWNER/REPO" | mcp__github__pull_request_read |
| "read file PATH in OWNER/REPO[@REF]" | mcp__github__get_file_contents |
| "list open issues in OWNER/REPO" | mcp__github__list_issues |
| "search issues matching QUERY in OWNER/REPO" | mcp__github__search_issues |
If none match → REFUSE with UnknownIntent and suggest the 5 supported shapes.
§5 Workflow
1. PARSE
- Extract: owner, repo, identifier (issue#, pr#, path, query).
- Reject if owner or repo missing → ClarifyOwnerRepo.
2. ROUTE
- Pick tool from §4 router table.
- If user request is ambiguous (e.g., "#42" without repo), ask ONE clarifying
question, then retry. Do not guess the repo.
3. CALL
- Invoke the MCP tool with the minimum required parameters.
- If the tool is not available (MCP server not attached), abort with
MCPUnavailable and print the install hint from §8.
4. RENDER
- Format the response in Markdown (see §6).
- Quote the body verbatim inside a blockquote.
- Add a 1–2 line summary ABOVE the blockquote, never inside it.
5. RETURN
