---
id: daily-integrate-context-matic
name: "integrate-context-matic"
url: https://skills.yangsir.net/skill/daily-integrate-context-matic
author: github
domain: ai-agent-external-interaction
tags: ["api", "integration", "mcp", "context", "automation"]
install_count: 1100
rating: 4.30 (6 reviews)
github: https://github.com/github/awesome-copilot
---

# integrate-context-matic

> 引导第三方 API 或服务集成到 ContextMatic MCP 的完整流程，包含认证、配置和测试

**Stats**: 1,100 installs · 4.3/5 (6 reviews)

## Before / After 对比

### 自动化 API 集成准备

**Before**:

在没有 `integrate-context-matic` 技能时，当需要集成第三方 API 时，开发者必须手动执行一系列繁琐的准备工作。这包括人工识别项目的编程语言，然后耗时地检查工作区中是否存在语言特定的安全、测试指南以及编码规范。如果缺失，开发者需要手动创建、查找或适配这些文件和技能。接着，为了找到合适的 API，开发者需要自行浏览大量文档、搜索外部服务或内部注册表，整个过程耗时且容易遗漏关键信息，导致集成前期准备效率低下且不一致，增加了项目启动的复杂性。

**After**:

通过 `integrate-context-matic` 技能，API 集成前的准备工作被彻底自动化。系统首先智能检测项目的编程语言，随后自动检查并确保所有必要的语言特定指南（如安全、测试）和编码规范（如 `{language}-conventions`）都已存在。如果发现任何缺失，技能会自动调用 `add_guidelines` 或 `add_skills` 进行生成，确保项目环境的标准化和一致性。最后，它通过 `fetch_api` 自动发现可用的 API 列表，提供名称、描述和 `key`，极大地简化了 API 选择和集成启动流程，显著提升了效率和准确性。

| Metric | Before | After | Change |
|---|---|---|---|
| API 集成准备时间 | 240分钟 | 15分钟 | -93.75% |
| 项目规范遵循度 | 60% | 95% | +58.33% |

## Readme

# 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.

- Provide the `language` parameter using the language detected in step 1a.

- The response returns available APIs with their names, descriptions, and `key` values.

- 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.

- **model_search** — look up a model/object definition.

Provide: `language`, `key`, and an exact or partial case-sensitive model name as `query` (e.g. `availableBalance`, `TransactionId`).

- **endpoint_search** — look up an endpoint method's details.

Provide: `language`, `key`, and an exact or partial case-sensitive method name as `query` (e.g. `createUser`, `get_account_balance`).

### 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_guidelines` called if guideline files were missing, otherwise skipped

-  `add_skills` called if `{language}-conventions` was missing, otherwise skipped

-  `fetch_api` called with correct `language` for the project

-  Correct `key` identified for the requested API (or user informed if not found)

-  `update_activity` called only when a milestone is concretely reached in code/infrastructure — never for questions, searches, or tool lookups

-  `update_activity` called with the appropriate `milestone` at each integration milestone

-  `ask` used for integration guidance and code samples

-  `model_search` / `endpoint_search` used 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_api` is API discovery, not integration — do not call `update_activity` before it.

Weekly Installs518Repository[github/awesome-copilot](https://github.com/github/awesome-copilot)GitHub Stars29.6KFirst Seen12 days agoSecurity Audits[Gen Agent Trust HubPass](/github/awesome-copilot/integrate-context-matic/security/agent-trust-hub)[SocketWarn](/github/awesome-copilot/integrate-context-matic/security/socket)[SnykPass](/github/awesome-copilot/integrate-context-matic/security/snyk)Installed onopencode475codex473github-copilot472gemini-cli472deepagents469antigravity469

---
*Source: https://skills.yangsir.net/skill/daily-integrate-context-matic*
*Markdown mirror: https://skills.yangsir.net/api/skill/daily-integrate-context-matic/markdown*