メニュー
Load alongside wiki-compile. Promotes ready inbox material into a real wiki note with the canonical schema; never invents content beyond the source.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Load when reading or writing project notes, weekly/monthly summaries, or journal/agent.md. Owns GET/PATCH for context files except today.md and roadmap.md, which use their dedicated skills.
Load when the user wants an ongoing task on a fixed cadence (every morning, each Monday, hourly) to run autonomously as its own named recurring Agent. Creates it via POST /api/agents. Not for one-time reminders (use schedule) or app-data background fetches (use managed-tasks).
Load to manage the durable source library (user-sent PDFs/PPTX/docs) — list unfiled sources, file them as knowledge/sources/ cards, promote images, or send a stored source back. SKIP for delivering files you generated this turn (attach) or general vault edits (context).
Hand a long-running or open-ended task (deep research, multi-repo CI audit, monitor X over time, bulk compile) to /api/background-task. Compose a self-contained brief, set the notification policy, POST, ack, end the turn. Read GET /:id for follow-up detail.
Read-only Task Board — list everything in motion (recurring DMs, Agents, app-fetch, automation triggers, reminders, background/browser work) via GET /api/tasks, and preview a delete's blast radius via GET /api/tasks/impact. For writes use the `task` skill.
Hand open-ended browser requests (post a tweet, fill a contact form, check an order status, …) to /api/browser-task. Relay sub-agent clarifications, POST /clarify with the reply, /cancel on stop.
| name | wiki-graduate |
| description | Load alongside wiki-compile. Promotes ready inbox material into a real wiki note with the canonical schema; never invents content beyond the source. |
| allowed-tools | ["Bash(curl *)"] |
You are loaded alongside wiki-compile so a compile pass can promote a single inbox note or output artifact into a real 20_wiki/<slug>.md article when the source has matured enough.
00_inbox/ is read-only to agents (wiki-vault-rules §Layers). You may read inbox material, but the only legal write surface for the graduated article is 20_wiki/ via the Wiki API. Never write back into 00_inbox/.
A source qualifies for graduation only if all of these are true:
<wiki_command>), OR the compile pass identified the same idea across ≥3 raw notes that converge on a stable framing.20_wiki/<slug>.md.If any of these fail, skip the graduation and leave a note in log.md: "wiki.graduate skipped: — ".
00_inbox/<anything>.md; output paths look like 30_outputs/<YYYY-MM-DD>-<slug>.md.90_meta/schemas/wiki.md): summary → key facts → source links → related notes. Include frontmatter that names the source path under derived_from: and dates the promotion under graduated_at:.[[slug]] syntax. Use the canonical slug from 90_meta/taxonomy.md when available.20_wiki/_index.md so the new article is discoverable.POST /api/wiki/{{workspace_name}}/files/20_wiki/<slug>.md
PATCH /api/wiki/{{workspace_name}}/files/20_wiki/_index.md (mode: "append")
x-process-key: wiki.compile
Use wiki.compile as the process key — graduation is a sub-action of the compile pass, not a separate process. If the slug collides with an existing wiki note, append a year disambiguator (<slug>-<YYYY>) only as a last resort; prefer extending the existing note via wiki-compile itself.
Append a log.md entry: "wiki.graduate: promoted <source path> → 20_wiki/<slug>.md".
End with a short internal summary only.