基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/Integralist/agent-skills --skill recap命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
MANDATORY for any work on Go files (*.go). Load this before editing, reviewing, or creating any *.go file. Go coding conventions and style guide covering naming, error handling, testing, HTTP handlers, caching, concurrency, and observability.
Rewrite text to be more concise, clear, and direct without losing critical information. Inventories load-bearing details first, rewrites, then audits the rewrite to verify nothing essential was dropped — for a plan, technical guide, agent instructions, or any prose too long or hard to follow.
Write or improve technical documentation. Applies documentation best practices: brevity, focusing on why and what rather than how, simple visualizations, modularization, and decoupling from volatile code. Use when writing new documentation from scratch, or editing, or reviewing and rewriting existing documents for clarity and quality.
| name | recap |
| description | Recap the current session — what's done, in progress, and next. |
| disable-model-invocation | true |
| argument-hint | (optional) a specific thread or task to recap |
Summarise the current session in chat. Do not write a file — for a
durable handoff document, that's handoff.
Structure the recap under three headings, each a short bullet list:
Lead with state, not narration. Keep the whole thing to ~10 lines; omit a heading that has nothing under it. If arguments name a specific task or thread, recap only that.