Rescope from Copilot-branded to an industry-standard, tool-neutral plugin marketplace

[devantler]

🤖 Generated by the Daily AI Assistant

Context. The repo was renamed copilot-plugins → plugins (the old URL redirects). It already supports VS Code, GitHub Copilot CLI, and Claude Code via dual manifests, so the old name under-sold it. This issue tracks finishing the scope change to a genuinely tool-neutral, industry-standard plugin marketplace.

Problem. Naming and framing are still Copilot-centric even though the marketplace is cross-tool.

Proposed direction

• De-Copilot-brand the surface: README.md ("A copilot-plugin marketplace…" → tool-neutral "agent-plugin marketplace"), and the .claude-plugin/marketplace.json name (devantler-copilot-plugins → devantler-plugins) + any Copilot-specific wording. Keep relative source paths (rename-safe).
• State supported tools/standards explicitly and keep manifests in sync (VS Code, Copilot CLI, Claude Code today).
• Evaluate broadening to additional industry standards — most notably MCP (the emerging cross-tool standard for extending agents) — and decide whether plugins should expose/bundle MCP servers alongside skill bundles. Design decision; capture as an ADR if non-trivial.
• Keep it a thin, additive bundler over devantler-tech/skills (single source of skills).

Acceptance criteria

• No Copilot-specific branding in name/README/manifest where the capability is actually cross-tool.
• Documented, in-sync manifests for each supported tool; install instructions per tool.
• A decision recorded on whether/how to support MCP (and any other standard).

Rough size: M (docs + manifest reframe is S; the MCP/standards evaluation is the larger part).