writing-prose

Draft and revise reader-facing prose using a Vale lint gate and editorial checks.

7|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/apoapostolov/humanizer --skill writing-prose-apoapostolov
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-prose
Source: https://github.com/apoapostolov/humanizer/tree/main/skills/writing-prose
Command: npx skills add https://github.com/apoapostolov/humanizer --skill writing-prose-apoapostolov

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires vale, and includes scripts (resource) and references (resource) components.

What problem does it solve? Drafting articles, docs, and long-form prose often produces generic, formulaic, or mechanically flawed text that linters alone cannot catch. This Skill pairs a deterministic Vale review gate with mandatory editorial checks so prose is both mechanically clean and genuinely specific, coherent, and reader-appropriate. ## Core Features & Use Cases - Vale house gate: A bundled Vale configuration with custom rules (no em dashes, plain word choice, AI-slop detection, weasel words) plus whitelisted Microsoft and built-in Vale styles, run via scripts/vale-lint.sh. - Editorial rule set: Fourteen mandatory quality rules covering specificity, fact discipline, register fit, regularity, and structure that a linter cannot judge. - Required checks and references: Ten revision tripwires plus long-form diagnostics, a formula watchlist, correction examples, and book-writing cost estimation references. - Use Case: You draft a blog post, run the Vale gate to clear mechanical errors, then apply the editorial pass to cut generic claims, verify fragile facts, and break repetitive sentence patterns before publishing. ## Quick Start Ask the agent to draft or revise your article using the writing-prose skill, then run the Vale gate on the draft file and apply the required editorial checks.

Frequently Asked Questions about writing-prose

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I lint Markdown prose with Vale?▼

Run scripts/vale-lint.sh with your file path, or invoke Vale directly with vale --config vale/vale.ini --minAlertLevel=warning <file>. Vale exits nonzero only on error-level violations like em dashes; warnings display but do not block.

What writing rules does the Vale house config enforce?▼

The HermesHouse style bans em dashes at error level, flags plain-word substitutions and AI-slop terms like delve or seamless at warning level, and suggests removing vague intensifiers. It also whitelists Microsoft Passive, SentenceLength, HeadingPunctuation, and Acronyms rules.

When should I use writing-prose instead of simple-english or humanizer?▼

Use writing-prose for reader-facing prose like articles, docs, and criticism. Use simple-english for strict technical procedures and error messages, humanizer for preserving a specific writer's voice, and ai-writing-detector for mechanical AI-signal scoring.

Why does Vale flag words that are valid domain terms?▼

The Spelling rule flags unknown words until you add them to the vocabulary accept-list at vale/styles/config/vocabularies/Hermes/accept.txt. Common stack terms are pre-loaded, and you can rename the vocab to match your own project.

Can I override house style rules for a specific project?▼

Yes. Copy vale/vale.ini to your project root, adjust settings, and run vale --config .vale.ini. To disable one rule, set something like HermesHouse.EmDash = NO in the project section.

Why do lowercase Vale style keys not work in the config?▼

Built-in Vale style rules require capitalized keys such as Vale.Spelling = YES and Vale listed in BasedOnStyles. Lowercase keys are silently ignored, which is a common configuration pitfall documented in the skill.