ワンクリックで
doey-mcp-example
Example skill demonstrating MCP server integration. Not for actual use.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Example skill demonstrating MCP server integration. Not for actual use.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Plan-first task creation — research, breakdown, risk analysis, then create tasks from approved plan. Usage: /doey-planned-task <goal>
Request a respawn of the current worker pane. Use when you need to "respawn me", "restart myself", "fresh context", or "reset my pane". Writes an atomic respawn request that kills the current Claude process and relaunches with a fresh context.
Discover scaffolding patterns in this project — structural fingerprints, accretion files, and refactoring patterns from git history. Returns candidates worth turning into templates.
Spawn the doey-scaffy MCP server so workers can drive the Scaffy template engine via tool calls. Loaded automatically when a task needs scaffy_run / scaffy_validate / scaffy_list / scaffy_audit / scaffy_discover / scaffy_new / scaffy_fmt or any scaffy:// resource.
Create a new scaffy template from existing files (--from-files) or interactively. Outputs to .doey/scaffy/templates/<name>.scaffy.
Manage persistent project tasks — list, add, transition, show, subtasks, decisions, notes. Tasks stored in .doey/tasks/ (survives reboot). Use when you need to "show tasks", "add a task", "mark a task done", "what are we working on", or "create a task".
| name | doey-mcp-example |
| description | Example skill demonstrating MCP server integration. Not for actual use. |
| mcp_servers | [{"name":"filesystem","command":"npx","args":"-y @modelcontextprotocol/server-filesystem /tmp","env":{}},{"name":"github","command":"github-mcp-server","args":"stdio","env":{"GITHUB_PERSONAL_ACCESS_TOKEN":"${GITHUB_TOKEN}"}}] |
This is a reference skill demonstrating the mcp_servers YAML frontmatter field.
Skills can declare MCP server dependencies in their YAML frontmatter using the mcp_servers field.
When a worker is launched to execute a skill with MCP dependencies, Doey:
mcp_servers block from the skill's SKILL.md frontmatter.mcp.json config file in $RUNTIME_DIR/mcp/--mcp-config <path> when launching the Claude instancemcp_servers:
- name: <server-name> # Required: unique server identifier
command: <executable> # Required: command to run
args: <arg1> <arg2> ... # Optional: space-separated arguments
env: # Optional: environment variables
KEY: value
KEY2: ${ENV_VAR} # Supports env var expansion
mcp__<server-name>__<tool-name> in tool listings