القائمة
Use when you need a one-off MCP server capability during research or debugging without permanently mounting it as a context-polluting integration.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/romiluz13/cc10x --skill mcp-cliيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Answers questions about cc10x itself — what it is, how to install and configure it, how the router, workflows, memory, and hooks operate, and how to troubleshoot. Use this skill when: the user asks ABOUT cc10x — "what is cc10x", "how do I configure cc10x", "why isn't cc10x activating", "how do cc10x workflows work", "how does cc10x memory work", "cc10x troubleshooting". NOT for performing work: "set up cc10x for me", build, debug, review, or plan requests route to cc10x-router. "Update cc10x" / "upgrade cc10x" route to the update skill. This skill answers questions; it never edits project code, never writes files, never runs workflows. Triggers: what is cc10x, cc10x help, cc10x guide, how to use cc10x, configure cc10x, cc10x setup, cc10x faq, cc10x troubleshooting, cc10x not working, cc10x not activating.
Greenfield architecture design: map functionality flows, draw components, design APIs, classify dependencies, plan observability. For multi-component, API, schema, auth, or integration-heavy work. For retrofitting existing code, use codebase-hygiene instead.
Use when a BUILD phase completes, a commit is staged, or a PR is about to be created, and the diff has not yet been reflected in documentation. Also use when the user says "update docs", "sync docs", "document this", or asks whether documentation is up to date.
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | mcp-cli |
| description | Use when you need a one-off MCP server capability during research or debugging without permanently mounting it as a context-polluting integration. |
| allowed-tools | Read Bash |
| user-invocable | false |
The mcp CLI (from github.com/f/mcptools) discovers and invokes MCP server capabilities on-demand. Use it when a task needs ONE server's tool — a doc fetch, a single query, a quick lookup — instead of permanently mounting that server as an always-loaded integration.
This keeps accelerators transient: spun up for the task, used, and dropped. A permanently mounted MCP server costs context on every session whether you call it or not. The CLI costs nothing until you run it.
Composes with cc10x:research.
Check first: command -v mcp. If absent, install:
git clone https://github.com/f/mcptools /tmp/mcptools
CGO_ENABLED=0 go build -o ~/.local/bin/mcp /tmp/mcptools/cmd/mcptools
# ensure ~/.local/bin is on PATH
If go is unavailable, report that the accelerator is missing and proceed with built-in tools — do NOT treat the missing binary as a task blocker (it is a fallback message, not a wall).
1. Discover first — always. Never call a tool whose schema you have not seen — guessed params fail silently or hit the wrong tool.
mcp tools <server-command> # list tools
mcp tools --format json <server-command> # full param schema for parsing
mcp resources <server-command> # list resources
mcp prompts <server-command> # list prompts
2. Lead read-only when exploring. Restrict the surface before you touch an unfamiliar server:
mcp guard --allow 'tools:read_*,list_*' --deny 'tools:write_*,delete_*' <server-command>
Drop the guard only once you know exactly which write you intend.
3. Call with params matching the discovered signature exactly (param:str, param:num, [optional]):
mcp call <tool_name> --params '<json>' -f json <server-command>
Output -f json for parsing, -f pretty for reading. Check exit code and stderr on failure — a non-zero exit is a real error, not a fallback message.
Server-command examples:
npx -y @modelcontextprotocol/server-filesystem /path--transport sse--auth-header "Bearer <token>", --auth-user user:pass, or -e ENV_VAR for docker serversIf you call the same server several times, alias it; remove it when the task ends so nothing lingers:
mcp alias add <name> <server-command> # then: mcp tools <name>, mcp call ... <name>
mcp alias remove <name> # release when done
Aliases persist in ~/.mcpt/aliases.json. Cleaning them up is part of keeping the accelerator transient.