메뉴
Refreshes README structure favoring concision (an index, not a manual). Use when the README needs a structural update after significant project changes.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/athola/claude-night-market --skill update-readme명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
SOC 직업 분류 기준
| name | update-readme |
| description | Refreshes README structure favoring concision (an index, not a manual). Use when the README needs a structural update after significant project changes. |
| alwaysApply | false |
| category | artifact-generation |
| tags | ["readme","documentation","exemplars","research","structure"] |
| tools | [] |
| complexity | high |
| model_hint | deep |
| estimated_tokens |
| 1200 |
| modules | ["modules/language-audit.md","modules/exemplar-research.md"] |
| progressive_loading | true |
| dependencies | ["sanctum:git-workspace-review","imbue:proof-of-work","scribe:slop-detector","scribe:doc-generator"] |
Use this skill whenever the README requires a structural refresh.
Run Skill(sanctum:git-workspace-review) first to capture repo context and diffs.
update-readme:language-auditupdate-readme:exemplar-researchupdate-readme:outline-alignedupdate-readme:edits-appliedupdate-readme:slop-scanned - AI marker detection via scribeupdate-readme:verification-reportingupdate-readme:language-audit)pwd, git status -sb, and the baseline branch for reference.See modules/language-audit.md for detailed detection patterns and commands.
update-readme:exemplar-research)See modules/exemplar-research.md for search query patterns and evaluation criteria.
update-readme:outline-aligned)The README is an index, not a manual. Lead with what the
project is, how to install it, and a scannable table of its
units (plugins, commands, packages); link out for everything
else. When this repo's root README was simplified in 2026, it
dropped from 435 to 200 lines (65% fewer words) by deleting
inlined depth and linking to book/ instead. Aim for that
shape, not a section-by-section coverage sweep.
rg -n '^#' README.md)
against the exemplars from Step 2. Lean marketplace and
CLI-tool READMEs (asdf-vm/asdf-plugins, ohmyzsh/ohmyzsh,
ryoppippi/ccusage) are index-shaped: prose intro under ~500
words, a unit table doing the work, depth behind links.Soft budget: a marketplace or collection root README runs roughly 150-400 lines of prose plus any index table. A section that grows over time (roadmap, FAQ, changelog) belongs in a linked page, not the README.
update-readme:edits-applied)README.md
(or the specified file).Skill(leyline:markdown-formatting) conventions:
wrap prose at 80 chars (prefer sentence/clause boundaries),
blank lines around headings, ATX headings only, blank line
before lists, reference-style links for long URLs.update-readme:slop-scanned)Run Skill(scribe:slop-detector) on the updated README to detect AI-generated content markers.
The scribe plugin provides AI slop detection:
Skill(scribe:slop-detector) --target README.md
This detects:
If slop score exceeds 2.0 (moderate), apply Skill(scribe:doc-generator) principles:
For significant cleanup needs, use:
Agent(scribe:doc-editor) --target README.md
update-readme:verification-reporting)git diff README.md (or the edited file) and capture snippets for the final report.TodoWrite items are complete.book/ or docs/ page;
depth is linked, not inlined (rg -n '^#' README.md headings
each map to a section that earns a place in an index).Documentation out of sync
Run make docs-update to regenerate from code
Build failures Check that all required dependencies are installed
Links broken Verify relative paths in documentation files
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.