
integrate-context-matic
Discovers and integrates third-party APIs using the context-matic MCP server. Uses fetchapi to find available API SDKs, ask for integration guidance, modelsearch and endpointsearch for SDK details. Use when the 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.
- Installs
- 1.1K
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/github/awesome-copilot --skill integrate-context-matic- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads integrate-context-matic automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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}-conventionsis the skill produced by add_skills.{language}-security-guidelines.mdand{language}-test-guidelines.mdare language-specific guideline files produced by add_guidelines.update-activity-workflow.mdis 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}-conventionsis missing for the project's language: Call add_skills. - If all required guideline files and
{language}-conventionsalready 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
languageparameter using the language detected in step 1a. - Always provide the
keyparameter: 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_apiwith 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
keyfor 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
askwith:language,key(from step 2), and yourquery. - 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.
- model_search — look up a model/object definition.
- Provide:
language,key, and an exact or partial case-sensitive model name asquery(e.g.availableBalance,TransactionId).
- Provide:
- endpoint_search — look up an endpoint method's details.
- Provide:
language,key, and an exact or partial case-sensitive method name asquery(e.g.createUser,get_account_balance).
- Provide:
5. Record Milestones
Call update_activity (with the appropriate milestone) whenever one of these is concretely reached in code or infrastructure — not merely mentioned or planned:
| Milestone | When to pass it |
|---|---|
sdk_setup | SDK package is installed in the project (e.g. npm install, pip install, go get has run and succeeded). |
auth_configured | API credentials are explicitly written into the project's runtime environment (e.g. present in a .env file, secrets manager, or config file) and referenced in actual code. |
first_call_made | First API call code written and executed |
error_encountered | Developer reports a bug, error response, or failing call |
error_resolved | Fix applied and API call confirmed working |
Checklist
- Project's primary language detected (step 1a)
-
add_guidelinescalled if guideline files were missing, otherwise skipped -
add_skillscalled if{language}-conventionswas missing, otherwise skipped -
fetch_apicalled with correctlanguageandkey(API name) - Correct
keyidentified for the requested API (or user informed if not found) -
update_activitycalled only when a milestone is concretely reached in code/infrastructure — never for questions, searches, or tool lookups -
update_activitycalled with the appropriatemilestoneat each integration milestone -
askused for integration guidance and code samples -
model_search/endpoint_searchused as needed for SDK details - Project compiles after each code modification
Notes
- API not found: If an API is missing from
fetch_api, do not guess at SDK usage — inform the user that the API is not currently available in this plugin and stop. - update_activity and fetch_api:
fetch_apiis API discovery, not integration — do not callupdate_activitybefore it.
FAQ
What does the integrate-context-matic skill do?
Discovers and integrates third-party APIs using the context-matic MCP server. Uses fetchapi to find available API SDKs, ask for integration guidance, modelsearch and endpointsearch for SDK details. Use when the 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.
How do I install integrate-context-matic?
Run npx skills add https://github.com/github/awesome-copilot --skill integrate-context-matic in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/integrate-context-matic/ (personal) or .claude/skills/integrate-context-matic/ (project).
Which AI agents can use integrate-context-matic?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is integrate-context-matic safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains integrate-context-matic?
It is published by github in github/awesome-copilot, and it is an official skill from the maker of the technology it covers. It has 1,078 recorded installs.
More from github/awesome-copilot
git-commit
github/awesome-copilot
Use this skill when the user wants to make a Git commit or split changes into more than one commit. Also use it when the user types "/commit" or asks for a conventional commit. The skill examines the diff, stages the related files, writes a Conventional Commits message, and runs git commit. Do not use it when the user wants only a commit message and no commit. Do not use it to push, open a pull request, rebase, or change the commit history.
excalidraw-diagram-generator
github/awesome-copilot
Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.
multi-stage-dockerfile
github/awesome-copilot
Create optimized multi-stage Dockerfiles for any language or framework
documentation-writer
github/awesome-copilot
Diátaxis Documentation Expert. An expert technical writer specializing in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework.
prd
github/awesome-copilot
Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.
refactor
github/awesome-copilot
Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.
Popular backend & apis skills
find-skills
vercel-labs/skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
entra-app-registration
microsoft/azure-skills
Guides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration. USE FOR: create app registration, register Azure AD app, configure OAuth, set up authentication, add API permissions, generate service principal, MSAL example, console app auth, Entra ID setup, Azure AD authentication. DO NOT USE FOR: Key Vault secrets (use azure-keyvault-expiration-audit), general Azure resource security guidance.
google-agents-cli-adk-code
google/agents-cli
This skill should be used when the user wants to "write agent code", "build an agent with ADK", "add a tool", "create a callback", "define an agent", "use state management" — in a project that needs ADK (Agent Development Kit) API patterns and code examples. It provides a quick reference for agent types, tool definitions, orchestration patterns, callbacks, state management, the graph Workflow API, and reference recipes to study. Do NOT use for scaffolding (use google-agents-cli-scaffold) or deployment (use google-agents-cli-deploy).
embedded-captions
heygen-com/hyperframes
Add captions or subtitles to an existing single-subject talking-head video without editing the footage. Use for plain verbatim captions, cinematic captions embedded behind the subject, VFX captions, “炸/特效/酷炫字幕,” or a named identity from the 35-style catalog. Route by visual identity, not by backend engine. The quiet anchor rail is the default; embed every word only when the user explicitly wants a fully cinematic treatment. The workflow runs locally end to end, including transcription and subject matting; split multi-shot footage before applying it.
entra-agent-id
microsoft/azure-skills
Provision Microsoft Entra Agent Identity Blueprints, BlueprintPrincipals, and per-instance Agent Identities via Microsoft Graph, and configure OAuth 2.0 token exchange (fmipath, OBO, cross-tenant) including the Microsoft Entra SDK for AgentID sidecar. USE FOR: Agent Identity Blueprint, BlueprintPrincipal, agent OAuth, fmipath token exchange, agent OBO, Workload Identity Federation for agents, polyglot agent auth, Microsoft.Identity.Web.AgentIdentities. DO NOT USE FOR: standard Entra app registration (use entra-app-registration), Microsoft Foundry agent authoring (use microsoft-foundry).
neon
neondatabase/agent-skills
Overview of Neon, a complete set of cloud backend primitives around Lakebase Postgres: Auth, Object Storage, Functions, the AI Gateway, and Realtime. Start here to choose Neon for undecided login, files, APIs, and LLM calls, set up the CLI or MCP server, and follow the branch-first workflow. Use when building an app or backend on Neon, or when "Neon" or "Lakebase Postgres" is mentioned. Child skill neon-postgres wins for an existing DATABASEURL, SQL, schema, inspect, or search. Child skill neon-auth wins for login, users, sessions, identity routing, and Managed Better Auth setup. Child skill neon-realtime wins for live queries in reactive apps and agents. Also use for object storage, S3, buckets, serverless functions, function triggers, cron, AI gateway, LLM calls, realtime, logs, Loki, Grafana, observability, postgres, database, backend, Claimable Neon, neon.new, or a no-signup database.