菜单
Calibrates finding importance (high / medium / low) before inbox_add — used by routines for consistent thresholds. Routine-only.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Evaluate multiple choices side-by-side based on relevant criteria, then present a comparison the user can act on. Use when the user asks to compare options, choose between alternatives, or weigh up X vs Y.
Day-of-week rotating proactive sweep — Mon=connections / Tue=routines / Wed=skills / Thu=memories / Fri=findings / Sat=cross-cutting / Sun=weekly summary. Forces outward scan instead of inward thrash. Routine-only; load this skill into a daily routine that fires AssistantAgent. Adapted from goanna's caretaker.
Use when an agent has had N consecutive quiet runs with nothing to do. Pivots to bounded inward consolidation (promote findings, refresh memory, audit asks) anchored in own data — NOT generic news summarisation. Adapted from goanna's reverie cycle. Routine-only; loaded by the routine that detects the quiet condition.
Use to track open questions you owe the user (asks) and time-bounded commitments you owe yourself (tasks). Write OPEN entries when you commit; promote to CLOSED when answered/done. Survives session compaction. Adapted from goanna's asks.md/tasks.md pattern.
Reviewer criteria for AI-generated code via with_review. Checks for security issues (injection, auth bypass, secret leakage), correctness, and project conventions. Use as criteria.skill when generating code that touches data, auth, or external systems.
Reviewer criteria for outbound email drafts via with_review. Checks tone-recipient match, professionalism, no AI tells, no placeholder leakage. Use as criteria.skill argument when reviewing email drafts before send.
| name | score-importance |
| description | Calibrates finding importance (high / medium / low) before inbox_add — used by routines for consistent thresholds. Routine-only. |
| disable_model_invocation | true |
inbox_add accepts an importance field — high, medium, or low. Without consistency, what one routine calls "high" another calls "medium" and the user stops trusting the field.
This skill defines what each level means so all your routines agree.
Action is needed within the day. If the user ignores it, something will break or get worse.
Examples:
Action is helpful within the week. Not blocking, but skipping has a cost.
Examples:
FYI. Skipping has no cost. The user is happy to know but won't act.
Examples:
| Signal | Suggests |
|---|---|
| Time-bound (deadline, expiry) | high |
| Money-bound (cost, revenue) | high or medium |
| Failure / regression | high |
| Volume / count change | medium or low |
| New content (article, video, message) | low (unless from a key relationship) |
| "Should I look at this?" — user-paced | medium or low |
Pair importance with confidence (0..1). High confidence + medium importance is more actionable than low confidence + high importance. If you're not sure something matters, lean low + add a reasoning line so the user can confirm.
high to get the user's attention. The user disables routines that cry wolf.low for things you secretly think are high — that's still crying wolf, just inverted.importance if you genuinely don't know. Leave it null and let the user filter.