Integrate Context Matic
Discover and wire third-party APIs with the context-matic MCP server instead of guessing SDK shapes from model memory.
Overview
Integrate Context Matic is an agent skill for the Build phase that discovers and implements third-party APIs using context-matic MCP tools instead of unchecked model knowledge.
Install
npx skills add https://github.com/github/awesome-copilot --skill integrate-context-maticWhat is this skill?
- Mandates context-matic MCP tools (fetch_api, ask, model_search, endpoint_search)—not model guesswork
- Detects primary language via csproj, package.json, go.mod, pyproject, and similar workspace signals
- Ensures language-specific guidelines and skills exist before integration steps
- Applies when users name PayPal, Twilio, or any third-party API implementation request
- Structured workflow from API discovery through SDK-aware implementation guidance
Adoption & trust: 878 installs on skills.sh; 34.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need a external API wired in, but the agent might invent endpoints, SDK versions, or auth flows that do not match the vendor.
Who is it for?
Solo builders adding vendor SDKs in typed or polyglot repos who already run or can enable the context-matic MCP server.
Skip if: Purely internal APIs with no third-party SDK, or teams forbidden from MCP network discovery during coding sessions.
When should I use this skill?
User asks to integrate a third-party API, add an API client, implement features with an external API, or work with any third-party API or SDK.
What do I get? / Deliverables
You get MCP-backed API discovery, SDK search, and integration guidance aligned to your detected project language before implementation proceeds.
- Language-detected integration plan grounded in MCP API/SDK search
- Implementation steps or code aligned to discovered endpoints and models
Recommended Skills
Journey fit
External API clients belong in Build when you implement product features against real vendor surfaces. The workflow centers on fetch_api, ask, model_search, and endpoint_search—integration discovery and implementation guidance.
How it compares
Use as an MCP-guided integration workflow—not a substitute for reading official vendor security and compliance docs yourself.
Common Questions / FAQ
Who is integrate-context-matic for?
Developers and indie builders using GitHub Copilot-class agents who integrate external APIs and want context-matic to ground SDK and endpoint facts.
When should I use integrate-context-matic?
In Build (integrations) when the user asks to integrate a third-party API, add an SDK client, or implement features that depend on an external service.
Is integrate-context-matic safe to install?
It steers agents toward MCP lookups but still touches external APIs; review the Security Audits panel on this Prism page and restrict secrets and network policy in your environment.
SKILL.md
READMESKILL.md - Integrate Context Matic
# API Integration When the user asks to integrate a third-party API or implement anything involving an external API or SDK, follow this workflow. Do not rely on your own knowledge for available APIs or their capabilities — always use the context-matic MCP server. ## When to Apply Apply this skill when the user: - Asks to integrate a third-party API - Wants to add a client or SDK for an external service - Requests implementation that depends on an external API - Mentions a specific API (e.g. PayPal, Twilio) and implementation or integration ## Workflow ### 1. Ensure Guidelines and Skills Exist #### 1a. Detect the Project's Primary Language Before checking for guidelines or skills, identify the project's primary programming language by inspecting the workspace: | File / Pattern | Language | |---|---| | `*.csproj`, `*.sln` | `csharp` | | `package.json` with `"typescript"` dep or `.ts` files | `typescript` | | `requirements.txt`, `pyproject.toml`, `*.py` | `python` | | `go.mod`, `*.go` | `go` | | `pom.xml`, `build.gradle`, `*.java` | `java` | | `Gemfile`, `*.rb` | `ruby` | | `composer.json`, `*.php` | `php` | Use the detected language in all subsequent steps wherever `language` is required. #### 1b. Check for Existing Guidelines and Skills Check whether guidelines and skills have already been added for this project by looking for their presence in the workspace. - `{language}-conventions` is the skill produced by **add_skills**. - `{language}-security-guidelines.md` and `{language}-test-guidelines.md` are language-specific guideline files produced by **add_guidelines**. - `update-activity-workflow.md` is a workflow guideline file produced by **add_guidelines** (it is not language-specific). - Check these independently. Do not treat the presence of one set as proof that the other set already exists. - **If any required guideline files for this project are missing:** Call **add_guidelines**. - **If `{language}-conventions` is missing for the project's language:** Call **add_skills**. - **If all required guideline files and `{language}-conventions` already exist:** Skip this step and proceed to step 2. ### 2. Discover Available APIs Call **fetch_api** to find available APIs — always start here. - Always provide the `language` parameter using the language detected in step 1a. - Always provide the `key` parameter: pass the API name/key from the user's request (e.g. `"paypal"`, `"twilio"`). - If the user did not provide an API name/key, ask them which API they want to integrate, then call `fetch_api` with that value. - The tool returns only the matching API on an exact match, or the full API catalog (name, description, and `key`) when there is no exact match. - Identify the API that matches the user's request based on the name and description. - Extract the correct `key` for the user's requested API before proceeding. This key will be used for all subsequent tool calls related to that API. **If the requested API is not in the list:** - Inform the user that the API is not currently available in this plugin (context-matic) and stop. - Request guidance from user on how to proceed with the API's integration. ### 3. Get Integration Guidance - 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?"_ ### 4. Look Up SDK Models and Endpoints (as needed) These tools return definitions only — they do not call APIs or generate code.