TwinMind action engine — manages standalone actions that aren't tied to any project. Use this skill when the user describes something they want to do that has a clear scope but doesn't belong to a project. Triggers: '建立行動', 'create action', '新增 action', '完成 action', 'action done', '做完了', '列出 actions', 'list actions', '升格為專案', 'promote to project', or when the user describes an executable goal like '研究 X', '設定 Y', '整理 Z'. Also use when the user says an action is getting too big and needs to become a project. Important: if the user mentions a specific project name, route to twinmind:project instead — that skill handles project-scoped actions.
TwinMind card engine. Use this whenever the user shares a thought, idea, knowledge, question, or source reference that should be captured as a card. Also handles card updates and deletions. Covers the full lifecycle: type classification, duplicate detection, card creation, automatic link inference to existing cards, and index updates. If the user says something that looks like knowledge worth remembering — this is the skill to use. For vague or unformed thoughts, route to twinmind:inbox instead.
TwinMind area engine — manages Areas of ongoing responsibility (long-term focus domains with no end date). Use this skill when the user talks about a persistent life/work domain they want to track, like '健康管理', '職涯發展', '財務規劃', or when they want to group projects and cards under a theme. Triggers: '建立領域', 'create area', '新增 area', '停用 area', 'deactivate', '重新啟用', 'reactivate', '關聯到 area', 'link to area', '列出 areas', 'list areas', '關注領域', or any mention of ongoing responsibilities, life domains, or thematic grouping of projects. Important: Areas are different from Projects (which have end dates) and from card domains (which are metadata tags). An Area is a conscious commitment to track a life domain.
TwinMind link engine for manual connections. Use when the user explicitly asks to link or unlink two specific cards (e.g. '把 X 和 Y 連起來', 'link X to Y', 'disconnect X from Y'). Handles relationship type classification, bidirectional link writing, and index updates. Not for automatic link inference during card creation — that's handled by twinmind:capture.
TwinMind inbox engine — the safety net for half-formed thoughts. Use this skill whenever the user shares something vague, unstructured, or not yet ready to become a Card, Action, Task, or Project. Classic triggers: '突然想到...', '隨手記一下', '有個想法但還不確定', 'inbox', '升格', 'promote', 'dismiss', '清理 inbox', 'triage', '待處理'. Also use this when the user's input is ambiguous — if you can't tell whether it's knowledge, a task, or an action, it belongs in the Inbox. The key question: does the user know what this should become? If not → Inbox. Important: do NOT use this for inputs that are already clear — a fact goes to twinmind:capture, '買牛奶' goes to twinmind:task, a scoped action goes to twinmind:action.
TwinMind shared post-operation pipeline — DEPRECATED as LLM subagent. Post-op is now handled programmatically via scripts/post-op.mjs. This skill file is retained for reference only.
TwinMind project engine — the hub for goal-driven work with a clear start and end. Use this skill for any project lifecycle operation: create, pause, resume, complete, archive. Also handles project-scoped actions and tasks (adding/completing actions within a project, managing project task lists), progress logging, and linking cards to projects. Triggers: '建立專案', 'create project', '暫停', 'pause', '恢復', 'resume', '完成專案', 'complete', '歸檔', 'archive', '進度', 'log', '列出專案', 'list projects', '專案狀況', or when the user mentions a specific project name in combination with an action/task operation (e.g., '在 build-blog 加個 action'). This is the central skill for anything that references a named project.
TwinMind review and maintenance engine. Use for vault health checks, seed card review, index verification/rebuild, MOC management, and vault status summaries. Triggers on: 'vault status', '知識庫狀況', 'health report', '健康報告', 'verify index', '檢查索引', 'rebuild index', '重建索引', 'review seeds', '有哪些 seed', 'update MOC', or any request about knowledge base maintenance and overview.