- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add nikolai-vysotskyi/trace-mcp --skill trace-mcp -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add nikolai-vysotskyi/trace-mcp --skill trace-mcp -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add nikolai-vysotskyi/trace-mcp --skill trace-mcp -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add nikolai-vysotskyi/trace-mcp --skill trace-mcp -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/nikolai-vysotskyi/trace-mcp/tree/HEAD/skills/trace-mcpFrom the publisher
trace-mcp is a framework-aware code intelligence MCP server. It exposes 182 tools that return semantic, structured results over a cross-language dependency graph. When trace-mcp is available, it is almost always cheaper and more accurate than native file tools.
Activate this skill whenever you need to:
Do not use Read, Grep, Glob, or shell ls/find/cat/head/tail for exploring source code (.ts, .js, .py, .php, .go, .rb, .java, etc.). Use trace-mcp tools instead. Native tools stay allowed only for non-code files (.md, .json, .yaml, configs) or immediately before an Edit on a known file.
get_project_map with summary_only=true — orient yourself to the project structureget_task_context with task: "<natural-language description>" — gather all relevant code in a single call instead of chaining search → get_symbol → Readget_env_vars. It returns keys plus
inferred types/formats only — never values, so it is safe for secrets.get_env_vars { "pattern": "DB_" } filters by key prefix.
get_env_vars { "file": ".env", "redacted": true } gives a line-by-line redacted
per-file view (keys + type hints, no values, preserves order/comments; requires file).search / get_symbol / get_outline /
get_task_context — never by importing a module to see what it touches.FORBIDDEN — never use these for env/config discovery (values leak into model context):
- never dump the environment:
python -c "import os; print(os.environ)"or anyos.environ/process.envprintout- never import-diff the environment:
before = dict(os.environ), import a module, then diffos.environto see what it touched- never
print(module.__file__)for file discovery- never
cator directly Read a.envfile for discovery
batch when you need 2+ independent tool calls:
batch({ calls: [
{ tool: "get_outline", args: { path: "src/foo.ts" } },
{ tool: "get_outline", args: { path: "src/bar.ts" } },
{ tool: "search", args: { query: "handleRequest", kind: "function" } }
]})
get_outline once, then get_symbol for specific pieces.get_context_bundle over chained get_symbol calls — it deduplicates shared imports.Read a file to edit it:
get_outline first to find the line range of the target symbol.offset + limit. Never read a 500-line file to edit 5 lines.register_edit with the edited file_path to reindex just that file and invalidate caches. This is much lighter than a full reindex and keeps subsequent queries accurate._duplication_warnings, review the referenced symbols — you may be duplicating existing logic.Edit tool already confirmed success.check_duplication with { name, kind } to verify no similar symbol exists. Prevents reinventing existing logic.audit_config — stale references in CLAUDE.md / settingsself_audit — dead exports, untested code, hotspotsget_tech_debt — per-module tech-debt gradesget_optimization_report — detects repeated reads, Bash grep usage, missed trace-mcp opportunitiestrace-mcp-refactoring — safe refactoring workflow (risk assessment → rename → impact check)trace-mcp-codemod — bulk mechanical changes via apply_codemodtrace-mcp-pre-commit — security, quality-gate, and antipattern checks before commitUse trace-mcp tools for code navigation, impact analysis, and framework-aware queries instead of Read/Grep/Glob/Bash. Activate whenever the agent needs to explore, understand, or modify a codebase tha
---name: trace-mcpdescription: Use trace-mcp tools for code navigation, impact analysis, and framework-aware queries instead of…---# skills/trace-mcp/SKILL.mdOverview
Use trace-mcp tools for code navigation, impact analysis, and framework-aware queries instead of Read/Grep/Glob/Bash. Activate whenever the agent needs to explore, understand, or modify a codebase that has trace-mcp indexed.
FAQ
Download skills/trace-mcp/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/nikolai-vysotskyi/trace-mcp.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.