@vapi-ai/mcp-server 0.0.11 → 0.2.0

package/README.md

@@ -1,103 +1,47 @@
 # Vapi MCP Server
 
-[![smithery badge](https://smithery.ai/badge/@VapiAI/vapi-mcp-server)](https://smithery.ai/server/@VapiAI/vapi-mcp-server)
+Build AI voice assistants and phone agents with [Vapi](https://vapi.ai) from any agent or app that speaks the [Model Context Protocol](https://modelcontextprotocol.com/).
 
-Build AI voice assistants and phone agents with [Vapi](https://vapi.ai) using the [Model Context Protocol](https://modelcontextprotocol.com/).
+## Connect to the hosted server
 
-<a href="https://glama.ai/mcp/servers/@VapiAI/mcp-server">
-  <img width="380" height="200" src="https://glama.ai/mcp/servers/@VapiAI/mcp-server/badge" alt="Vapi Server MCP server" />
-</a>
+**You don't need to clone, install or run anything.** Vapi hosts this server for you:
 
-## Setup
+- **URL:** `https://mcp.vapi.ai/mcp` (Streamable HTTP)
+- **Header:** `Authorization: Bearer YOUR_VAPI_API_KEY`
 
-The MCP server requires a Vapi API key. Get one from the [Vapi dashboard](https://dashboard.vapi.ai/org/api-keys).
+Get an API key from the [Vapi dashboard](https://dashboard.vapi.ai/org/api-keys).
 
-### Local Server (stdio)
+👉 **[Step-by-step setup for Codex, Claude Code, Cursor, VS Code, Hermes and Claude Desktop](https://docs.vapi.ai/sdk/mcp-server#connect-your-agent)**
 
-Configure any MCP client that supports local stdio servers to run:
+The two most common setups:
 
-```text
-npx -y @vapi-ai/mcp-server
-```
-
-Set `VAPI_TOKEN` in the server environment. MCP client configuration formats vary, but the server definition generally looks like this:
+**Claude Code**
 
-```json
-{
-  "mcpServers": {
-    "vapi": {
-      "command": "npx",
-      "args": ["-y", "@vapi-ai/mcp-server"],
-      "env": {
-        "VAPI_TOKEN": "<your_vapi_token>"
-      }
-    }
-  }
-}
+```bash
+export VAPI_API_KEY="YOUR_VAPI_API_KEY"
+claude mcp add --transport http --scope user vapi \
+  https://mcp.vapi.ai/mcp \
+  --header 'Authorization: Bearer ${VAPI_API_KEY}'
 ```
 
-### Remote Server (Streamable HTTP)
-
-Clients that support remote MCP servers can connect directly:
-
-- URL: `https://mcp.vapi.ai/mcp`
-- Header: `Authorization: Bearer your_vapi_api_key_here`
-
-### Client-Specific Examples
-
-#### Claude Code
+**Codex**
 
 ```bash
-claude mcp add -e VAPI_TOKEN=your_vapi_token vapi -- npx -y @vapi-ai/mcp-server
+export VAPI_API_KEY="YOUR_VAPI_API_KEY"
+codex mcp add vapi --url https://mcp.vapi.ai/mcp \
+  --bearer-token-env-var VAPI_API_KEY
 ```
 
-#### Claude Desktop
+Keep `VAPI_API_KEY` set whenever you launch your agent. Start a new session, then try:
 
-Use the local server configuration above in the Claude Desktop configuration file. To connect to the hosted server through an stdio bridge instead:
-
-```json
-{
-  "mcpServers": {
-    "vapi": {
-      "command": "npx",
-      "args": [
-        "mcp-remote",
-        "https://mcp.vapi.ai/mcp",
-        "--header",
-        "Authorization: Bearer ${VAPI_TOKEN}"
-      ],
-      "env": {
-        "VAPI_TOKEN": "<your_vapi_token>"
-      }
-    }
-  }
-}
 ```
-
-### Optional Agent Skill
-
-The [`skill`](./skill) directory contains reusable instructions for AI coding agents that support Agent Skills. Install it using your host's skill installation process.
-
-For Claude Code:
-
-```bash
-mkdir -p ~/.claude/skills/vapi
-curl -o ~/.claude/skills/vapi/SKILL.md https://raw.githubusercontent.com/VapiAI/mcp-server/main/skill/SKILL.md
+List my Vapi assistants.
 ```
 
----
-
-## Example Usage
-
-### Create a Voice Assistant
-
-Ask your MCP-enabled agent:
 ```
-I want to build a voice assistant that can schedule appointments
+I want to build a voice assistant that can schedule appointments.
 ```
 
-### Make an Outbound Call
-
 ```
 Call +1234567890 using my appointment reminder assistant with these details:
 - Customer name: Sarah Johnson
@@ -105,25 +49,34 @@ Call +1234567890 using my appointment reminder assistant with these details:
 - Appointment time: 2:30 PM
 ```
 
-### Schedule a Future Call
-
 ```
 Schedule a call with my support assistant for next Tuesday at 3:00 PM to +1555123456
 ```
 
----
+> The legacy SSE endpoint (`https://mcp.vapi.ai/sse`) is deprecated. Move existing remote configurations to `https://mcp.vapi.ai/mcp`.
+
+### Optional: add the Vapi agent skill
+
+The [`skill`](./skill) directory contains reusable instructions for AI coding agents that support Agent Skills. Install it using your host's skill installation process.
+
+For Claude Code:
 
-## Using Variable Values in Assistant Prompts
+```bash
+mkdir -p ~/.claude/skills/vapi
+curl -o ~/.claude/skills/vapi/SKILL.md https://raw.githubusercontent.com/VapiAI/mcp-server/main/skill/SKILL.md
+```
+
+### Using Variable Values in Assistant Prompts
 
 The `create_call` action supports passing dynamic variables through `assistantOverrides.variableValues`. Use double curly braces in your assistant's prompts: `{{variableName}}`.
 
-### Example Prompt with Variables
+#### Example Prompt with Variables
 
 ```
 Hello {{customerName}}, this is a reminder about your appointment on {{appointmentDate}} at {{appointmentTime}} with {{doctorName}}.
 ```
 
-### Default Variables
+#### Default Variables
 
 These are automatically available (no need to pass):
 
@@ -139,56 +92,155 @@ See [Vapi documentation](https://docs.vapi.ai/assistants/dynamic-variables#defau
 
 ---
 
-## Remote MCP Server
+## Oh, you're still here?
+
+You must want to [leave feedback](#leave-feedback), [run a local server yourself](#run-a-local-server) or [peek under the hood](#peek-under-the-hood). Read on.
 
-Connect to Vapi's hosted MCP server from any MCP client:
+### Leave feedback
+
+- **Found a bug or want a tool we don't have?** [Open an issue](https://github.com/VapiAI/mcp-server/issues).
+- **Have a question or want to talk it through?** Join the [Vapi Discord](https://discord.gg/v5Ee6FhAZt).
+- **Want to fix it yourself?** Pull requests are welcome. See [Development](#development) for how to build and test.
+
+### Run a local server
+
+Run the server on your own machine if your client only supports local stdio servers or you want to try unreleased changes. It uses the same tools as the hosted server.
+
+Configure your MCP client to run:
+
+```text
+npx -y @vapi-ai/mcp-server
+```
+
+Set `VAPI_TOKEN` to your Vapi API key in the server environment. MCP client configuration formats vary, but the server definition generally looks like this:
+
+```json
+{
+  "mcpServers": {
+    "vapi": {
+      "command": "npx",
+      "args": ["-y", "@vapi-ai/mcp-server"],
+      "env": {
+        "VAPI_TOKEN": "<your_vapi_token>"
+      }
+    }
+  }
+}
+```
 
-### Streamable HTTP (Recommended)
+For Claude Code:
 
-- URL: `https://mcp.vapi.ai/mcp`
-- Header: `Authorization: Bearer your_vapi_api_key_here`
+```bash
+claude mcp add -e VAPI_TOKEN=your_vapi_token vapi -- npx -y @vapi-ai/mcp-server
+```
 
-### SSE (Deprecated)
+For Claude Desktop, add the configuration above to the Claude Desktop configuration file.
 
-- URL: `https://mcp.vapi.ai/sse`
-- Header: `Authorization: Bearer your_vapi_api_key_here`
+To run a build from this repository instead, see [Local Development Config](#local-development-config).
 
 ---
 
-## Available Tools
+## Peek under the hood
 
-### Assistants
+### Available Tools
+
+#### Documentation
+| Tool | Description |
+|------|-------------|
+| `ask_vapi_docs` | Query the Fern docs MCP for current documentation passages and source URLs |
+
+`ask_vapi_docs({"question":"How do assistant hooks work?","topK":8})` forwards to
+`searchDocs` at `https://docs.vapi.ai/_mcp/server`. The result preserves Fern's
+content, source links and error flag. This endpoint currently returns passages
+for the calling agent to synthesize, rather than a generated answer. `topK`
+defaults to 8 (maximum 20). Each request owns its MCP connection, supports caller
+cancellation, times out after 30 seconds and closes the connection afterwards.
+
+This tool needs outbound HTTPS to the Fern endpoint. It makes no Vapi API calls
+and sends no Vapi credentials upstream. The server still requires `VAPI_TOKEN`
+at startup. Discovery through `tools/list` makes no network requests; upstream
+failures are returned as tool errors. No extra MCP connection is needed. Do not
+include secrets or private customer data in docs questions.
+
+#### Assistants
 | Tool | Description |
 |------|-------------|
-| `list_assistants` | List all assistants |
+| `list_assistants` | List assistants in pages of up to 10 |
 | `get_assistant` | Get assistant by ID |
 | `create_assistant` | Create new assistant |
 | `update_assistant` | Update assistant |
 
-### Calls
+#### Calls
 | Tool | Description |
 |------|-------------|
-| `list_calls` | List call history |
+| `list_calls` | List call history in pages of up to 10 |
 | `get_call` | Get call details |
 | `create_call` | Start outbound call (immediate or scheduled) |
 
-### Phone Numbers
+#### Phone Numbers
 | Tool | Description |
 |------|-------------|
-| `list_phone_numbers` | List phone numbers |
+| `list_phone_numbers` | List phone numbers in pages of up to 10 |
 | `get_phone_number` | Get phone number details |
 
-### Tools (Function Calling)
+#### Tools (Function Calling)
 | Tool | Description |
 |------|-------------|
-| `list_tools` | List custom tools |
+| `list_tools` | List custom tools in pages of up to 10 |
 | `get_tool` | Get tool details |
 | `create_tool` | Create tool for API integration |
 | `update_tool` | Update tool |
 
----
+#### Public Skills
+| Tool | Description |
+|------|-------------|
+| `search_skills` | Search public Vapi skills by keywords; omit `query` to browse |
+| `load_skill` | Read a skill's `SKILL.md` or a supporting file |
+
+For example, call `search_skills({"query":"simulations"})`, then
+`load_skill({"name":"simulations"})`. The load result includes a `files` list;
+read a supporting file with `load_skill({"name":"simulations","path":"references/example.md"})`,
+using an exact path from that list. Loading returns instructions for the current
+task; it does not install skills or run scripts.
+
+Skills come directly from the public [VapiAI/skills](https://github.com/VapiAI/skills)
+repository, including experimental skills. Discovery uses its GitHub tree rather
+than the proposed skills manifest. Each server caches a commit-pinned snapshot
+for five minutes, so file reads within that snapshot use the same revision. Search
+matches names, descriptions and instruction text; it returns at most `limit`
+results (default 10, maximum 30) and the total match count. `load_skill` returns
+one text file at a time, up to 512 KB, with its source URL and revision.
+
+The skills tools need outbound HTTPS to public GitHub. They make no Vapi API
+calls and send no Vapi credentials upstream. The server still requires
+`VAPI_TOKEN` at startup. Discovery through `tools/list` makes no network requests;
+upstream failures are returned as tool errors. No GitHub token is needed for this
+public content. GitHub's unauthenticated API rate limits apply.
+
+#### Simulations
 
-## Development
+| Tool | Description |
+|------|-------------|
+| `list_simulation_personalities` | List simulated callers |
+| `create_simulation_personality` | Create a simulated caller with a tester assistant |
+| `list_simulation_scenarios` | List tester scripts and evaluations |
+| `create_simulation_scenario` | Create a tester script and evaluations |
+| `list_simulations` | List scenario/personality pairs |
+| `create_simulation` | Pair a scenario with a personality |
+| `list_simulation_suites` | List groups of simulations |
+| `create_simulation_suite` | Group simulations into a suite |
+| `run_simulations` | Run simulations or suites against an assistant or squad |
+| `list_simulation_runs` | List runs and filter by status or target |
+| `get_simulation_run` | Get run status and item summaries |
+| `get_simulation_run_item` | Get a full item including transcript and results |
+
+The catalog contains 29 tools. Simulation lists default to 50 results.
+`get_simulation_run` returns the first 100 item summaries, with API pagination
+metadata in `itemsMetadata` and `itemsTruncated: true` when more items exist.
+Legacy array responses are also supported. Use `get_simulation_run_item` for
+the full details of a known item.
+
+### Development
 
 ```bash
 # Install dependencies
@@ -201,7 +253,7 @@ npm run build
 npm run inspector
 ```
 
-### Local Development Config
+#### Local Development Config
 
 ```json
 {
@@ -217,7 +269,7 @@ npm run inspector
 }
 ```
 
-### Testing
+#### Testing
 
 ```bash
 # Safe default suite (build, mocked execution, contract, and stdio compatibility)
@@ -247,6 +299,91 @@ export VAPI_TOKEN=your_test_org_token_here
 npm run test:live:mutating
 ```
 
+#### Input validation from OpenAPI
+
+All 21 parameterized MCP tools use imported OpenAPI constraints through
+Zod's experimental `z.fromJSONSchema()`, pinned to Zod 4.6.7. This covers
+assistant names/LLMs/voices/transcribers, call schedules and customer numbers,
+lookup/update IDs, function parameters, transfer destinations, HTTP methods,
+timeouts and retry plans, plus all 12 simulation tools. The four original list
+tools have local empty input schemas.
+
+`src/schemas/assistant-openapi.json` is the compact projection for the original
+tool surfaces (the filename is retained from the initial assistant cutover). It
+records the [public API spec](https://api.vapi.ai/api-json) source SHA-256 and
+includes the recursive JSON-schema definitions needed for function parameters
+and request bodies. Builds and installs use it without network access. Refresh
+explicitly with `npm run schemas:snapshot`, or pass a saved spec with
+`npm run schemas:snapshot -- /path/spec.json`.
+
+`src/schemas/simulation-openapi.json` bundles the full simulation DTOs and their
+referenced definitions from the same public spec. The same refresh command
+updates both snapshots. Simulation validation includes names, folder paths,
+UUIDs, instructions, evaluations, nested tester assistants and structured
+outputs. Scenario/suite `additionalFields` are validated after merging, so they
+cannot override an API constraint. Large nested assistant and structured-output
+objects have compact advertised envelopes; their full API contracts are checked
+at runtime. The shared summary projection omits long documentation and recursive
+definitions from simulation discovery. The 25-tool catalog is about 28 KB.
+No runtime schema fetch or
+`get_api_schema` tool is required.
+
+Simulation aliases remain local adapters: `run_simulations` takes exactly one
+assistant/squad target and at least one simulation/suite ID, then builds the API
+request. Integer iterations and integer page sizes of 1–100 are MCP policies;
+API iteration bounds and parameter formats come from the snapshot. The item
+lookup endpoint publishes plain strings for its IDs, so those are not assigned
+UUID constraints from a different endpoint.
+
+The shared normalizer also represents empty preset enums as always-failing
+branches and preserves property names such as `oneOf` and `default` when walking
+JSON Schema definitions.
+
+When upgrading `@vapi-ai/server-sdk`, refresh and review the bundled schema in
+the same PR, then run `npm run typecheck`, `npm test`, and `npm run test:package`.
+Check changes against the SDK's request types and the MCP adapters below. The
+public endpoint serves the current API spec, not a spec version tied to the SDK
+release, so refreshing does not by itself guarantee compatibility. Keep the
+reviewed schema bundled with the release; do not refresh it during installation
+or startup.
+
+The adapter documents published contract corrections: overlapping enum/string
+`oneOf` alternatives become `anyOf`; duplicate enum values and JavaScript regex
+delimiters are removed; the contradictory object/string-enum annotation on
+`BackoffPlan.type` is corrected. Provider variants reject undeclared fields.
+Spec defaults do not inject request fields; MCP defaults remain separate.
+For the original compact assistant tools, variants requiring fields outside
+the current interface remain excluded: custom
+voice, Neuphonic voice, custom transcriber, Speechmatics transcriber, and custom
+LLM. Adding their required fields needs an explicit interface extension.
+
+MCP wrappers preserve field aliases and sparse updates. URL checks and
+string-valued header maps remain explicit transport rules because the spec only
+describes a string/object. API-request header maps and SMS metadata retain legacy MCP representations;
+they are explicit compatibility adapters, not claimed to be full API DTO
+validation. SMS metadata is not described in the published DTO. Response summaries also remain
+local: they are transformed MCP representations, not raw API DTOs.
+
+Validation failures return `isError: true`, concise text and structured
+`validationError` details: tool name, issue code, field path, message and allowed
+choices where relevant. Errors select the supplied provider's union branch,
+include at most 12 issues and 8 allowed choices per issue, and indicate
+truncation. Submitted values and credential contents are not echoed. Agents
+should correct the listed fields and retry; a validation failure never invokes
+the API handler. Tests exercise this correction loop through a real MCP client.
+
+`tools/list` advertises a compact input summary derived from the same validators:
+field names, basic types, required fields, defaults, and short constraints. It
+omits provider/model catalogs, lengthy API documentation, and recursive schema
+definitions. The full OpenAPI-derived validator still runs before any API call;
+the advertised summary is intentionally broader. Catalog tests cap the
+original 13-tool list at 20 KB, the 12 simulation tools at 10 KB, and the complete
+25-tool list at 30 KB to prevent unexpected agent-context growth.
+
+`npm test` includes schema contract tests, independent Ajv parity cases, and
+validation-feedback tests. The existing live compatibility
+suites cover read-only resources and disposable assistants/custom tools.
+
 ---
 
 ## References

package/dist/knowledge/docs.d.ts

@@ -0,0 +1,96 @@
+import type { Transport } from '@modelcontextprotocol/sdk/shared/transport.js';
+export declare const DOCS_MCP_URL = "https://docs.vapi.ai/_mcp/server";
+export declare function askVapiDocs(question: string, topK: number, signal?: AbortSignal, transport?: Transport): Promise<{
+    [x: string]: unknown;
+    content: ({
+        type: "text";
+        text: string;
+        annotations?: {
+            audience?: ("user" | "assistant")[] | undefined;
+            priority?: number | undefined;
+            lastModified?: string | undefined;
+        } | undefined;
+        _meta?: Record<string, unknown> | undefined;
+    } | {
+        type: "image";
+        data: string;
+        mimeType: string;
+        annotations?: {
+            audience?: ("user" | "assistant")[] | undefined;
+            priority?: number | undefined;
+            lastModified?: string | undefined;
+        } | undefined;
+        _meta?: Record<string, unknown> | undefined;
+    } | {
+        type: "audio";
+        data: string;
+        mimeType: string;
+        annotations?: {
+            audience?: ("user" | "assistant")[] | undefined;
+            priority?: number | undefined;
+            lastModified?: string | undefined;
+        } | undefined;
+        _meta?: Record<string, unknown> | undefined;
+    } | {
+        type: "resource";
+        resource: {
+            uri: string;
+            text: string;
+            mimeType?: string | undefined;
+            _meta?: Record<string, unknown> | undefined;
+        } | {
+            uri: string;
+            blob: string;
+            mimeType?: string | undefined;
+            _meta?: Record<string, unknown> | undefined;
+        };
+        annotations?: {
+            audience?: ("user" | "assistant")[] | undefined;
+            priority?: number | undefined;
+            lastModified?: string | undefined;
+        } | undefined;
+        _meta?: Record<string, unknown> | undefined;
+    } | {
+        uri: string;
+        name: string;
+        type: "resource_link";
+        description?: string | undefined;
+        mimeType?: string | undefined;
+        size?: number | undefined;
+        annotations?: {
+            audience?: ("user" | "assistant")[] | undefined;
+            priority?: number | undefined;
+            lastModified?: string | undefined;
+        } | undefined;
+        _meta?: {
+            [x: string]: unknown;
+        } | undefined;
+        icons?: {
+            src: string;
+            mimeType?: string | undefined;
+            sizes?: string[] | undefined;
+            theme?: "light" | "dark" | undefined;
+        }[] | undefined;
+        title?: string | undefined;
+    })[];
+    _meta?: {
+        [x: string]: unknown;
+        progressToken?: string | number | undefined;
+        "io.modelcontextprotocol/related-task"?: {
+            taskId: string;
+        } | undefined;
+    } | undefined;
+    structuredContent?: Record<string, unknown> | undefined;
+    isError?: boolean | undefined;
+} | {
+    [x: string]: unknown;
+    toolResult: unknown;
+    _meta?: {
+        [x: string]: unknown;
+        progressToken?: string | number | undefined;
+        "io.modelcontextprotocol/related-task"?: {
+            taskId: string;
+        } | undefined;
+    } | undefined;
+}>;
+//# sourceMappingURL=docs.d.ts.map

package/dist/knowledge/docs.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"docs.d.ts","sourceRoot":"","sources":["../../src/knowledge/docs.ts"],"names":[],"mappings":"AAEA,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,+CAA+C,CAAC;AAE/E,eAAO,MAAM,YAAY,qCAAqC,CAAC;AAI/D,wBAAsB,WAAW,CAC/B,QAAQ,EAAE,MAAM,EAChB,IAAI,EAAE,MAAM,EACZ,MAAM,CAAC,EAAE,WAAW,EACpB,SAAS,GAAE,SAAoE;;;;;mBAW44f,CAAC;oBAA4B,CAAC;oBAAgE,CAAC;wBAAkD,CAAC;;aAAkE,CAAC;;;;;mBAA+J,CAAC;oBAA4B,CAAC;oBAAgE,CAAC;wBAAkD,CAAC;;aAAkE,CAAC;;;;;mBAA+J,CAAC;oBAA4B,CAAC;oBAAgE,CAAC;wBAAkD,CAAC;;aAAkE,CAAC;;;;;;oBAA8L,CAAC;iBAA2C,CAAC;;;;oBAA4I,CAAC;iBAA2C,CAAC;;mBAA6E,CAAC;oBAA4B,CAAC;oBAAgE,CAAC;wBAAkD,CAAC;;aAAkE,CAAC;;;;;mBAAkK,CAAC;gBAA0C,CAAC;YAAsC,CAAC;mBAA6C,CAAC;oBAA4B,CAAC;oBAAgE,CAAC;wBAAkD,CAAC;;aAAkE,CAAC;;;aAAsF,CAAC;;oBAAyD,CAAC;iBAA2C,CAAC;iBAA6C,CAAC;;aAA8E,CAAC;;;;qBAAiH,CAAC;8CAAiF,CAAC;;;;;;;;;;;qBAAgV,CAAC;8CAAiF,CAAC;;;;GADv/lB"}

package/dist/knowledge/docs.js

@@ -0,0 +1,16 @@
+import { Client } from '@modelcontextprotocol/sdk/client/index.js';
+import { StreamableHTTPClientTransport } from '@modelcontextprotocol/sdk/client/streamableHttp.js';
+export const DOCS_MCP_URL = 'https://docs.vapi.ai/_mcp/server';
+// A separate connection per request avoids sharing a failed session or leaking
+// concurrent calls across each other. No Vapi credentials are sent upstream.
+export async function askVapiDocs(question, topK, signal, transport = new StreamableHTTPClientTransport(new URL(DOCS_MCP_URL))) {
+    const client = new Client({ name: 'vapi-mcp-docs', version: '1.0.0' });
+    const options = { signal: AbortSignal.any([AbortSignal.timeout(30_000), ...(signal ? [signal] : [])]), timeout: 30_000 };
+    try {
+        await client.connect(transport, options);
+        return await client.callTool({ name: 'searchDocs', arguments: { query: question, topK } }, undefined, options);
+    }
+    finally {
+        await client.close().catch(() => undefined);
+    }
+}

package/dist/knowledge/skills.d.ts

@@ -0,0 +1,28 @@
+export declare class PublicSkills {
+    private readonly fetcher;
+    private cached?;
+    constructor(fetcher?: typeof fetch);
+    private read;
+    private snapshot;
+    private content;
+    private skill;
+    search(query: string, limit: number): Promise<{
+        repository: string;
+        revision: string;
+        total: number;
+        skills: {
+            name: string;
+            description: string;
+            sourceUrl: string;
+        }[];
+    }>;
+    load(name: string, path: string): Promise<{
+        name: string;
+        path: string;
+        revision: string;
+        sourceUrl: string;
+        content: string;
+        files: string[];
+    }>;
+}
+//# sourceMappingURL=skills.d.ts.map

package/dist/knowledge/skills.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"skills.d.ts","sourceRoot":"","sources":["../../src/knowledge/skills.ts"],"names":[],"mappings":"AAwBA,qBAAa,YAAY;IAGX,OAAO,CAAC,QAAQ,CAAC,OAAO;IAFpC,OAAO,CAAC,MAAM,CAAC,CAAoD;gBAEtC,OAAO,GAAE,OAAO,KAAa;YAE5C,IAAI;IA6BlB,OAAO,CAAC,QAAQ;IAiBhB,OAAO,CAAC,OAAO;YAWD,KAAK;IAQb,MAAM,CAAC,KAAK,EAAE,MAAM,EAAE,KAAK,EAAE,MAAM;;;;;;;;;;IAyBnC,IAAI,CAAC,IAAI,EAAE,MAAM,EAAE,IAAI,EAAE,MAAM;;;;;;;;CAatC"}