菜单
Process freeform notes and dropped files in {VAULT_PATH}/Inbox.md and {VAULT_PATH}/Inbox_Files/ — classify each item and file it into the correct place in the vault. Use when the user says "process my inbox," "sort my notes," or /inbox-triage.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Log a vault change (note created/edited/deleted) to a running daily changelog note. After any write to the vault, ask the user "should this be logged?" and run this skill on confirmation. Also runs directly when the user says /changelog.
Update a project's README and the relevant vault notes (overview / module map) after a meaningful code change — new feature, new file, new module, or an architectural decision. Should trigger on its own once a coding task is finished, without the user having to ask — skip it for trivial (typo/formatting) changes. Also runs manually when the user says "update the docs" or "document this."
Update "where we left off" tracking for {PROJECT} when a milestone or unit of work closes. Updates Status.md (active milestone + next concrete action) and Milestone_Log.md (chronological record); touches Goal.md/Decisions.md if needed. Called by project-orchestrator at the end of every milestone; also used directly when the user says "log this milestone" or "update status."
Design phase for {PROJECT} — data model, module boundaries, API contract, access control, and any multi-tenancy/security design, before code is written. Called by project-orchestrator before implementation; also used directly when the user says "design {PROJECT}'s X module."
Implementation phase for {PROJECT} — builds the actual code for a module or vertical slice against an existing design. Called by project-orchestrator once a design exists; also used directly when the user says "implement {PROJECT}'s X module."
Main orchestrator for building {PROJECT}. Tracks cross-session continuity, reads "where we left off," routes to the correct phase sub-skill, and runs autonomously. Use when the user says "continue {PROJECT}," "work on {PROJECT}," "{PROJECT} where did we leave off," or /project-orchestrator. This is for the BUILD side of {PROJECT} — not for unrelated day-to-day tasks about it.
| name | inbox-triage |
| description | Process freeform notes and dropped files in {VAULT_PATH}/Inbox.md and {VAULT_PATH}/Inbox_Files/ — classify each item and file it into the correct place in the vault. Use when the user says "process my inbox," "sort my notes," or /inbox-triage. |
An inbox exists so that a fleeting thought or a dropped file doesn't have to be filed correctly at the moment it's captured. This skill does the filing later, in a batch.
Read Inbox.md (freeform text notes) and list the contents of Inbox_Files/ (dropped documents, audio, images, links).
For each item, decide:
vault-format for the area/project structure).task-list).Move or write the content into the correct location following vault-format conventions (frontmatter, naming, navigation link, hub update). Once filed, remove the raw item from the Inbox — the inbox should end each triage pass empty or holding only genuinely unresolved items.
Give a short summary of what was filed where, so anything mis-classified can be corrected immediately rather than discovered later.
If an item's destination genuinely isn't clear (not enough context to tell which project it belongs to), ask rather than guessing — a wrongly-filed note is often harder to find later than one left in the inbox.