content-linter

Lint markdown content for spelling, en-GB compliance, and writing quality.

59|10|Updated Jul 17, 2021
One-click install
npx skills add https://github.com/spences10/scottspence.com --skill content-linter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: content-linter
Source: https://github.com/spences10/scottspence.com/tree/main/.claude/skills/content-linter
Command: npx skills add https://github.com/spences10/scottspence.com --skill content-linter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Manual content review for spelling, grammar, and style is time-consuming and prone to human error. This Skill automates these checks, ensuring high-quality, consistent content without the manual grind.

Core Features & Use Cases

  • Comprehensive Linting: Automatically checks for spelling errors (en-GB), vague language, and ensures code blocks have language identifiers.
  • Language Consistency: Enforces British English spellings (e.g., colour, organisation) across all content.
  • Writing Quality: Flags weak verbs and vague phrases like "very" or "really" to improve clarity and impact.
  • Use Case: Before publishing a blog post, use this Skill to quickly identify and correct all spelling mistakes, ensure British English compliance, and flag areas for improved writing quality, saving you hours of proofreading.

Quick Start

Use the content-linter skill to check the attached markdown file 'my-new-post.md' for spelling errors and writing quality.

Frequently Asked Questions about content-linter

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

FAQPage Schema
How do I check markdown files for spelling errors and British English compliance?

Markdown linting automatically detects spelling mistakes and enforces en-GB compliance across your content. This Skill uses cspell and targeted checks to flag non-standard British English spellings like 'color' instead of 'colour', catching errors before publication without manual review.

Can I automate content quality checks in my publishing workflow?

Yes. Integrate linting into your CI pipeline or pre-publication process to automatically validate spelling, grammar, and writing quality. It runs batch audits on markdown assets across posts, newsletters, and documentation, reducing manual proofreading hours.

What writing quality issues does markdown linting catch?

Linting detects vague language like 'very' and 'really', flags weak verbs, validates that code blocks include language identifiers, and identifies phrases that reduce clarity. These checks improve content impact and consistency across your documentation.

Does this work with CI validation and batch audits?

Yes. The Skill uses npm scripts and file globs to support publication-grade content validation in CI environments and batch processing. Run checks automatically on multiple files or integrate into your existing deployment pipeline.

What's the difference between general grammar checking and British English linting?

British English linting enforces specific regional spelling and terminology standards—'organisation' vs 'organization', 'colour' vs 'color'. This Skill ensures consistency across your entire content set, critical for brands targeting UK audiences or maintaining editorial standards.