菜单
Periodic review for loopany — daily, weekly, or monthly. Triggers: 'what's due today', 'what am I forgetting', 'what's slipping', 'weekly check', 'is the workspace healthy', 'is this still the right mission?', 'anything structural?', session start, daily/weekly/monthly cadence.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Artifact lifecycle for loopany — the agent brain. Use when creating, modifying, or querying any artifact (task, signal, learning, skill-proposal, mission, person, note, brief, journal). Read this SKILL.md first for routing, then the relevant kind's Playbook. Triggers: any artifact CRUD, 'create a task', 'write a signal', 'dismiss signal', 'flip to done', 'what kind should this be', choosing a relation verb.
Self-improvement loop for loopany. Reads recent task outcomes + dismissed signals, discovers patterns, writes learning and skill-proposal artifacts. Also handles accepting/rejecting proposals. Triggers: 'reflect', 'what have we learned', 'improve yourself', ≥3 tasks done recently, 'accept <proposal-id>', 'reject <proposal-id>', 'review proposals', writing a learning or skill-proposal from any source.
Read FIRST in any loopany workspace. Routes user intent to the correct skill, enforces bootstrap, and orchestrates cross-skill chaining. Triggers: any loopany interaction, session start, ambiguous request, 'what should I do', multi-skill workflow.
Migrate a loopany workspace from v0.1.0 to v0.2.0. Strips kind ID prefixes (tsk-/sig-/lrn-/...), flattens date-bucketed storage to artifacts/<dirName>/, renames snake_case frontmatter to camelCase, auto-stamps createdAt/updatedAt, builds the journal index, and adds the journal kind. Triggers when bootstrap throws SchemaVersionMismatchError pointing at this skill.
Auto-capture after substantive work concludes. Routes events (PR shipped, incident resolved, decision made, problem noticed) to the right loopany artifact kind with a quality gate. Should run proactively — check this skill at the end of every user-requested task. Triggers: after any substantive work, 'record this', 'log this outcome', PR shipped, incident resolved, decision made, problem noticed but deferred.
| name | loopany-review |
| description | Periodic review for loopany — daily, weekly, or monthly. Triggers: 'what's due today', 'what am I forgetting', 'what's slipping', 'weekly check', 'is the workspace healthy', 'is this still the right mission?', 'anything structural?', session start, daily/weekly/monthly cadence. |
One skill, three frequencies. Each adds scope; all share the same closure gate.
| Freq | Scope | Trigger | Read |
|---|---|---|---|
| daily | checkAt = today | "what's due today", session start | references/daily.md |
| weekly | overdue + parking lots + doctor | "what's slipping", "weekly check" | references/weekly.md |
| monthly | mission alignment + structural drift | "right mission?", "anything structural?" | references/monthly.md |
Don't mix scopes. One week of overdue is a pattern; one day isn't.
Frequency-specific — see the reference file.
Read each: loopany artifact get <id>
checkAt with a one-line reason.checkAt forward with a reason.For learnings: loopany trace <learning-slug> --direction backward
Only bucket B. One line per item:
3 things need you today:
1. [<task-slug>] 2-week recheck — did $/session settle?
2. [<learning-slug>] "short deals close 2.5x faster" — still true?
3. [<signal-slug>] recurring churn signal, 3rd time. Upgrade?
Empty → say so and stop.
Route to kind playbooks in loopany-core:
../loopany-core/kinds/task.md § Playbook../loopany-core/kinds/learning.md § Playbook../loopany-core/kinds/signal.md § Playbook../loopany-core/kinds/mission.md § PlaybookEvery surfaced item must end the session in one of:
checkAt pushed with reason. "Not yet" isn't a reason.checkAt removed with note.No zombie items. A digest without state changes is noise.
DAILY: followups --due today → classify → surface → dispatch → close
WEEKLY: doctor + overdue + parking lots → classify → surface → close → feed reflect
MONTHLY: mission alignment + structural drift → surface → user decides
GATE: every surfaced item → resolved / deferred / retired