Re: [MENTORS] Potential issue with GitHub releases

Hi,

Thanks, Jakub. This is a really useful perspective. You're right that SKILLs have some real advantages: zero install friction, full transparency, repo-local versioning, and composability with the agent's own reasoning. For a developer workflow those are compelling.

For IncubatorMCP specifically, I ended up on MCP for a few reasons:
- The tools need live data (ASF roster, mail archives, release artifacts). A SKILL could embed those HTTP calls directly, but the logic gets verbose fast.
- The IPMC audience is not necessarily a dev team running agentic CLI sessions. Claude Desktop with a copy-paste JSON config felt like a lower bar than "install Claude CLI, clone a repo."
- MCP works across clients (Claude Desktop, Claude.ai remote MCP, anything MCP-compatible) without tying the workflow to a specific CLI.

That said, the hybrid idea is interesting. Some of the stateless analytical tools (graduation readiness, report summaries) could work well as SKILLs that wrap the public ASF APIs directly, while the live-data tools stay as MCP.

Kind Regards,
Justin