docs-applying-content-quality

Enforce accessible markdown content quality standards across repository documentation.

3|1|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/wahidyankf/ose-primer --skill docs-applying-content-quality
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-applying-content-quality
Source: https://github.com/wahidyankf/ose-primer/tree/main/.claude/skills/docs-applying-content-quality
Command: npx skills add https://github.com/wahidyankf/ose-primer --skill docs-applying-content-quality

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates inconsistent markdown quality, accessibility gaps, and unprofessional formatting across all repository content, ensuring all documentation, planning documents, and root files meet universal readability and compliance standards.

Core Features & Use Cases

  • Writing Standard Enforcement: Applies active voice, professional tone, and clarity rules to all markdown content for direct, easy-to-understand communication.
  • Accessibility Compliance: Guarantees WCAG AA adherence including descriptive alt text for all images, proper heading hierarchy, and screen reader support.
  • Formatting Consistency: Standardizes code block syntax highlighting, list formatting, paragraph length, and eliminates time-based estimates for professional, user-focused content.
  • Use Case: Use this Skill when creating repository READMEs, documentation site content, planning documents, or any markdown file to ensure all output aligns with the repository's content quality rules.

Quick Start

Use the docs-applying-content-quality skill to review and update your markdown document to meet all repository content quality and accessibility standards.

Frequently Asked Questions about docs-applying-content-quality

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

FAQPage Schema
How do I enforce WCAG AA accessibility standards in markdown documentation?

To enforce WCAG AA accessibility in markdown, apply rules for descriptive image alt text, maintain proper heading hierarchy, and ensure screen reader support across all repository documentation and root files.

What is the best way to standardize markdown formatting across a repository?

Standardize markdown formatting by enforcing consistent code block syntax highlighting, list formatting, paragraph length, and active voice usage to eliminate unprofessional formatting across all planning documents and READMEs.

How do I check markdown files for proper heading hierarchy and active voice?

Check markdown files by reviewing content against quality rules that require proper heading hierarchy without skipping levels, and direct active voice usage to ensure clear, professional communication.

Does this markdown content quality check apply to planning documents and root files?

Yes, this markdown content quality check applies to all repository content including planning documents, root files, documentation sites, and README files to ensure universal readability and compliance.

Why should I remove time-based estimates from technical documentation?

Remove time-based estimates from technical documentation to maintain professional, user-focused content standards that prioritize consistent formatting and clarity over speculative timelines in markdown files.