Conversation
There was a problem hiding this comment.
Pull request overview
Adds a new ContextMatic plugin to Awesome Copilot, providing an MCP server configuration plus two skills (onboarding + integration) and registering the plugin/skills in the repository’s generated docs and marketplace metadata.
Changes:
- Introduces two new skills:
/integrate-context-maticand/onboard-context-matic. - Adds a new
plugins/context-matic/plugin with README, MCP server config, and plugin metadata. - Updates skills/plugins indices and marketplace listing to include the new additions.
Reviewed changes
Copilot reviewed 8 out of 8 changed files in this pull request and generated 7 comments.
Show a summary per file
| File | Description |
|---|---|
| skills/onboard-context-matic/SKILL.md | New interactive onboarding/tour skill for the ContextMatic MCP server. |
| skills/integrate-context-matic/SKILL.md | New workflow skill intended to guide end-to-end third-party API integration via ContextMatic tools. |
| plugins/context-matic/README.md | Plugin documentation describing tools, supported APIs, and usage examples. |
| plugins/context-matic/.mcp.json | MCP server registration/config for the plugin. |
| plugins/context-matic/.github/plugin/plugin.json | Plugin metadata (name/description/version/keywords/skill references). |
| docs/README.skills.md | Adds the two new skills to the skills index table. |
| docs/README.plugins.md | Adds the new plugin to the plugins index table. |
| .github/plugin/marketplace.json | Registers the plugin in the marketplace list used by tooling/CI. |
| Call **update_activity** immediately before calling **ask**. | ||
|
|
||
| - Provide `ask` with: `language`, `key` (from step 2), and your `query`. | ||
| - Break complex questions into smaller focused queries for best results: | ||
| - _"How do I authenticate?"_ | ||
| - _"How do I create a payment?"_ | ||
| - _"What are the rate limits?"_ | ||
| - Call **update_activity** immediately before generating or fixing code. | ||
|
|
||
| ### 4. Look Up SDK Models and Endpoints (as needed) | ||
|
|
||
| These tools return definitions only — they do not call APIs or generate code. | ||
|
|
||
| Call **update_activity** immediately before each call. |
There was a problem hiding this comment.
The skill requires update_activity before/around tool calls, but update_activity isn’t documented as an available ContextMatic tool in the plugin README. If it’s not provided by the MCP server, this will cause runtime failures—either remove this requirement or document/validate the tool as part of the plugin.
| Call **update_activity** immediately before calling **ask**. | |
| - Provide `ask` with: `language`, `key` (from step 2), and your `query`. | |
| - Break complex questions into smaller focused queries for best results: | |
| - _"How do I authenticate?"_ | |
| - _"How do I create a payment?"_ | |
| - _"What are the rate limits?"_ | |
| - Call **update_activity** immediately before generating or fixing code. | |
| ### 4. Look Up SDK Models and Endpoints (as needed) | |
| These tools return definitions only — they do not call APIs or generate code. | |
| Call **update_activity** immediately before each call. | |
| Use **ask** to get high-level integration guidance and best practices for the selected API. | |
| - Provide `ask` with: `language`, `key` (from step 2), and your `query`. | |
| - Break complex questions into smaller focused queries for best results: | |
| - _"How do I authenticate?"_ | |
| - _"How do I create a payment?"_ | |
| - _"What are the rate limits?"_ | |
| - Before generating or fixing code, ensure your query clearly describes the current context (existing code, framework, and desired change). | |
| ### 4. Look Up SDK Models and Endpoints (as needed) | |
| These tools return definitions only — they do not call APIs or generate code. | |
| Use these tools when you need structural details about models or endpoints for the selected API. |
| description: > | ||
| Interactive onboarding tour for the context-matic MCP server. Walks the user through what the | ||
| server does, shows all available APIs, lets them pick one to explore, explains it in their project | ||
| language, demonstrates model_search and endpoint_search live, and ends with a menu of things | ||
| the user can ask the agent to do. USE FOR: first-time setup; "what can this MCP do?"; "show me | ||
| the available APIs"; "onboard me"; "how do I use the context-matic server"; "give me a tour". | ||
| DO NOT USE FOR: actually integrating an API end-to-end (use integrate-context-matic instead). |
There was a problem hiding this comment.
Frontmatter description should follow the established skills pattern of a single quoted string (e.g., skills/noob-mode/SKILL.md uses description: '...') rather than a folded multiline block. This keeps skill metadata consistent and avoids unexpected formatting in generated docs.
| description: > | |
| Interactive onboarding tour for the context-matic MCP server. Walks the user through what the | |
| server does, shows all available APIs, lets them pick one to explore, explains it in their project | |
| language, demonstrates model_search and endpoint_search live, and ends with a menu of things | |
| the user can ask the agent to do. USE FOR: first-time setup; "what can this MCP do?"; "show me | |
| the available APIs"; "onboard me"; "how do I use the context-matic server"; "give me a tour". | |
| DO NOT USE FOR: actually integrating an API end-to-end (use integrate-context-matic instead). | |
| description: 'Interactive onboarding tour for the context-matic MCP server. Walks the user through what the server does, shows all available APIs, lets them pick one to explore, explains it in their project language, demonstrates model_search and endpoint_search live, and ends with a menu of things the user can ask the agent to do. USE FOR: first-time setup; "what can this MCP do?"; "show me the available APIs"; "onboard me"; "how do I use the context-matic server"; "give me a tour". DO NOT USE FOR: actually integrating an API end-to-end (use integrate-context-matic instead).' |
| > The **api-context-plugins** MCP server solves a fundamental problem with AI-assisted coding: general | ||
| > models are trained on public code that is often outdated, incorrect, or missing entirely for newer | ||
| > SDK versions. This server acts as a **live, version-aware grounding layer**. Instead of the agent | ||
| > guessing at SDK usage from training data, it queries the server for the *exact* SDK models, | ||
| > endpoints, auth patterns, and runnable code samples that match the current API version and the | ||
| > project's programming language. |
There was a problem hiding this comment.
This section describes the server as the "api-context-plugins" MCP server, but this skill/plugin is for the context-matic server. Update the wording to avoid confusing users about which MCP server they’re onboarding for.
| /integrate-api-context-plugins Set up the Spotify TypeScript SDK and fetch my top 5 tracks. | ||
| Show me the complete client initialization and the API call. |
There was a problem hiding this comment.
The example prompts reference /integrate-api-context-plugins, but this plugin’s integration skill is /integrate-context-matic (and there’s no integrate-api-context-plugins skill added in this PR). Replace the command here (and in the rest of this menu section) so users don’t try a non-existent slash command.
| Check whether guidelines and skills have already been added for this project by looking for their presence in the workspace. Check for existing skill and guideline files, e.g., `{language}-conventions`, `{language}-security-guidelines.md`, `{language}-test-guidelines.md`, `update-activity-workflow.md`, or prior output from `add_guidelines` and `add_skills`. | ||
|
|
||
| - **If they do not exist for the project's language:** Call **add_guidelines** and **add_skills** to create them. This sets up the necessary skills and guidelines for the MCP server to work correctly. |
There was a problem hiding this comment.
This workflow tells the agent to call add_guidelines and add_skills, but the plugin README only documents four ContextMatic tools (fetch_api, ask, model_search, endpoint_search). If add_guidelines/add_skills aren’t actually available from the MCP server, these steps will fail—please remove them or update the plugin docs/tooling accordingly.
| Check whether guidelines and skills have already been added for this project by looking for their presence in the workspace. Check for existing skill and guideline files, e.g., `{language}-conventions`, `{language}-security-guidelines.md`, `{language}-test-guidelines.md`, `update-activity-workflow.md`, or prior output from `add_guidelines` and `add_skills`. | |
| - **If they do not exist for the project's language:** Call **add_guidelines** and **add_skills** to create them. This sets up the necessary skills and guidelines for the MCP server to work correctly. | |
| Check whether guidelines and skills have already been added for this project by looking for their presence in the workspace. Check for existing skill and guideline files, e.g., `{language}-conventions`, `{language}-security-guidelines.md`, `{language}-test-guidelines.md`, `update-activity-workflow.md`, or other previously generated language-specific guidelines and skills. | |
| - **If they do not exist for the project's language:** Create or follow appropriate language-specific guidelines and skills for the project (for example, adding convention, security, and testing guideline documents) so that future API integration work can reference them. |
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Pull Request Checklist
npm startand verified thatREADME.mdis up to date.stagedbranch for this pull request.Description
Type of Contribution
Additional Notes
By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.