菜单
Use when deciding whether to install, keep, move, or remove MCP servers, or when setting up, reviewing, or troubleshooting MCP servers, especially for global vs repo-local placement, trend checks, config file locations, transport choices, credential handling, or startup failures.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Route work in the `~/.apm` global APM workspace: decide what owns a change, which path is the source of truth, and which APM rollout / `mise` task to run. Use for skill update and redistribution requests (`skillアップデートして再配布して`, `再配布`), `apm.yml` / `apm.lock.yaml` and managed catalog rollout, manual-skills package state, orphaned APM packages, checked-out external dependency repositories, optional repository-scoped skill packages, and `apmのバージョンあげて` / pinned `apm` source checks. For skill body, description, script, reference, or asset design itself, coordinate with `skill-creator`; for general mise usage outside the APM workspace (including `mise upgrade TOOL` and `minimum_release_age`), use `mise`.
Use when deciding whether to install, enable, or troubleshoot Headroom context compression for local AI agent workflows, especially MCP, proxy, or agent-wrap usage.
Use when adding or reviewing CI-stability hooks and gates: Lefthook/pre-commit/pre-push configuration, aligning local push gates with GitHub Actions, deciding commit-vs-push gate scope, or migrating pre-commit to Lefthook. For mise task design itself, use `mise`; for debugging failing PR checks, use `gh-fix-ci`.
Curate external agent collections into this APM workspace. Use when evaluating whether an outside agent repository can be installed through APM, importing selected agents into catalog/agents, recording provenance, or refreshing curated agents from upstream.
Use when creating, rebuilding, or updating a Google Forms survey from a Markdown survey spec such as SURVEY_QUESTIONS.md, especially when the form should stay synchronized with question text, required flags, Google Forms item types, scale labels, and removed-question notes.
Slack app management knowledge for app settings, manifests, OAuth installs, scopes, bot users, Marketplace settings, App Home, display names, sender names, mrkdwn message formatting, and safe workspace-visible changes. Use when diagnosing or changing a Slack app, installed app, bot user, app label, DM header, chat sender, message text decoration, Slack links, block quotes, app approval/install state, token impact, Slack API app settings, Slack Marketplace settings, or stale Slack app name propagation.
| name | mcp-tools |
| description | Use when deciding whether to install, keep, move, or remove MCP servers, or when setting up, reviewing, or troubleshooting MCP servers, especially for global vs repo-local placement, trend checks, config file locations, transport choices, credential handling, or startup failures. |
This skill is for MCP server selection, placement, and wiring, not for using a specific downstream tool. Start by deciding whether the task is placement review, setup, diagnosis, or credential review.
Read references/mcp-placement.md when deciding global vs repo-local vs on-demand placement. Read references/mcp-tools-details.md for fuller setup examples, references/server-configurations.md for server patterns, and references/security-and-credentials.md when secrets or token handling are in scope.
使わない場面:
Claude Desktop Codex 他のクライアント のどれか確定するglobal repo-local on-demand do-not-install のどれかに分類するtransport command/url args/env を分けて確認するreferences/mcp-placement.md で設置場所を決めるstdio なら command と args を、http なら url を確認するapm-usage も使い、deployed target を直接編集しないargs がその server に合っているかstdio server の失敗を network 問題だと誤認するcommand は正しいが依存 runtime が未インストールreferences/mcp-placement.mdreferences/mcp-tools-details.mdreferences/server-configurations.mdreferences/security-and-credentials.md