Skip to content
Back to skills

Write Good English Prose Linting Technical Content

ASecurity

This skill uses write-good to flag vague, wordy, or hard-to-read English prose in documentation and content drafts. It is useful when a team wants lightweight style feedback inside editors, scripts, or CI checks.

  • 36 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added June 8, 2026
ai-agentsgonodegitsecuritydocumentation

Security analysis

A92/100
  • mediumInstalls packages at runtime which could introduce malicious dependencies

Pro shows the line behind each finding and how to fix it

Scanned June 8, 2026

npx -y skills add agentskillexchange/skills --skill write-good-english-prose-linting-technical-content --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Write Good English Prose Linting Technical Content?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Write Good English Prose Linting Technical Content
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/agentskillexchange-write-good-english-prose-linting-technical-content/badge)](https://www.skillsdirectory.com/skills/agentskillexchange-write-good-english-prose-linting-technical-content)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: "write-good English Prose Linting for Technical Content"
slug: "write-good-english-prose-linting-technical-content"
description: "This skill uses write-good to flag vague, wordy, or hard-to-read English prose in documentation and content drafts. It is useful when a team wants lightweight style feedback inside editors, scripts, or CI checks."
github_stars: 5065
verification: "security_reviewed"
source: "https://github.com/btford/write-good"
category: "Content Writing & SEO"
framework: "Multi-Framework"
tool_ecosystem:
  github_repo: "btford/write-good"
  github_stars: 5065
  npm_package: "write-good"
  npm_weekly_downloads: 49520
---

# write-good English Prose Linting for Technical Content

This skill uses write-good to flag vague, wordy, or hard-to-read English prose in documentation and content drafts. It is useful when a team wants lightweight style feedback inside editors, scripts, or CI checks.

## Installation

Use the upstream install or setup path that matches your environment:
- npm install write-good
- npm install -g write-good
- If you have npm version 5.2.0 or later installed, you can use npx to run write-good without installing it:
- npx write-good *.md

Requirements and caveats from upstream:
- var writeGood = require('write-good');
- var schreibGut = require('schreib-gut');
- write-good takes a [glob](https://github.com/isaacs/node-glob) and prints suggestions to stdout:

Basic usage or getting-started notes:
- Like this, you can check non-English documents, for example with the linter extension for German, [schreib-gut](https://github.com/TimKam/schreib-gut):
- For example, normally only would be picked up as a bad word to use, but you might want to exempt read-only from that:
- You can run just specific checks like this:

- Source: https://github.com/btford/write-good
- Extracted from upstream docs: https://raw.githubusercontent.com/btford/write-good/HEAD/README.md

## Source

- [Agent Skill Exchange](https://agentskillexchange.com/skills/write-good-english-prose-linting-technical-content/)

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.