메뉴
Template example showing the SKILL.md structure — replace this description with one that names YOUR skill's concrete trigger condition ("Triggers when the user asks how to X, Y, Z"). Keep it ≤200 characters for best intent-matching.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Router skill for Anthropic's news + research feeds — auto-refreshed daily from anthropic.com/news and anthropic.com/research. Use when the user asks about TIME-SENSITIVE Anthropic content: model launches ("did Claude X just release?"), product announcements, partnership news, region launches, new research papers, recent policy positions, or "what's new from Anthropic?" / "what did Anthropic just announce?" / "any recent research on X?" Skip: deep technical reference (use the other 7 skills — claude-code, anthropic-api, etc.); historical news older than ~30 items (link out to anthropic.com instead); detailed paper content (the digest carries title + summary + URL — Claude WebFetches the paper for depth on demand).
Router skill for Claude Cowork — the enterprise multi-cloud surface and Office agents. Cowork covers Claude for Work deployed on third- party clouds (Amazon Bedrock, Microsoft Foundry, LLM gateways), enterprise SSO, telemetry, the M365 connector, and policy controls. Office agents covers Claude in Excel and Slack-style office integrations. Use when the user asks about: deploying Claude for Work on Bedrock or Microsoft Foundry, integrating an LLM gateway, configuring enterprise SSO, enabling telemetry / audit logs, connecting M365, applying enterprise policies, Claude in Excel, or Slack-style office agent integrations. Skip: raw API on Bedrock / Vertex (use anthropic-platform-features), user-facing connectors directory (use claude-connectors), Claude Code CLI in enterprise contexts (use claude-code).
Router skill for Claude Connectors (the user-facing MCP integration surface on claude.com), Claude Desktop extensions (MCPB packaging), MCP Apps for Claude Desktop with their visual + interaction design guidelines, the directory of pre-built integrations (GitHub, Google Workspace, Microsoft 365, Slack, …), the user-facing Agent Skills surface, and the user-facing Plugins surface. Use when the user asks about: enabling a connector in the Claude app, building a custom connector, packaging a Desktop extension (MCPB), MCP Apps visual / interaction design rules, submitting to the connectors directory, OAuth + token handling for connectors, the GitHub / Google / Microsoft / Slack connector integrations, authoring user-installable Skills, or installing plugins via the Claude app. Skip: low-level MCP protocol spec (use mcp-spec), MCP servers run by Claude Code CLI (use claude-code), MCP connector exposed by the API (use anthropic-platform-features → SKILL-agents-and-tools).
Router skill for Claude Code (the CLI tool itself). Contains intent hints and a dispatch table that maps a user's question to the surface-specific deep-reference file Claude should Read next. Use when the user asks about Claude Code internals: editing .claude/settings.json or settings.local.json, authoring or debugging hooks (PreToolUse, PostToolUse, Stop, SubagentStop, Notification, UserPromptSubmit, PreCompact, SessionStart, SessionEnd, etc.), writing slash commands or agents, configuring MCP servers in .mcp.json, building plugins or marketplaces, setting ANTHROPIC_* / CLAUDE_* env vars, troubleshooting permission modes, understanding the ~/.claude/ directory layout, or asking "what does <feature> in Claude Code do". Skip: questions about the Anthropic Messages API (use anthropic-api), the Claude Agent SDK (use claude-agent-sdk), the MCP protocol spec (use mcp-spec), or general shell / git / programming topics not specific to Claude Code internals.
Router skill for Anthropic platform-side features that sit above the raw Messages API: Agent Skills format (the spec for `.skill` packages used by platform-managed agents), MCP connectors hosted by Anthropic, tool use (computer use, code execution, bash tool, define-your-own tools), build-with-claude features (extended thinking, message batches, citations, Amazon Bedrock, Google Vertex, embeddings, fast mode, context editing), manage-claude operations (workload identity federation, billing, identity), and the Managed Agents product. Use when the user asks about: writing an Agent Skill `.skill` package, Anthropic's hosted MCP connector, MCP Tunnels (connecting private-network MCP servers without opening inbound ports), the computer-use tool, the code_execution tool, bash tool, extended thinking, message batches, prompt caching strategy at the platform level, citations, deploying via Bedrock or Vertex, embeddings models, fast-mode behavior, context editing strategies, WIF setup, billing / cost reports, identit
Router skill for the Anthropic Messages API and adjacent surfaces (admin endpoints, compliance, beta features, models catalog) hosted under platform.claude.com/docs/en/api/. Use when the user asks about: POST /v1/messages, tool_use / tool_result blocks, count_tokens, message batches, streaming responses, prompt caching, prompt cache TTL / breakpoints, system prompts, anthropic-beta headers, the admin API (organizations / workspaces / API keys / invites), compliance endpoints (data residency, audit logs, retention), beta-only features behind a beta header, or the models catalog (model IDs, deprecation dates, context window sizes). Skip: questions about Claude Code (use claude-code skill), the Claude Agent SDK (use claude-agent-sdk), platform features beyond the raw API such as Agent Skills format or tool-use guides (use anthropic-platform-features), MCP connector docs (claude-connectors), or per-language auto-generated SDK reference (use anthropic-sdk's TypeScript / Python types directly via your IDE).
| name | example-skill |
| description | Template example showing the SKILL.md structure — replace this description with one that names YOUR skill's concrete trigger condition ("Triggers when the user asks how to X, Y, Z"). Keep it ≤200 characters for best intent-matching. |
| user-invocable | false |
This is a minimal SKILL.md showing the required structure.
name and description. description is what Claude reads at intent-match time, so make it specific and name the trigger condition.Split into a router + per-surface deep references, and load them on demand:
---
name: my-skill
description: Router for my-skill. Use when the user asks about X, Y, or Z.
---
# My Skill — Router
| Surface | Read when… |
|---|---|
| [`SKILL-foo.md`](SKILL-foo.md) | User asks about Foo |
| [`SKILL-bar.md`](SKILL-bar.md) | User asks about Bar |
The router stays small (≤100 lines), and Claude reads the surface files only when the dispatch table maps to them. This repo's own SKILL.md is an example of the pattern.
If a fact lives in another skill (e.g., a sibling deep reference), link to it with a markdown link rather than duplicating.