lektorat-applylisted

Reviews existing Markdown prose against six editorial dimensions (readability, comprehensibility, grammar, style, audience-fit, idiomatic naturalness) defined in `spec/project/lektorat/`. Three operations — `audit` (read-only report), `patch` (one finding, one diff, one approval), `revise` (full-artefact rewrite with diff review); dispatches `lektorat-scanner` for the detection phase. Invoke when the user asks to "lektoriere README.md", "audit docs for audience-fit", "revise this page with Lektorat", "prüfe auf Lesbarkeit", or equivalent EN/DE requests. Writes outputs to `.audits/lektorat/<YYYY-MM-DD-HHMM>/`. Don't use to author new prose (use `audience-doc-author`), curate Vale rules (use `prose-vale-curator`), lektor `spec/` files (out of scope), or edit code, configs, or LLM-instruction artefacts (SKILL.md, agents/*.md). Supports resume on re-invocation per `spec/claude/resumable-work/`.
nolte/claude-shared · ★ 0 · Data & Documents · score 76

Install: claude install-skill nolte/claude-shared

# Lektorat Apply Operationalises `spec/project/lektorat/` for the `nolte-shared` plugin: the editorial layer that audits, patches, or revises already-existing human-readable Markdown prose against six named quality dimensions, with a per-language rule set and explicit operator dialogue at every mutating step. This skill binds the spec's contract to an on-disk procedure. It does not redefine the rules; when this skill and the spec disagree, the spec wins and this skill needs the update. ## German trigger phrases This skill also triggers on equivalent German-language requests, including: - "lektoriere die README" - "prüfe diese Doku auf Lesbarkeit" - "audit die Seite auf Audience-Fit" - "revise diesen Eintrag mit Lektorat" - "Rechtschreibung in den deutschen Docs prüfen" ## User-language policy Detect the user's language from their message and respond in it. The machine-readable JSON output uses English keys (per `spec/project/lektorat/` §Outputs); the human-readable Markdown summary uses English section headings so downstream tooling can parse it reliably; prose around the report is localised. The artefact being reviewed is **not** translated by this skill. Each file is reviewed against the rules of its own language (DE-rules on DE-text, EN-rules on EN-text); cross-language translation belongs to the `spec` skill or the `spec/project/docs-multilingual-authoring/` spec. ## Why this is a skill, not an agent - **Mid-flow user approval is load-bearing**: `patch` requires