Docs & writing
16,632 rows, by stacks then stars
3,030 of these skill files have been read, by 1,951 distinct authors, and what they tell an agent counted. What Docs & writing authors agree on, and what they forbid
urmzd/dotfiles/dot_agents/skills/choose-stack Skill
3★ repoCanonical tech-stack reference organized by purpose: release/versioning (sr), docs/demos (teasr, fsrc), codegen (oag), and per-language tools (cargo, clippy, clap, golangci-lint, biome, tsdown, uv, ruff, ty, pytest, pydantic, fastapi). Use when choosing a library, picking the standard CLI/linter/logging tool for a language, setting up a project, or asking "what do we use for X." Do NOT use for coding patterns or error-handling idioms (use write-code) or testing frameworks in depth (use test-code).
urmzd/dotfiles/dot_agents/skills/clean-docs Skill
3★ repoClean and modernize documentation in place. Enforce no em dashes, readable structure, proper Markdown formatting, accurate commands, current examples, resolved internal links, and user-focused guidance. Use when the user invokes /clean-docs, asks to clean docs, make docs up to date, improve README/AGENTS prose, remove AI-looking punctuation, or make docs easier for users to act on.
urmzd/dotfiles/dot_agents/skills/configure-ai Skill
3★ repoAuthors AGENTS.md and defines the skills-vs-docs boundary for a repo. Configures AI coding tools (Claude Code, Codex, Antigravity CLI, Copilot) and the skills-as-docs philosophy. Use when creating or auditing AGENTS.md, setting up AI tooling for a project, or deciding what belongs in a skill versus docs/. Do NOT use for README structure -> use write-readme; for llms.txt generation -> use create-llms-txt; for Claude-specific skill features (invocation control, subagents, model overrides) -> use extend-oss-skills-to-claude.
urmzd/dotfiles/dot_agents/skills/sync-docs Skill
3★ repoAudit and synchronize project documentation. Enforce clean prose, no em dashes, evidence-backed accuracy, current embedded examples, command drift checks, and cross-reference consistency. Use after feature changes, refactors, stale docs, README/AGENTS/llms.txt edits, or when the user asks to clean up docs. Delegates file-specific structure to owning skills.
urmzd/dotfiles/dot_agents/skills/test-code Skill
3★ repoTesting philosophy, test types (unit, integration, golden, fuzz, property, benchmark, smoke, E2E), per-language conventions (Rust, Go, Python, TypeScript), file organization, fixtures/mocks, CI strategy, and what NOT to test. Use when writing tests, reviewing test coverage, setting up test infrastructure, or deciding what to test. Do NOT use for general implementation patterns or error handling (use write-code) or design-by-contract reasoning (use review-design).
urmzd/dotfiles/dot_agents/skills/write-code-portfolio Skill
3★ repoPersonal portfolio dev-setup: add or remove a package/tool in flake.nix per-language shells, edit chezmoi installer scripts, and adjust Powerlevel10k (dot_p10k.zsh), Nix, or Neovim (private_dot_config/nvim) machine config. Use when editing chezmoi-managed dotfiles, adding/removing a language toolchain or CLI to a Nix shell, changing the zsh prompt, tweaking Neovim, branching dotfiles on machine attributes (is_macos / is_personal / is_work), or bootstrapping a new machine in this portfolio. Do NOT use for portable coding patterns or general tech-stack picks; use write-code for those.
urmzd/dotfiles/dot_agents/skills/write-code Skill
3★ repoOperational tech-stack picks and coding patterns: error handling per language, commit conventions, interface design (Go SDKs), workspace layout, junior-friendly bias. Use when writing or reviewing implementation code and you need a concrete answer for "what tool, pattern, or idiom." Do NOT use for design-tradeoff reasoning (use review-design) or the quality framework (use assess-quality). Personal Nix / chezmoi / Powerlevel10k / Neovim machine specifics live in write-code-portfolio; use that for portfolio-only setup.
urmzd/dotfiles/dot_agents/skills/write-readme Skill
3★ repoStructures and writes a project README: centered header, badges, demo image, section order, install.sh one-liner, Quick Start, fsrc code embeds, and the Agent Skill section. Use when creating or updating any project's README.md. Do NOT use for AGENTS.md or the skills-vs-docs taxonomy -> use configure-ai (configure-ai owns AGENTS.md and the docs taxonomy; write-readme owns README structure). For llms.txt generation -> use create-llms-txt.
br3eze-code/br3eze-code/.claude/skills/writing-guidelines Skill
3★ repoReview docs/prose for Writing Guidelines compliance. Use when asked to "review my docs", "check writing style", "audit prose", "review docs voice and tone", or "check this page against the writing handbook".
The same file is in 2 other repositories
br3eze-code/br3eze-code/docs Skill
3★ repoPersonal Ai Agent
judicael-s/Copywriting-skill/skills/french-copywriting Skill
3★ repoWhen the user wants to write, rewrite, or improve marketing copy in French. Use when the user says 'French copy,' 'copywriting en francais,' 'ecrire en francais,' 'landing page francais,' 'CTA francais,' 'redaction web,' 'redaction publicitaire,' 'copy FR,' 'French landing page,' 'texte marketing francais,' 'page de vente,' 'accroches en francais,' or any request to write marketing text in French. For English copy, see copywriting. For social media copy, see social-copywriting. For defining brand voice first, see tone-of-voice.
judicael-s/Copywriting-skill/skills/seo-copywriting Skill
3★ repoWrite SEO-optimized content — blog posts, articles, product pages, pillar pages, FAQ pages, and local SEO pages. Triggers on: 'SEO copy', 'optimize for search', 'write a blog post', 'rank for keyword', 'SEO content', 'content brief', 'optimize this page', 'meta description', 'title tag', 'featured snippet', 'topic cluster', 'pillar page', 'keyword research'. For conversion copy without SEO focus see copywriting. For French SEO see french-copywriting. For social media see social-copywriting.
judicael-s/Copywriting-skill/skills/social-copywriting Skill
3★ repoWrite platform-native copy for LinkedIn and X/Twitter — posts, threads, carousels, and polls. Triggers on: 'LinkedIn post', 'tweet', 'thread', 'X post', 'social media copy', 'write a post for LinkedIn', 'write a tweet', 'LinkedIn carousel', 'Twitter thread', 'social copy', 'post for X', 'LinkedIn hook', 'viral tweet', 'write a thread', 'help me post on LinkedIn/X'. Focuses on WRITING copy, not strategy or scheduling. For web page copy see copywriting. For French copy see french-copywriting. For defining brand voice first see tone-of-voice.
judicael-s/Copywriting-skill/skills/tone-of-voice Skill
3★ repoDefine, create, or refine a brand's tone of voice, writing voice, or content style. Triggers on: 'tone of voice', 'brand voice', 'voice guide', 'how should we sound', 'define our tone', 'brand personality', 'writing guidelines', 'voice and tone', 'content style guide', 'brand language', 'we need a consistent voice', 'our copy sounds inconsistent'. Run this BEFORE using copywriting, french-copywriting, or social-copywriting skills. For writing actual copy see copywriting. For French copy see french-copywriting. For social media copy see social-copywriting.
fastfold-ai/skills/skills/slack_report Skill
no license3★ repoShare markdown reports to the user's configured Slack agent_cli_report channel via Fastfold API, and persist the markdown as a library item.
Yue-Zhou1/zkcrypto-audit/.codex/skills/crypto-report-writer Skill
3★ repoWrite final audit findings for ZK and cryptographic reviews. Use when a finding has survived verification and needs to be turned into clear report prose with severity, impact, root cause, and test evidence.
Yue-Zhou1/zkcrypto-audit/plugins/core-audit-flow/skills/crypto-report-writer Skill
3★ repoWrite final audit findings for ZK and cryptographic reviews. Use when a finding has survived verification and needs to be turned into clear report prose with severity, impact, root cause, and test evidence.
KrishnaShettyDev/dosed/write Skill
3★ repoAlcohol-disinhibited first draft writing, then Amphetamine-focused editing. Two-phase writing assistance that kills the inner critic for drafts, then activates perfectionism for polish. Activates with "/write", "help me write", "I need to write...", or writing assistance requests.
jovd83/restassured-skill/analysis/contracts Skill
3★ repoUse when Codex needs to derive Rest Assured test scenarios from OpenAPI or Swagger contracts, including endpoints, methods, schemas, auth rules, status codes, and error conditions.
jovd83/restassured-skill/analysis/requirements Skill
3★ repoUse when Codex needs to extract testable API behavior from epics, user stories, acceptance criteria, tickets, markdown docs, or other prose requirements before generating Rest Assured scenarios.
jovd83/restassured-skill/coverage_plan/generation Skill
3★ repoUse when Codex needs to generate a Rest Assured API test coverage plan from approved requirements, OpenAPI or Swagger contracts, WSDL analysis, and explicit scope constraints.
jovd83/restassured-skill/documentation/assertion-strength-report Skill
3★ repoUse when Codex needs to assess whether Rest Assured tests are weak, moderate, or strong based on the assertions they make, the amount of API behavior they verify, and whether they go beyond status-code checks.
jovd83/restassured-skill/documentation/contract-mismatches Skill
3★ repoUse when Codex needs to document differences between an API contract and the observed live Rest Assured runtime behavior so humans and later agents can implement tests safely and track drift explicitly.
jovd83/restassured-skill/documentation/coverage-gap-report Skill
3★ repoUse when Codex needs to highlight uncovered, partial, drift-only, or weakly covered API areas so humans can prioritize the next Rest Assured work instead of reading the full traceability report.
jovd83/restassured-skill/documentation/documentation-sync Skill
3★ repoUse when Codex needs to keep Rest Assured narrative documentation synchronized with endpoint traceability, coverage rows, and executable tests across BDD, TDD, plain-text, mixed, or partially documented API suites.
jovd83/restassured-skill/documentation/handover Skill
3★ repoUse when Codex needs to produce a concise handover for completed Rest Assured API testing work, including what changed, what remains open, and how to continue safely.
jovd83/restassured-skill/documentation/openapi-change-impact-report Skill
3★ repoUse when Codex needs to compare two OpenAPI or Swagger contracts, identify added, removed, or changed operations and schemas, and map the impact back to existing Rest Assured coverage.
jovd83/restassured-skill/documentation/report-bundle Skill
3★ repoUse when Codex needs to generate or refresh a bundled Rest Assured reporting set, including traceability, contract mismatches, coverage gaps, OpenAPI change impact, assertion strength, and the human-friendly HTML portal, with support for BDD, TDD, plain-text, mixed, or absent narrative documentation.
jovd83/restassured-skill/documentation/root_cause Skill
3★ repoUse when Codex needs to analyze failing Rest Assured API tests, identify the most likely root cause, and produce a developer-focused failure diagnosis.
jovd83/restassured-skill/documentation/session-state Skill
3★ repoUse when Codex needs to persist a durable resume checkpoint for Rest Assured API testing work so a human or later agent can see what is done, what is blocked, and exactly how to continue.
jovd83/restassured-skill/documentation/test_cases/bdd Skill
3★ repoLegacy Rest Assured-specific alias for BDD case formatting. Prefer the standalone `test-artifact-export-skill` skill for Gherkin, BDD, and export-ready case rendering, and use this only when Rest Assured-local conventions must be preserved explicitly.
jovd83/restassured-skill/documentation/test_cases/plain_text Skill
3★ repoLegacy Rest Assured-specific alias for plain-text case formatting. Prefer the standalone `test-artifact-export-skill` skill for lightweight narrative case output, and use this only when Rest Assured-local conventions must be preserved explicitly.
jovd83/restassured-skill/documentation/test_cases/tdd Skill
3★ repoLegacy Rest Assured-specific alias for TDD-style case documentation. Prefer the standalone `test-artifact-export-skill` skill for formatting approved test cases or building export-ready artifacts, and use this only when Rest Assured-local conventions must be preserved explicitly.
jovd83/restassured-skill/documentation/tests Skill
3★ repoUse when Codex needs to add human-readable documentation to Rest Assured automation code, including class purpose, role boundaries, shared specs, and scenario intent.
jovd83/restassured-skill/documentation/traceability-report Skill
3★ repoUse when Codex needs to produce a traceability report that maps API endpoints, methods, operations, coverage rows, Rest Assured tests, and narrative documentation references so humans and later agents can see exactly what is covered across BDD, TDD, plain-text, mixed, or absent documentation.
jovd83/restassured-skill/reporting/stakeholder Skill
3★ repoUse when Codex needs to summarize Rest Assured API test execution for non-technical stakeholders in clear business terms instead of raw test runner output.
raydeveloperF/App-Store-Connect-release-kit/skills/asc-metadata Skill
3★ repoWrite localized ASC metadata for iOS apps, including subtitle, promotional text, and app description. Use when the user asks for App Store Connect listing copy, ASC metadata, localized subtitle, promotional text, or app description. This skill requires project understanding first, and must ask for missing target languages or writing style before producing final copy.
ribeirogab/specwright/plugins/sw/skills/review Skill
3★ repoA multi-host plugin for Claude Code, Codex, and OpenCode. It gives a repository one explicit, change-driven engineering workflow:
hnikoloski/imlazy/skills/imlazy-write-plans Skill
3★ repoUse when you have a spec or requirements for a multi-step task, before touching code
hnikoloski/imlazy/skills/imlazy-write-skills Skill
3★ repoUse when creating new skills, editing existing skills, or verifying skills work before deployment
xonika9/agent-skills/skills/x9-research Skill
3★ repoUse when the user wants a genuinely researched answer from current or primary sources, including X/Twitter or Reddit — «разберись в вопросе», «изучи тему», «собери факты», "research this", "verify this claim". Also use for durable research intent in varied wording — «создай ресерч в папке», «сохрани исследование», «обнови ресерч», "save/update this research" — and for explicit HTML delivery — «ресерч по теме X + html», «подготовь HTML-отчёт с источниками», «нужна HTML-версия», "research X and deliver it as HTML". Infer semantic intent rather than requiring an exact trigger phrase. Do not use for library/API documentation (find-docs), product search owned by another skill, personal advice, or questions answerable from stable supplied context. Mentioning HTML only as the research subject does not request HTML files.
coroboros/agent-skills/skills/code-ultrareview Skill
3★ repoEight-axis judgment code review for the current diff — Correctness, Simplification, Tests, Documentation, Style, Intent, Design/API, Performance (+ Coherence on metadata changes). Five-phase pipeline scope → deterministic tool battery (npx/uvx-preferred, zero-install for the JS + Python majority) → 8 parallel LLM axis reviewers → Haiku validators on sub-80 findings (verbatim rubric, ≥80 threshold) → synthesis with no-silent-drop + Conventional Comments JSONL. Every report closes with "What I did NOT check" (security → /security-review, runtime perf, flaky detection). Opt-in flags `--verify-build`, `--mutation-test`, `--reconcile`, `--apply-safe`. Public-skill posture — zero auto-install, graceful skip on missing native tools. Invoke before a commit or PR — "review my changes", "deep review", "did I miss anything", "check before I commit", "audit this PR", "drift / gaps / blind spots".
The same file is in 1 other repository
coroboros/agent-skills/skills/humanize-en Skill
3★ repoStrip AI writing tells from English prose — em-dash overuse, rule of three, negative parallelisms, AI vocabulary (delve, tapestry, crucial, pivotal, underscore, showcase), vague attributions, promotional tone, conjunctive padding (moreover, furthermore, indeed), hedging, signposting, chatbot artifacts. Preserves meaning, structure, code blocks, links, anchors, and frontmatter — rewrites only the flagged phrasing. Operates on inline text or a prose file path; optionally loads a `BRAND-VOICE.md` via `-f` for brand-specific rules. Use whenever English prose needs to sound less machine-generated — "humanize this", "remove AI tells", "clean up the AI slop", "sounds like ChatGPT", "polish the English" — on READMEs, docs, release notes, blog drafts, PR bodies, or commit messages.
coroboros/agent-skills/skills/markitdown Skill
3★ repoConvert any document to Markdown with Microsoft's `markitdown` CLI — PDF, Word, Excel, PowerPoint, HTML, CSV, JSON, XML, ZIP, EPub, images (OCR/EXIF), audio (transcription), and YouTube URLs. Use whenever the user wants to extract text from a binary document, transcribe audio, OCR an image, scrape a YouTube transcript, or pre-process a file for an LLM context window — even when they just say "convert this pdf", "what's in this docx", "transcribe this mp3", or "get the text out of this".
coroboros/agent-skills/skills/notion Skill
3★ repoNotion access from Claude Code via the official MCP connector (default path, ~95% of intents) or the `ntn` CLI (only for file uploads, Notion Workers, headless/CI scripts, raw API discovery, shell piping). Routes intent to the right transport, pre-flights the Notion-flavored Markdown spec and target data-source schema, and pins the empirical gotchas not surfaced by tool descriptions or `ntn --help`. Use whenever the user wants to read, fetch, search, create, update, query, or organize Notion content — pages, databases, data sources, views, comments, blocks, properties, schemas, wikis, docs — or upload a file to Notion, build a Notion Worker, or script Notion non-interactively. Triggers on Notion, Notion page, Notion database, Notion DB, Notion wiki, Notion doc, Notion comment, Notion view, Notion property, Notion schema, Notion file, Notion Worker, NOTION_API_TOKEN, ntn, ntn api.
coroboros/agent-skills/skills/write-clear-readme Skill
3★ repoAuthor, audit, or polish a project README — clarity, structure (Pattern A per-section collapse / Pattern B grouped / Pattern C per-entry), wording concision, anchor integrity. Reads the repo first, proposes diffs, applies on approval. Use when creating, restructuring, auditing, optimizing, or polishing a README for clarity, concision, or scannable structure — "write readme", "audit readme", "polish readme", "clarify readme", "optimize readme", "restructure readme", README clarity/wording — for long human-facing docs, skill libraries, npm SDK references, or CLI manuals.
redamancy231-create/claude-skills/write-claude-md Skill
3★ repo[流程:项目] Create or optimize project-level CLAUDE.md. Triggers when user asks to write/create/optimize/review a CLAUDE.md file, or when a new project lacks one. Uses five-step protocol: evidence collection, vulnerability testing, five-gap/five-abuse checks, empirical rules, and optional multi-backend validation. Not for: general documentation writing, README creation, project scaffolding, or conceptual discussions about CLAUDE.md without modification intent.
lythos-labs/lythoskill/packages/lythoskill-writer/skill Skill
3★ repoHuman-first documentation writer and reviewer. Reviews README, wiki, ADR, daily handoff, showcase, and reference docs for information density, structural rhythm, and anti-template patterns. Ensures human readers get clear prose, not AI-flavored filler.
lythos-labs/lythoskill/showcase/2026-05-20-head-skill-self-claim-verification/docx-skill Skill
3★ repoUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.
The same file is in 31 other repositories
lythos-labs/lythoskill/skills/lythoskill-writer Skill
3★ repoHuman-first documentation writer and reviewer. Reviews README, wiki, ADR, daily handoff, showcase, and reference docs for information density, structural rhythm, and anti-template patterns. Ensures human readers get clear prose, not AI-flavored filler.
TheColliery/CoalLedger/plugin/skills/doc-leak Skill
3★ repoDocs-health audience-safety scan — PROSE-level sensitive content in a doc meant to be public: internal URLs/hostnames/paths, personal data (names, emails, phone numbers in examples or logs), unpublished plans or roadmaps, private figures (pricing, customers), anything whose audience boundary the doc crosses. Catches LEAKED docs. Explicitly NOT a secret scanner: token-shaped secrets (API keys, passwords, private keys) are gitleaks' job — this canary hunts the sensitive PROSE that token scanners and gitignore both miss. Triggers on: "/doc-leak", "doc-leak", "is this safe to publish", "leak check", "anything private in this doc". Semantic, conservative by design: EVERY finding is SUSPECTED — public-vs-private is the human's judgment, never the tool's. Config-gated via the .coalledger.json docLeak key (default on; a private-only project turns it off).
TheColliery/CoalLedger/plugin/skills/doc-quality Skill
3★ repoDocs-health readability scan — two axes: QUALITY (bloat: filler, repetition, walls of text, buried leads; clarity: unexplained jargon, ambiguity, sentences that fight the reader) and language MECHANICS (typo, grammar, spelling, orthography — including script-level defects like decomposed characters that render right but break search, doubled spaces, wrong ellipsis/quote characters, spacing rules of the doc's language). Catches UNREADABLE or MALFORMED-LANGUAGE docs. Triggers on: "/doc-quality", "doc-quality", "tighten this doc", "proofread", "typos and grammar", "is this readable". Mechanical layer = deterministic mechanics (Unicode normalization, spacing, punctuation shape — ~free, report-only); semantic layer = bloat/clarity judgment + grammar in context (paid, consent-gated). Honors the project's own style/language rules where defined. Severity judged by context, never mechanical.
TheColliery/CoalLedger/plugin/skills/doc-rot Skill
3★ repoDocs-health staleness scan — content that time has made false: version strings older than the shipped version, dates and "last updated" stamps long past, stale badges, dead TODO/FIXME/"coming soon" markers, superseded instructions (steps for a surface that has since changed or gone), revalidate-by dates that have passed. Catches STALE docs — was true once, is not now. Triggers on: "/doc-rot", "doc-rot", "stale docs", "outdated docs", "is this doc still current". Mechanical layer = deterministic age-markers (versions, dates, TODO markers, badges — ~free, report-only); semantic layer = judging whether a flagged marker is actually rotten and spotting undated superseded content (paid, consent-gated). Severity judged by context, never mechanical; CONFIRMED and SUSPECTED reported separately.
TheColliery/CoalLedger/plugin/skills/doc-standard Skill
3★ repoDocs-health completeness scan — a doc measured against its KIND's standard: required sections present, public surface documented (every command/config key/exported API the code ships appears in the doc), the shape the genre expects (a README's install path, a security policy's reporting channel, a formal letter's parts). Catches INCOMPLETE docs. The standard is the project's OWN declared one first (a style guide, template, or pattern doc in the repo), else the kind's widely-accepted standard verified REAL-TIME against MULTIPLE authoritative sources. Triggers on: "/doc-standard", "doc-standard", "is this doc complete", "missing sections", "audit doc completeness". Mechanical layer (sections/hierarchy present via the AST — language-neutral) + semantic layer (completeness judgment, consent-gated). Offline degrades safe to "⚠️ unverified". Severity judged by context, never mechanical.
TheColliery/CoalLedger/plugin/skills/doc-structure Skill
3★ repoDocs-health structure scan — broken internal links/anchors (GitHub-slug resolution, Thai/CJK safe), dead relative file links, heading hierarchy (skipped levels, multiple H1), duplicate sibling headings (same parent, same text), GFM table shape (silently-dropped cells), orphan/undefined reference definitions, bare URLs in prose, images missing alt text (WCAG-aware, SUSPECTED-only — decorative-vs-content intent is a human call). Triggers on: "/doc-structure", "doc-structure", "broken links", "check docs structure", "doc health". Mechanical + deterministic: detection runs through the shipped CommonMark+GFM AST engine (never regex over raw markdown), so things that render fine are not flagged. Reports; fixes on request via choice-gated menu. Severity is judged by context, never mechanical.
TheColliery/CoalLedger/skills/doc-leak Skill
3★ repoDocs-health audience-safety scan — PROSE-level sensitive content in a doc meant to be public: internal URLs/hostnames/paths, personal data (names, emails, phone numbers in examples or logs), unpublished plans or roadmaps, private figures (pricing, customers), anything whose audience boundary the doc crosses. Catches LEAKED docs. Explicitly NOT a secret scanner: token-shaped secrets (API keys, passwords, private keys) are gitleaks' job — this canary hunts the sensitive PROSE that token scanners and gitignore both miss. Triggers on: "/doc-leak", "doc-leak", "is this safe to publish", "leak check", "anything private in this doc". Semantic, conservative by design: EVERY finding is SUSPECTED — public-vs-private is the human's judgment, never the tool's. Config-gated via the .coalledger.json docLeak key (default on; a private-only project turns it off).
TheColliery/CoalLedger/skills/doc-quality Skill
3★ repoDocs-health readability scan — two axes: QUALITY (bloat: filler, repetition, walls of text, buried leads; clarity: unexplained jargon, ambiguity, sentences that fight the reader) and language MECHANICS (typo, grammar, spelling, orthography — including script-level defects like decomposed characters that render right but break search, doubled spaces, wrong ellipsis/quote characters, spacing rules of the doc's language). Catches UNREADABLE or MALFORMED-LANGUAGE docs. Triggers on: "/doc-quality", "doc-quality", "tighten this doc", "proofread", "typos and grammar", "is this readable". Mechanical layer = deterministic mechanics (Unicode normalization, spacing, punctuation shape — ~free, report-only); semantic layer = bloat/clarity judgment + grammar in context (paid, consent-gated). Honors the project's own style/language rules where defined. Severity judged by context, never mechanical.
TheColliery/CoalLedger/skills/doc-rot Skill
3★ repoDocs-health staleness scan — content that time has made false: version strings older than the shipped version, dates and "last updated" stamps long past, stale badges, dead TODO/FIXME/"coming soon" markers, superseded instructions (steps for a surface that has since changed or gone), revalidate-by dates that have passed. Catches STALE docs — was true once, is not now. Triggers on: "/doc-rot", "doc-rot", "stale docs", "outdated docs", "is this doc still current". Mechanical layer = deterministic age-markers (versions, dates, TODO markers, badges — ~free, report-only); semantic layer = judging whether a flagged marker is actually rotten and spotting undated superseded content (paid, consent-gated). Severity judged by context, never mechanical; CONFIRMED and SUSPECTED reported separately.
TheColliery/CoalLedger/skills/doc-standard Skill
3★ repoDocs-health completeness scan — a doc measured against its KIND's standard: required sections present, public surface documented (every command/config key/exported API the code ships appears in the doc), the shape the genre expects (a README's install path, a security policy's reporting channel, a formal letter's parts). Catches INCOMPLETE docs. The standard is the project's OWN declared one first (a style guide, template, or pattern doc in the repo), else the kind's widely-accepted standard verified REAL-TIME against MULTIPLE authoritative sources. Triggers on: "/doc-standard", "doc-standard", "is this doc complete", "missing sections", "audit doc completeness". Mechanical layer (sections/hierarchy present via the AST — language-neutral) + semantic layer (completeness judgment, consent-gated). Offline degrades safe to "⚠️ unverified". Severity judged by context, never mechanical.
TheColliery/CoalLedger/skills/doc-structure Skill
3★ repoDocs-health structure scan — broken internal links/anchors (GitHub-slug resolution, Thai/CJK safe), dead relative file links, heading hierarchy (skipped levels, multiple H1), duplicate sibling headings (same parent, same text), GFM table shape (silently-dropped cells), orphan/undefined reference definitions, bare URLs in prose, images missing alt text (WCAG-aware, SUSPECTED-only — decorative-vs-content intent is a human call). Triggers on: "/doc-structure", "doc-structure", "broken links", "check docs structure", "doc health". Mechanical + deterministic: detection runs through the shipped CommonMark+GFM AST engine (never regex over raw markdown), so things that render fine are not flagged. Reports; fixes on request via choice-gated menu. Severity is judged by context, never mechanical.