content-audit

Audit handbook content for formatting, punctuation, and heading consistency.

3|1|Updated Apr 18, 2025
One-click install
npx skills add https://github.com/imsaif/aiex --skill content-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: content-audit
Source: https://github.com/imsaif/aiex/tree/main/.claude/skills/content-audit
Command: npx skills add https://github.com/imsaif/aiex --skill content-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill acts as a content guardian for handbook material, detecting formatting issues, inappropriate punctuation, generic AI phrases, and inconsistent heading styles that can make content feel like "AI slop."

Core Features & Use Cases

  • Style & Punctuation Checks: Remove overuse of italics, bold, em-dashes, and repeated punctuation.
  • AI Slop Guard: Flag generic phrases such as "innovative", "transformative", and "harnesses the power of AI".
  • Heading Consistency: Enforce consistent heading sizes and styles across the document.
  • Flowery Language Reduction: Flag hedging language and marketing-style phrasing.
  • Use Case: Clean up handbook content to read clearly and directly.

Quick Start

Run: /content-audit check handbook-content.ts Suggestions: /content-audit suggest handbook-content.ts Fix All: /content-audit fix handbook-content.ts

Frequently Asked Questions about content-audit

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

FAQPage Schema
How do I check handbook content for formatting and style inconsistencies?

Content audit checks detect formatting issues like overused italics, bold, em-dashes, and inconsistent heading styles across handbook pages. Run the check command to identify problems with line numbers and severity levels, then review suggestions or apply automated fixes to enforce consistent style.

What generic phrases should I remove from documentation to avoid sounding like AI-generated content?

The audit flags overused marketing and AI phrases such as 'innovative,' 'transformative,' and 'harnesses the power of AI,' along with hedging language that dilutes clarity. Removing these makes handbook content read more directly and authentically.

Can I automatically fix formatting and punctuation issues in my handbook?

Yes. The fix command applies concrete corrections to formatting violations, punctuation overuse, and inconsistent heading styles automatically. You can review suggested changes before committing them to your documentation.

When should I run content audits on my internal documentation?

Run audits before publishing handbook updates, during live quality monitoring cycles, or when refreshing existing knowledge bases. The audit supports pre-publish checks and content maintenance workflows to catch style drift early.

Does content audit work with any documentation format or just specific file types?

The audit applies to handbook content, internal documentation, and knowledge bases in supported formats. It enforces consistent checks across your documentation architecture regardless of specific file extension or platform.

What's the difference between checking and suggesting fixes for content issues?

Check mode identifies all formatting, punctuation, and phrasing issues with line numbers and severity. Suggest mode recommends specific rewrites and corrections. Fix mode applies those corrections automatically to clean up content in one pass.