How do I install the Memtrace API Topology skill?

Run npx skillmds@latest add syncable-dev/memtrace-api-topology in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Memtrace API Topology safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Memtrace API Topology?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Memtrace API Topology free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Memtrace API Topology?

syncable-dev (@syncable-dev) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Memtrace API Topology by syncable-dev

Name: Memtrace API Topology
Author: syncable-dev

Memtrace API Topology

Map API endpoints, outbound HTTP calls, and cross-repo service topology in indexed source code. Use when the user asks about API endpoints, HTTP routes, fetch/client calls, REST surface, service dependencies, cross-repo dependencies, or API topology. Do not use Grep, Glob, rg, find, or manual file search for routes or HTTP calls; Memtrace maps endpoints and call edges from the indexed AST graph.

syncable-dev d30dc9d 1.9 KB Updated Sep 17, 2026

File contents

Overview

Map HTTP API surface — endpoints, outbound calls, cross-repo topology.

Quick Reference

Tool	Required	Key optional
`find_api_endpoints`	`repo_id`	`method`, `path_contains`, `limit`, `branch`
`find_api_calls`	`repo_id`	`method`, `path_contains`, `limit`, `branch`
`get_api_topology`	—	`repo_id`, `min_confidence`, `include_external`

Full parameter spec for every Memtrace tool: references/mcp-parameters.md (bundled at the memtrace-skills plugin root).

Steps

1–3. Endpoints, calls, topology

{ "repo_id": "memdb" }
{ "repo_id": "memdb", "method": "GET", "path_contains": "/users" }
{ "min_confidence": 0.7 }

4. Deep-dive an endpoint handler

Use handler symbol name — not symbol ID:

{ "repo_id": "memdb", "symbol": "handleGetUsers" }

Output

Result	Carries
Endpoint entry (`find_api_endpoints`)	HTTP method, route path, handler symbol name (feed to `get_symbol_context` as `symbol`)
Call entry (`find_api_calls`)	HTTP method, target path, calling symbol
Topology edge (`get_api_topology`)	caller repo → handler repo, confidence 0.0–1.0 (edges below `min_confidence` dropped)

Common Mistakes

Mistake	Reality
`get_symbol_context(symbol_id=...)`	Use `symbol` (name) + `repo_id`
Cross-repo links with one repo indexed	Index all services; use `link_repositories` if needed

---name: memtrace-api-topologydescription: Map API endpoints, outbound HTTP calls, and cross-repo service topology in indexed source code. Use when the user asks about API endpoints, HTTP routes, fetch/client calls, REST surface, service dependencies, cross-repo dependencies, or API topology. Do not use Grep, Glob, rg, find, or manual file search for routes or HTTP calls; Memtrace maps endpoints and call edges from the indexed AST graph.---## OverviewMap HTTP API surface — endpoints, outbound calls, cross-repo topology.## Quick Reference| Tool | Required | Key optional ||------|----------|--------------|| `find_api_endpoints` | `repo_id` | `method`, `path_contains`, `limit`, `branch` || `find_api_calls` | `repo_id` | `method`, `path_contains`, `limit`, `branch` || `get_api_topology` | — | `repo_id`, `min_confidence`, `include_external` |Full parameter spec for every Memtrace tool: `references/mcp-parameters.md` (bundled at the memtrace-skills plugin root).## Steps### 1–3. Endpoints, calls, topology```json{ "repo_id": "memdb" }{ "repo_id": "memdb", "method": "GET", "path_contains": "/users" }{ "min_confidence": 0.7 }```### 4. Deep-dive an endpoint handlerUse handler **symbol name** — not symbol ID:```json{ "repo_id": "memdb", "symbol": "handleGetUsers" }```## Output| Result | Carries ||--------|---------|| Endpoint entry (`find_api_endpoints`) | HTTP method, route path, handler symbol name (feed to `get_symbol_context` as `symbol`) || Call entry (`find_api_calls`) | HTTP method, target path, calling symbol || Topology edge (`get_api_topology`) | caller repo → handler repo, confidence 0.0–1.0 (edges below `min_confidence` dropped) |## Common Mistakes| Mistake | Reality ||---------|---------|| `get_symbol_context(symbol_id=...)` | Use **`symbol`** (name) + `repo_id` || Cross-repo links with one repo indexed | Index all services; use `link_repositories` if needed |

Frequently asked questions