菜单
Generates or remediates documentation with human-quality writing. Use when creating new docs, rewriting AI-generated content, or applying style profiles.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/athola/claude-night-market --skill doc-generator命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Turn hunches into accepted results: worthiness score, evidence bar, research-to-rules. Use when vetting ideas. Not for QA; use night-market-validation-and-qa.
Generates and self-executes a diff-derived test plan for a PR. Use when validating PR changes before merge. Do not use for code review; use sanctum:pr-review.
Curate the web-capture index. Use when the capture backlog grows, captures sit unprocessed at seedling/pending, or to surface stored research during work.
正在显示 SKILL.md
基于 SOC 职业分类
| name | doc-generator |
| description | Generates or remediates documentation with human-quality writing. Use when creating new docs, rewriting AI-generated content, or applying style profiles. |
| globs | **/*.md |
| alwaysApply | false |
| category | artifact-generation |
| tags | ["documentation","writing","generation","remediation","polish"] |
| tools | [] |
| complexity | medium |
| model_hint | standard |
| estimated_tokens | 1600 |
| progressive_loading | true |
| modules | ["modules/generation-guidelines.md","modules/remediation-workflow.md","modules/quality-gates.md"] |
| dependencies | ["scribe:slop-detector"] |
A document costs the sum of its readers' time. Earn that cost or cut.
Generate documents that are grounded in specific claims, lead with their thesis, and earn every sentence. Filler phrases like "In today's fast-paced world" and vague descriptors like "thorough" or "complete" without evidence are bloat. So is any sentence that does not carry, instance, bound, or repeat the document's one takeaway.
This skill enforces both sentence-level cleanliness (no
slop vocabulary, em dash overuse, or sycophantic openers) and
document-level economy (thesis-first, every sentence
earns weight, repetition reserved for the thesis). See
Skill(scribe:slop-detector) module document-economy.md
for the full rubric.
scribe:doc-importer)scribe:slop-detector)Use active voice and an authorial perspective. Explain the reasoning behind technical choices (why this database, not that one) rather than presenting neutral boilerplate. Use bullets sparingly for short, parallel summaries. Convert multi-line bullet waterfalls into prose so the reasoning survives.
Avoid business jargon and linguistic tics like mirrored sentence structures or em dash overuse. Use the imperative mood for docstrings ("Validate input", not "Validates"). Do not humanize non-living constructs ("the code wants", "the function speaks to").
| Instead of | Use |
|---|---|
| fallback | default, secondary |
| leverage | use |
| utilize | use |
| facilitate | help, enable |
| comprehensive | thorough, complete |
"Lives under," "speaks to," and similar phrases only make sense for living things.
"Validate" not "Validates" (per PEP 257, pydocstyle, ruff).
doc-generator:scope-defined - Target files and type identifieddoc-generator:style-loaded - Style profile applied (if available)doc-generator:content-drafted - Initial content createddoc-generator:slop-scanned - AI markers checkeddoc-generator:quality-verified - Principles checklist passeddoc-generator:user-approved - Final approval receivedFor new documentation:
## Generation Request
**Type**: [README/Guide/API docs/Tutorial]
**Audience**: [developers/users/admins]
**Audience size**: [1 / small team / org / public]
**Read frequency**: [once / weekly / per-invocation]
**Thesis**: [one sentence the reader must walk away with]
**Length target**: [~X words or sections]
**Style profile**: [profile name or "default"]
The Thesis field is required. If you cannot state the
takeaway in one sentence, the scope is not ready. Audience
size and read frequency feed the reader-time budget (see
scribe:slop-detector module document-economy.md): a
skill loaded daily by 50 users has a wildly different
budget than a 1:1 design note.
If a style profile exists:
cat .scribe/style-profile.yaml
Apply voice, vocabulary, and structural guidelines.
Lead with the thesis. The first paragraph must state the single takeaway. If a reader stops after the lead, they should still leave with the message. Echo the thesis once in the body and once at the close. Cut every other repetition.
Follow the 10 core principles above. For each section:
Skill(scribe:slop-detector)
Fix any findings before proceeding.
Verify against checklist:
Sentence-level:
Document-level (document-economy module):
For cleaning up existing content:
Load: @modules/remediation-workflow.md
# Get slop score
Skill(scribe:slop-detector) --target file.md
For large files (>200 lines), edit incrementally:
## Section: [Name] (Lines X-Y)
**Current slop score**: X.X
**Issues found**: [list]
**Proposed changes**:
1. [Change 1]
2. [Change 2]
**Before**:
> [current text]
**After**:
> [proposed text]
Proceed? [Y/n/edit]
Never change WHAT is said, only HOW. If meaning is unclear, ask.
After edits, re-run slop-detector to confirm improvement.
When editing code comments:
modules/generation-guidelines.md for content creation patternsmodules/quality-gates.md for validation criteria| Skill | When to Use |
|---|---|
| slop-detector | After drafting, before approval |
| style-learner | Before generation to load profile |
| sanctum:doc-updates | For broader doc maintenance |