菜单
Use when creating, editing, converting, polishing, checking, or inspecting public-facing artifacts such as DOCX, PDF, PPTX, TikZ diagrams, manuscript figures, or manuscripts being prepared for journal submission.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Planning-centric workflow for substantial work across software, analyses, artifacts, documentation, and configuration. Invoke manually with $work-cycle when alignment matters; not for straightforward one- or two-edit requests.
Create or update developer-facing and agent-facing project documentation, or run module-scoped codebase audits. Invoke manually with $documentation for codebase maps, module documentation, codebase review/audit workflows, and README.md or AGENTS.md work.
Documentation subskill for project hygiene maintenance. Use through $documentation when the user asks to maintain, clean up, health-check, refresh AGENTS.md/notebook/TODOs, inspect git branches/PRs/stashes, or review overall project state. Do not use for codebase audit, codebase review, release-check, or module-scoped bug-finding requests; those belong to module-codebase-review.
Manual-only workflow for codebase audit, codebase review, release-check, paper-freeze-check, and module-scoped multi-agent read-only bug/code-smell audits that produce a prioritized notebook report and TODO-ready findings. Use this instead of maintain-project for requests that ask to audit or review code behavior.
Ergonomic notebook-backed TODO capture for deferred work. Invoke manually with /defer when the user asks to defer, save, park, or add a TODO for later work while preserving the current conversation context.
Initialize a project workspace for Claude Code with project instructions, repository checks, notebook scaffolding, optional remotes, and optional O2/SLURM setup. Invoke manually with /init-project for first-time project setup, notebook bootstrap, project remotes, or O2/SLURM setup.
| name | artifacts |
| description | Use when creating, editing, converting, polishing, checking, or inspecting public-facing artifacts such as DOCX, PDF, PPTX, TikZ diagrams, manuscript figures, or manuscripts being prepared for journal submission. |
| recommended_scope | global |
Choose the appropriate internal subskill for the artifact type, then read only that subskill's SKILL.md and supporting files:
subskills/docx/ for Word documents.subskills/pdf/ for PDF files and forms.subskills/pptx/ for PowerPoint presentations.subskills/tikz-flowchart/ for TikZ/LaTeX flowcharts, schematics, and diagrams.subskills/polished-manuscript-figure/ for manuscript figure styling, critique, and journal-ready visual presentation.subskills/finalize-manuscript/ for pre-submission and resubmission manuscript checklists; use when the user says "finalize manuscript", "check manuscript", "pre-submission check", "manuscript checklist", "ready to submit", or asks to prepare a manuscript for journal submission.Artifacts should have a high signal-to-noise ratio: prioritize the message, evidence, and user's concrete purpose over decoration or exhaustive process notes.
Artifacts meant for public consumption should avoid path dependence. Do not refer to previous versions, user prompts, or the process that produced the artifact; those references would not make sense to a reader besides the user.