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