菜单
The closing step of every task — codify what was learned so the system gets better each use. Use after completing any task where the agent was corrected, a bug was found, a procedure was discovered, or friction repeated. Also on request ("capture this", "make sure we don't repeat that").
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/aiosbrain/aios-workspace --skill compound-learnings命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Manage the AIOS Linear board (the ONLY PM tool — Plane is retired). Use whenever updating, reading, or commenting on AIOS Linear issues (identifiers like AIO-72, AIO-75), the brain→PM projection-tracking epic, or the backlog. Triggers on "update AIO-NN", "the Linear board", "the AIOS board", "projection tracking issue", "/aios-linear". Provides a terse `linear.mjs` CLI so issue edits are one fast command instead of ad-hoc GraphQL one-liners. DO NOT use the Plane MCP for AIOS work — it is retired and its tools return huge irrelevant payloads.
Use YOUR own Slack to act as you — send messages and DMs to teammates, read your channels/DMs, and react — via the `slack` CLI (a zero-dependency tool that talks straight to the Slack Web API with your USER token). Messages post AS you and replies land in your own DMs. This is the INDIVIDUAL "act as me" connector — distinct from the team's read-only Slack history ingestion. Use when the user asks to message/DM a teammate on Slack, read a Slack thread/DM, or react. Requires Slack connected (run `aios connect slack`).
Verify that a fix or change actually did what it was for, before reporting that it works. Use before any "it works", "verified", "fixed", "confirmed", or "done" about something that was previously broken — and whenever a hook or a reviewer asks you to re-check a claim. Catches the failure where you measure a proxy (a neighbouring count, an absence of errors, a ratio) instead of the property the change exists to produce.
基于 SOC 职业分类
正在显示 SKILL.md
| name | compound-learnings |
| description | The closing step of every task — codify what was learned so the system gets better each use. Use after completing any task where the agent was corrected, a bug was found, a procedure was discovered, or friction repeated. Also on request ("capture this", "make sure we don't repeat that"). |
| source | Kieran Klaassen (compound engineering — the fourth step); Mitchell Hashimoto (mistake → guardrail reflex); Boris Cherny (CLAUDE.md as error-ledger) |
| am_pattern | A1, C1 |
| triggers | ["lessons learned","compound learnings","postmortem","post-mortem","capture what we learned"] |
"The first three steps produce a feature; the fourth produces a system that builds features better." You are running the compound step: turn this task's lessons into durable artifacts so no one — human or agent — pays for the same lesson twice.
Harvest. Scan the task you just finished for compoundable material:
Choose the strongest container that fits. Escalate up this ladder — prefer enforcement over advice:
| Lesson type | Container |
|---|---|
| Must NEVER happen (secret, protected path, destructive op) | a hook/guard — guaranteed, not advisory |
| Mechanical rule a tool can check | a lint rule / type / CI check |
| Repeatable procedure with judgment in it | a skill (see skill-author) |
| Repeated command sequence | a script / slash-command |
| Convention or gotcha an agent must know | one line in AGENTS.md (error ledger, dated) |
| Correctness fact about the code | a test |
Write it now, in this session — small and specific. A one-line AGENTS.md entry shipped today beats a perfect skill never written. Date error-ledger entries.
Prune while you're there. If an AGENTS.md line has graduated into a hook or formatter, delete the line. The ledger stays short or it stops being read.
Ask: if the same situation arises next month in a fresh session with no memory of today, does the artifact you just wrote prevent the mistake or shortcut the work? If not, it's a diary entry, not a compounding step — sharpen it.
