菜单
Review cowork project outputs and sync the workspace-level README.md and log.md in cowork_projects/. Use when cowork agents have done work and the workspace index needs to be updated, or when the user says "sync cowork", "review cowork status", or "update cowork workspace".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Calibrate the Claude Code statusline against the real /usage numbers. Use when the user shares a screenshot of the in-app `/usage` panel (or the claude.ai Settings → Usage page) and wants the statusline's "time left", session %, and weekly % to match what Claude actually reports. Fixes ccusage block-drift, where the local 5-hour clock starts from the first transcript message instead of the real server-side reset.
Dispatch a review task to Gemini CLI (large-context review — plans, docs, large file corpora) or Codex CLI (code review — diffs, PRs, implementation quality). Routes based on the nature of the artifact being reviewed. Use from achieve-goal, literature-survey skills, or any skill that needs a CLI-based review gate. This is a headless CLI review gate over a concrete artifact (code, diff, or doc corpus); for an interactive second opinion or a side-by-side model comparison via MCP chat, use consult-llm instead.
Use when the user wants a second opinion from Gemini or OpenAI/ChatGPT, asks to "consult" another model, or wants to compare responses across models. This is the interactive MCP chat path for a second opinion or model comparison; to run a structured review gate over code, diffs, plans, or large doc corpora through a headless CLI, use cli-review instead.
Use this skill when deciding whether and how to update the knowledge base at /path/to/works/for/you/knowledge_base/ after completing a task. This is the post-task "does this work belong in the KB, and where" decision path; to turn a pasted LLM conversation transcript into a KB note use kb-from-conversation instead.
Periodic review of the memory system at ~/.claude/memory/ for duplicates, redundancies, conflicts, and stale entries. Use when the user asks to audit, clean up, or review memory. Presents findings with enforcement trade-off context — never retires anything without user confirmation. Scoped to the agent memory files under ~/.claude/memory/; for the same kind of duplicate/stale/conflict audit over the knowledge base at /path/to/works/for/you/knowledge_base/ use kb-sweep instead.
Use this skill when the user wants to "promote", "move", "upgrade", or "migrate" a project-level skill, agent, or rule (e.g. a Cursor rule, a project-local AI rule, or any .md skill/agent file) into a global Claude scope. By default always promotes to global (~/.claude/skills/, ~/.claude/agents/, ~/.claude/CLAUDE.md) unless the user explicitly says "project-level". Moves the file so it is shared across all projects and symlinks it back so the original project is not broken. This keeps the skill private to your global ~/.claude scope; to publish skills to the public agent_skills GitHub repo, use publish-skills instead.
| name | cowork-sync |
| description | Review cowork project outputs and sync the workspace-level README.md and log.md in cowork_projects/. Use when cowork agents have done work and the workspace index needs to be updated, or when the user says "sync cowork", "review cowork status", or "update cowork workspace". |
Updates the workspace-level index (cowork_projects/README.md and cowork_projects/log.md) by reading each cowork project's current state. These workspace-level files are Claude Code's responsibility — cowork agents must not touch them.
kb-update to promote cowork outputs to canonical KB| File | Owner |
|---|---|
cowork_projects/README.md | Claude Code — this skill updates it |
cowork_projects/log.md | Claude Code — this skill appends to it |
cowork_projects/CONVENTIONS.md | Claude Code — never touch |
<project-name>/README.md | Cowork agent — read-only from this skill's perspective |
<project-name>/log.md | Cowork agent — read-only from this skill's perspective |
List all subdirectories inside knowledge_base/projects/cowork_projects/. Ignore files at the workspace root (CONVENTIONS.md, README.md, log.md). Each subdirectory is a cowork project.
For each project folder found, read:
<project-name>/README.md — current state, findings, proposed KB destination, open questions<project-name>/log.md — append-only event timelineClassify each project into one of three states based on its README:
Compare each project's most recent log.md date against the last sync entry in cowork_projects/log.md. Only projects with new log entries since the last sync need to be reflected in the workspace log.
Rewrite the workspace README to reflect the current state of all projects. Use this structure:
---
title: Cowork Projects
summary: Sandbox workspace for Claude.ai web ("cowork") task outputs. Claude Code reviews and promotes content from here into the canonical KB.
topics: [cowork, workflow, sandbox]
status: active
updated: <today's date>
---
<!-- BEGIN KB_INDEX -->
# cowork_projects/
Sandbox workspace for Claude.ai web ("cowork") task outputs. Cowork writes here; Claude Code reviews and promotes to canonical KB. See `CONVENTIONS.md` for cowork operating rules.
## Key Topics
cowork, workflow, sandbox, conventions, kb-maintenance
## Files
| File | Summary | Topics | Status | Updated |
|------|---------|--------|--------|---------|
| CONVENTIONS.md | Authoritative operating conventions for cowork agents: boundary rules, per-task folder structure, README vs log.md conventions, and handoff protocol | cowork, workflow, sandbox, conventions, kb-maintenance | active | <date> |
| log.md | Append-only timeline | — | active | <date> |
## Subfolders
| Folder | Description | Key Topics |
|--------|-------------|------------|
<one row per project, summary drawn from project README>
<!-- END KB_INDEX -->
## Active projects
<list each active project: name, one-line status, last log entry date>
## Pending promotion
<list each pending_promotion project with: name, suggested KB destination from project README, any open questions>
## Stale projects
<list stale projects with their last activity date — or omit section entirely if none>
For each project that has new activity since the last sync, append one line:
## [YYYY-MM-DD] update | <project-name>: <one-liner drawn from most recent project log entry>
If multiple projects updated, write one line per project. Always add a final sync line:
## [YYYY-MM-DD] sync | cowork-sync ran; <N> project(s) reviewed, <M> updated
Summarize:
kb-update promotion is recommended