メニュー
Enables tracking of higher-level user tasks across projects using MCP tools
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Deterministic communication metrics for the mirrored Teams channels. Computes reply-latency distributions, after-hours share, burst/fragmentation index, unanswered blockers, and interruption-cascade depth from data/teams/*/messages.jsonl, and refreshes the hyperscreen dashboard data. Use before making ANY quantitative claim about team communication.
Generate an interactive "application simulator" — a tiny, agent-built React mock of an external app (SAP MD04, a CRM, an ERP form) that the trainee can click through. The trainee's clicks stream back to you via viewerState so you can coach in real time. Each simulator is a single self-contained HTML file under `out/simulators/<app>.simulator.html`. Use this skill when the expert asks for a simulator (often in the context of curriculum topic 4 "Werkzeuge") or when a guest asks "can I practice this somewhere?".
Co-author a new roleplay scenario with an expert. Interview the expert about the persona, topic, hints with point values, and evaluation criteria, draft the JSON, and on confirmation write it to roleplay/<slug>.roleplay.json. Use when the expert invokes "Author a roleplay scenario" from the menu, asks "let me add a customer call to practice", "I want to script a difficult buyer", or equivalent. The scenarios authored here are consumed at runtime by the roleplay-engine skill.
Maintains a project knowledge wiki at wiki/ as the agent's long-term memory, dynamically structured around the mission in wiki/_meta/mission.md. Use whenever the user shares a fact, decision, preference, requirement, or finding worth remembering; whenever the user says "remember this", "add to wiki", "we decided", "save", "note that", or "for the record"; whenever the user asks "what do we know about X", "have we considered Y", "what did we decide", "summarize what we have"; whenever a file in the project codebase contains information relevant to the mission and should be ingested; at the end of a session to consolidate findings; and at session start to load relevant context. Reads index first, deduplicates before writing, tracks provenance, appends history rather than overwriting, and creates stubs for mentioned-but-unresearched topics. Pure markdown, no embeddings, no external network.
Engineering Design Support System. Use this skill whenever the user is doing long-horizon product/engineering design and wants to capture intent, decisions, risks, assumptions, evidence, open questions, or hypotheses; whenever they say 'add a decision', 'propose a hypothesis', 'what did we rule out', 'what changed', 'generate a status report', 'show whitespots', 'sharpen this', 'mission', 'realign', or ask what the project knows; at session start to load mission + state; and as the curator/researcher/synthesizer/critic loops. The mission is the versioned north star; the RDF knowledge graph is the system of record for a typed dependency graph (Concept/Decision/Risk/Assumption/Evidence/OpenQuestion/Gap/Whitespot/Hypothesis/Test); the scrapbook is a projected view; the wiki is synthesized prose; hypotheses run as stateful workflows. Pull-only: never push to the engineer except a critic mission-contradiction.
Use this skill whenever the user wants to take structured notes, collect ideas, organize project requirements, or manage a project notebook — trigger on phrases like 'scrapbook', 'add a note', 'what have we captured', 'notebook', 'show my notes', 'what should I focus on', 'jot this down', or any request to review, prioritize, or organize project items. Reads and writes to the project scrapbook via MCP tools, presenting content as a structured hierarchy with priorities and focus levels.
| name | user-orders |
| description | Enables tracking of higher-level user tasks across projects using MCP tools |
This skill enables you to create and manage user orders — higher-level tasks that track complex multi-step work across the workspace.
Use this skill when the user asks for something that involves multiple steps or complex work, such as:
A user order is NOT for simple single-step tasks like answering a question, writing a short text, or making a quick file edit. It is for higher-level work involving research, multi-file creation, scheduled activities, or ongoing monitoring.
When you begin a complex task, create a user order to track it:
Tool: add_user_order
sessionId: The current chat session IDprojectName: The current project nameorderTitle: A short title (max 60 characters)orderDescription: A description of the work (max 2096 characters)orderType: One of "Research", "Scheduled Activity", "Monitoring"Returns: { orderId } — save this for subsequent updates.
As you work through the task, update the order status to keep the user informed:
Tool: update_user_order
orderId: The UUID returned from step 1statusNew: The new status (see below)statusMessage: A human-readable description of what changedWhen finished, set status to complete-success or complete-failure with a summary message.
| Status | When to use |
|---|---|
in-progress | Work is actively being done |
complete-success | Task completed successfully |
complete-failure | Task could not be completed |
requires-human-input | You need clarification or a decision from the user |
blocked-by | Work is blocked by an external dependency |
paused | Work is temporarily paused |
canceled-by-agent | You determined the task cannot or should not proceed |
Use get_user_order with the orderId to retrieve the full order object including status history.
requires-human-input when you need the user's clarification — they will see an action button in the UIstatusMessage entries — they form the order's history timeline