菜单
Triage the user's inbox into reply-now, later, and archive buckets, grounded in their arc-starter context layer so priority reflects who actually matters to them. Trigger when the user asks to "triage my inbox", "sort my emails", "what should I reply to first", or uses "/triage".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Join an existing ARC company brain. For a teammate who has cloned the shared company repo and wants to get set up without re-running the business interview. Trigger on "join the company brain", "join an existing company", "I was added to the team brain", or "/join-company".
Promote one or more private articles into the shared company wiki, with a re-check for sensitive content and founder confirmation. The reviewed path by which a company-mode brain grows. Trigger on "share this", "promote this to the team", "this should be company knowledge", or "/promote".
LLM-assisted resolution of git merge/rebase conflicts in the ARC wiki. Unions additive knowledge, flags genuine contradictions for the founder, and continues the operation. Trigger on "fix the conflicts", "reconcile", "merge these changes", or when a rebase/merge is in progress with unmerged paths.
Manually pull, commit, and push ARC changes to GitHub. The primary git-sync path for Codex users (since Codex's Stop event doesn't fit auto-push). Trigger when the user asks to push their changes, sync to GitHub, save to GitHub, or uses "/sync".
Convert a personal ARC second brain into a shared company brain. A deliberate, reviewed ritual that crosses a trust boundary — default-deny, founder-approved, never a one-click switch. Trigger on "make this a company brain", "share this with my team", "upgrade to company", "set up the team version", or "/upgrade-to-company".
Lightweight daily wiki garden pass. Surfaces stale notes, orphans, weak links, sparse stubs, and daily promote candidates in wiki/garden-{date}.md for founder review before applying. Trigger when the user asks to garden the wiki, run daily maintenance, declutter the wiki, or uses "/garden".
| name | triage |
| description | Triage the user's inbox into reply-now, later, and archive buckets, grounded in their arc-starter context layer so priority reflects who actually matters to them. Trigger when the user asks to "triage my inbox", "sort my emails", "what should I reply to first", or uses "/triage". |
| metadata | {"short-description":"Inbox triage into reply-now / later / archive, context-aware"} |
Triage the user's inbox into three buckets: reply now, later, archive.
Default window is the last 24 hours. If the user provides a different window as an argument (e.g. "last 3 days"), use that.
Gmail MCP — unread threads in the window, plus starred unread older threads. Skip newsletters, receipts, marketing, automated notifications.
The user's context layer (this arc-starter folder)
context/ — client and project notes, so priority is grounded in
who actually matters to them right nowMemory/workspace.md if present — stated focus for this weekRecent meetings (Granola MCP, if connected) — last 7 days, to spot follow-ups they owe people from this week's conversations
Reply now: someone's explicitly blocked on them, time-sensitive deadline, a client in their active context, or a follow-up promised in a recent meeting.
Later today / this week: meaningful but not blocking.
Archive / ignore: not worth reading in full. Explain why briefly.
Markdown, compact. One line per thread.
One line. Low-priority thread the context layer says matters. Or "nothing flagged."