菜单
Use when proposals, reports, plans, manuals, acceptance materials, or other project documents must become final-facing deliverables. Owns reader-ready wording, stale-claim removal, draft-language cleanup, and process-leak checks.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | material-final-editor |
| description | Use when proposals, reports, plans, manuals, acceptance materials, or other project documents must become final-facing deliverables. Owns reader-ready wording, stale-claim removal, draft-language cleanup, and process-leak checks. |
Final-facing project materials fail when agents leave stale project names, objectives, metrics, partners, responsibilities, or draft-process text in the submitted document. This skill keeps the work focused on what the reader must trust: current project identity, correct scope, clear responsibilities, and content that reads like a deliverable rather than a work log.
Own final-facing content editing for project materials.
Does not own DOCX/Markdown conversion, source-vs-derived file handling, snapshot policy, or low-level document extraction.
references/final-material-review-checklist.md: read for full proposal, report, acceptance material, manual, or adapted-document review.Use when the requested output is maintainable text diagram source for docs, specs, architecture notes, workflows, data flows, sequences, models, or lightweight timelines. Supports Mermaid, PlantUML, D2, and ASCII. Do not use for polished document/slide figure assets, raster visual-reference passes, or UI mockups.
Use when creating, redesigning, revising, or quality-checking explanatory figure assets for documents or slides, including architecture, workflow, process, API, data-flow, algorithm, concept, infographic, and text-heavy figures. Owns DOCX/PDF/PPT-ready raster/SVG assets, mandatory AI-generated visual-reference passes for generated figures, Chromium/Playwright rendering, and readability QA, not whole-slide, page, or deck layout.
Use before or during cross-module work where documented contracts and implementation must stay aligned, including shared types, config, schemas, serialization, runtime state, pipeline boundaries, or public behavior. Owns contract-first fixes and independent review for substantial contract changes.
Use when the user wants to discover, compare, evaluate, update, or install catalog/repo-sourced agent skills, including asking whether a capability exists as an installable skill. Do not use for ordinary one-off work the agent should perform directly.
Use when revising existing skills or skill sets to fix routing, boundaries, rationale, workflow, validation, metadata, or observed agent failures. Owns trigger-focused, self-contained skill revisions with eval checks and lean descriptions.
Use when document source files and exported deliverables must be inspected, converted, regenerated, or preserved. Owns DOCX, Markdown, PDF, and similar source-vs-derived file roles, inventory, conversion, snapshots, and regeneration decisions.