菜单
Sweep the current session for uncaptured durable knowledge and file it to disk before a context reset. Use when the captain invokes /stow (e.g. "/stow", "stow what you've learned"), before a session reset or context compaction, or periodically to keep operational memory current.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/korallis/firstmate-lee --skill stow命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Agent-only reference for firstmate harness operations. Use before spawning or recovering a crewmate or secondmate, handling a trust dialog, sending a harness-specific skill invocation, interrupting or exiting an agent, resuming an exited agent, or verifying a new harness adapter. Contains verified facts for claude, codex, opencode, pi, and grok, plus the Cursor C0 primary-session detection caveat.
Generate a "pick up where I left off" status report from firstmate's live fleet state. Use when the captain invokes /bearings or asks for a bearings report, morning brief, status report, catch-up, "where did I leave off", or "what's in the works". Reads live fleet state cheaply (backlog, per-task crew state, open PRs, scout reports, pending decisions, date-gated queued work), composes a scannable dated report to data/status-report-<YYYY-MM-DD>.md, and surfaces a concise version in chat; it is read-mostly and must not tear down, merge, or mutate task state as a side effect of producing the brief.
Agent-only reference for persistent secondmate setup and retirement. Use when creating, seeding, validating, launching, recovering, handing backlog to, pushing inherited config into, or retiring a secondmate home, or when editing data/secondmates.md. Covers home leases, transactional seeding, project clone restrictions, secondmate harness pins, inherited config push, idle charter, handoff helper, and teardown safety.
基于 SOC 职业分类
正在显示 SKILL.md
| name | stow |
| description | Sweep the current session for uncaptured durable knowledge and file it to disk before a context reset. Use when the captain invokes /stow (e.g. "/stow", "stow what you've learned"), before a session reset or context compaction, or periodically to keep operational memory current. |
| user-invocable | true |
| metadata | {"internal":true} |
Sweep this session for durable knowledge that only exists in conversation right now, and write it to the disk locations firstmate already prints in the next session-start context digest. The goal is a session that is safe to reset or destroy because everything durable has already been captured.
Sweep the session for uncaptured durable knowledge. Read back over this conversation and look for:
data/captain.md directly.AGENTS.md.Route each finding using AGENTS.md's knowledge-routing table. AGENTS.md (section 6, "Knowledge routing") is the single source of truth for where each kind of knowledge belongs. Read that table and route each finding there instead of re-deriving the mapping here.
Write within firstmate's existing write boundaries. This skill does not grant any new write permission; it only prompts firstmate to use the boundaries that already exist (AGENTS.md section 1):
data/captain.md and data/learnings.md respectively.
data/learnings.md may not exist yet; create it on first learning, in the same dated, evidence-backed, curated style as data/captain.md - rewrite and prune stale or superseded entries rather than appending forever.AGENTS.md.
Route it through a normal ship task so a crewmate records it via bin/fm-ensure-agents-md.sh and commits it through that project's delivery pipeline, exactly as section 6 describes.
If the fleet is live, delegate this to a crewmate rather than doing it inline.AGENTS.md (or other shared, tracked material), shipped through the normal branch -> no-mistakes -> PR -> captain-merge pipeline for this repo (section 1), never hand-committed straight to main.tasks-axi update <id> --append "<note>", or hand-edit data/backlog.md per the active backend (section 10).blocked-by recorded if it genuinely depends on something else.Curate, don't just append.
When a finding overlaps or supersedes something already on disk, prefer rewriting or pruning the existing entry over piling on a new one.
Graduation moves are limited to exactly three: promote a learning to the shared AGENTS.md via PR, fold it into data/captain.md, or delete a stale entry.
Do not invent other graduation paths.
Report to the captain. Summarize, in plain outcome language (section 9): what was stowed and where, what was filed to the backlog, and whether the session is now safe to reset or destroy - i.e. whether every durable finding from this sweep now lives on disk rather than only in this conversation. If something could not be captured yet (for example, project-intrinsic knowledge waiting on a crewmate to land it), say so explicitly rather than reporting the session fully safe.
/stow must never store, create, or edit a skill as a destination for any finding.
There is no "graduate this to a skill" move in this skill's routing.
This is a deliberate, standing exclusion, not an oversight: even with the two-tier skill layout, a stow sweep is a memory-routing operation, not a way to author or mutate skills.
Writing learnings into either .agents/skills/ or public skills/ would still risk mixing fleet-local material with shared firstmate behavior or standalone installer-facing behavior.
Until a human deliberately scopes a skill change as firstmate repo work, route generalizable knowledge to the shared AGENTS.md (or other shared, tracked material) via the pipeline, and fleet-local knowledge to data/, never to a skill.