Onboard Context Matic
Take a guided, interactive tour of the context-matic MCP server—APIs, live searches, and what to ask next—before you integrate anything.
Overview
Onboard Context-Matic is an agent skill most often used in Build (also Validate discover, Build integrations) that runs an interactive context-matic MCP tour with live model and endpoint search demos.
Install
npx skills add https://github.com/github/awesome-copilot --skill onboard-context-maticWhat is this skill?
- Multi-phase interactive tour: explain server purpose, list APIs, user picks one to explore
- Live demonstrations of model_search and endpoint_search via context-matic MCP tools
- Agent conduct rules: no narrating phase numbers; announce every tool call before executing
- Ends with a menu of follow-up tasks the user can request from the agent
- Explicit DO NOT USE for end-to-end API integration—hand off to integrate-context-matic instead
- Live demonstration of model_search and endpoint_search during the tour
- Multi-phase tour with explicit wait-for-user interaction points
Adoption & trust: 839 installs on skills.sh; 34.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You connected context-matic MCP but do not know which APIs it exposes or how to explore endpoints before committing to an integration.
Who is it for?
First-time context-matic MCP users who want a patient, tool-annotated tour before writing integration code.
Skip if: Builders who already know their target API and need full repo integration in one session—use integrate-context-matic instead.
When should I use this skill?
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".
What do I get? / Deliverables
You finish a guided tour with a chosen API context, seen live search demonstrations, and a clear menu of next steps—then invoke integrate-context-matic when you are ready to wire code end-to-end.
- Completed conversational tour of context-matic capabilities
- User-selected API area explored with live search demonstrations
- Action menu of follow-up requests tailored to the user’s project
Recommended Skills
Journey fit
First-time MCP onboarding is agent-tooling setup during Build, even though the same tour helps when validating which external API to adopt. The skill orchestrates phased conversation, MCP tool calls, and menu-driven exploration—not shipping code or production monitoring.
How it compares
Onboarding tour and MCP capability discovery—not a substitute for the integrate-context-matic end-to-end wiring skill.
Common Questions / FAQ
Who is onboard-context-matic for?
Solo builders and indie devs who just added the context-matic MCP server and want a structured first-run explanation without jumping straight into code changes.
When should I use onboard-context-matic?
At Build agent-tooling setup when you ask what the MCP does or want a tour; at Validate discover when comparing external APIs; before integrations when you need endpoint_search demos in your project language.
Is onboard-context-matic safe to install?
It drives read-oriented MCP exploration and live searches; review the Security Audits panel on this Prism page and confirm MCP network scopes match what you expect before connecting production credentials.
Workflow Chain
Then invoke: integrate context matic
SKILL.md
READMESKILL.md - Onboard Context Matic
# Onboarding: ContextMatic MCP This skill delivers a guided, interactive tour of the `context-matic` MCP server. Follow every phase in order. Stop after each interaction point and wait for the user's reply before continuing. > **Agent conduct rules — follow throughout the entire skill:** > - **Never narrate the skill structure.** Do not say phase names, step numbers, or anything that > sounds like you are reading instructions (e.g., "In Phase 1 I will…", "Step 1a:", "As per the > skill…"). Deliver the tour as a natural conversation. > - **Announce every tool call before making it.** One short sentence is enough — tell the user > what you are about to look up and why, then call the tool. Example: *"Let me pull up the list > of available APIs for your project language."* This keeps the user informed and prevents > silent, unexplained pauses. --- ## Phase 0 — Opening statement and tool walkthrough Begin with a brief, plain-language explanation of what the server does. Say it in your own words based on the following facts: > The **context-matic** 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. After explaining the problem the server solves, walk through each of the four tools as if introducing them to someone using the server for the first time. For each tool, explain: - **What it is** — give it a memorable one-line description - **When you would use it** — a concrete, relatable scenario - **What it gives back** — the kind of output the user will see Use the following facts as your source, but say it conversationally — do not present a raw table: > | Tool | What it does | When to use it | What you get back | > |---|---|---|---| > | `fetch_api` | Returns an exact match for an API `key`/identifier and language, or lists all APIs for a given language. The `key` is the machine-readable identifier returned by `fetch_api` (for example, `paypal`), not the human-readable display name (for example, "PayPal Server SDK"). | "What APIs can I use?" / Starting a new project / "Do you have the PayPal SDK?" | A named list of available APIs with short descriptions (full catalog), or one exact API match when you provide its identifier/key and language | > | `ask` | Answers integration questions with version-accurate guidance and code samples | "How do I authenticate?", "Show me the quickstart", "What's the right way to do X?" | Step-by-step guidance and runnable code samples grounded in the actual SDK version | > | `model_search` | Looks up an SDK model/object definition and its typed properties | "What fields does an Order have?", "Is this property required?" | The model's name, description, and a full typed property list (required vs. optional, nested types) | > | `endpoint_search` | Looks up an endpoint method, its parameters, response type, and a runnable code sample | "Show me how to call createOrder", "What does getTrack return?" | Method signature, parameter types, respon