René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Support external repository sources for plugins (don't require content to live in this repo)","articleBody":"## Problem\n\n`marketplace.json` requires all plugin content to live inside this repo via relative paths. This forces plugin authors to duplicate content here rather than pointing to their canonical source repo.\n\n## Use Case\n\nWe maintain [AzureCosmosDB/cosmosdb-agent-kit](https://github.com/AzureCosmosDB/cosmosdb-agent-kit) - 57+ Cosmos DB best-practice rules in the standard skill format (SKILL.md + AGENTS.md). The same skill is consumed by Claude Code, Gemini CLI, Cursor, and other agents via [Agent Skills](https://agentskills.io/). We want it discoverable through this registry without duplicating content that would drift from the source.\n\n## Proposal\n\nSupport a `repository` field in `marketplace.json` that points to an external GitHub repo:\n\n```json\n{\n  \"name\": \"cosmosdb-best-practices\",\n  \"repository\": \"AzureCosmosDB/cosmosdb-agent-kit\",\n  \"path\": \"skills/cosmosdb-best-practices\",\n  \"description\": \"Azure Cosmos DB best practices — 57+ rules for data modeling, partitioning, queries, SDK patterns, and more.\",\n  \"version\": \"1.0.0\"\n}\n```\n\nThis is the same pattern used by npm, Homebrew, and the VS Code Marketplace - the registry indexes, the external repo provides content. The `workiq` plugin already does this for its MCP server (`npx @microsoft/workiq`), so the precedent exists for skills too.\n\n## Happy to Help\n\nWe can submit a PR, help define the schema, and serve as a test case once this is supported.","author":{"url":"https://github.com/TheovanKraay","@type":"Person","name":"TheovanKraay"},"datePublished":"2026-02-17T16:13:35.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/15/copilot-plugins/issues/15"}