メニュー
Use when the user asks to inspect or manage Oratorio board items, local tasks, review rounds, or agent-work coordination through the available Oratorio board tools.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/DotHarness/dotcraft --skill oratorioコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Browser automation for the DotCraft in-app browser. Use to open, navigate, inspect, test, click, type, screenshot, or verify local targets such as localhost, 127.0.0.1, ::1, file://, dotcraft-viewer:, the current app browser tab, and approved http/https pages.
Use the user's existing Chrome browser through the DotCraft Chrome extension backend. Use for authenticated/profile-dependent pages, existing Chrome tabs, cookies-backed sessions, installed extensions, and workflows where the Desktop embedded browser is not enough.
Find and export DotCraft session, trace, and memory context for external coding agents or DotCraft Doctor troubleshooting. Use when a user needs to locate related sessions from an error, provider message, tool failure, symptom, or thread id, then produce a clean Markdown handoff.
| name | oratorio |
| description | Use when the user asks to inspect or manage Oratorio board items, local tasks, review rounds, or agent-work coordination through the available Oratorio board tools. |
Oratorio is an operator-facing board for agent work. It tracks local tasks, GitHub issues, pull requests, review rounds, run history, decisions, comments, drafts, and source-write audit records. Its board tools are delivered through the Oratorio App Binding and MCP. Refer to the stable local tool names below; DotCraft assigns the canonical MCP namespace, so do not guess or hard-code it.
Use ListBoardItems to scan the board. Filter by state, source, repository, assignee, search text, or limit when the user asks for a subset.
Use GetBoardItem before making claims about one item or before queuing work against it. Prefer item ids or short ids from Oratorio results. Do not invent ids.
Use CreateBoardTask when the user clearly wants a durable Oratorio task. Create concise titles and useful descriptions. Include repository, branch, assignee, and labels only when known or explicitly requested.
Use QueueReviewRound when the user wants Oratorio to start a review-analysis round for an existing board item. Include a short note describing the requested focus.
When the user asks what is on the board, summarize items by status and highlight likely next actions.
When the user asks to create tasks from a discussion, extract concrete tasks, avoid duplicates when visible board context is available, and create only tasks that are specific enough to act on.
Use CreateBoardTask or QueueReviewRound only when the user explicitly asks to change Oratorio state. Do not rely on a possible approval prompt as authorization. Execute clear, low-risk requests directly; ask a short clarification only when the target, scope, or risk is ambiguous. If DotCraft presents an approval prompt, treat it as an additional gate.
Mention Oratorio item titles, short ids, states, repositories, and next actions when they help the user act. Keep summaries concise and avoid exposing raw tool payloads unless the user asks for details.