acc-documentation-qa-knowledge

Documentation QA knowledge base. Provides quality checklists, audit criteria, and metrics for documentation review.

16 stars

Best use case

acc-documentation-qa-knowledge is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Documentation QA knowledge base. Provides quality checklists, audit criteria, and metrics for documentation review.

Teams using acc-documentation-qa-knowledge should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/acc-documentation-qa-knowledge/SKILL.md --create-dirs "https://raw.githubusercontent.com/diegosouzapw/awesome-omni-skill/main/skills/documentation/acc-documentation-qa-knowledge/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/acc-documentation-qa-knowledge/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How acc-documentation-qa-knowledge Compares

Feature / Agentacc-documentation-qa-knowledgeStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Documentation QA knowledge base. Provides quality checklists, audit criteria, and metrics for documentation review.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Documentation QA Knowledge Base

Quick reference for documentation quality assessment and audit criteria.

## Quality Dimensions

### Core Quality Metrics

| Dimension | Description | Weight |
|-----------|-------------|--------|
| **Completeness** | All APIs/features documented | 25% |
| **Accuracy** | Code matches documentation | 25% |
| **Clarity** | Understandable, no jargon | 20% |
| **Consistency** | Terms, style, format uniform | 15% |
| **Navigation** | Easy to find information | 10% |
| **Freshness** | Up-to-date with latest version | 5% |

### Quality Scoring

```
Score = (Completeness × 0.25) + (Accuracy × 0.25) + (Clarity × 0.20)
      + (Consistency × 0.15) + (Navigation × 0.10) + (Freshness × 0.05)

Rating:
90-100: Excellent
75-89:  Good
60-74:  Adequate
40-59:  Poor
0-39:   Critical
```

## Audit Checklists

### README Checklist

| Item | Required | Score |
|------|----------|-------|
| Project name and description | ✅ | /10 |
| Installation instructions | ✅ | /15 |
| Basic usage example | ✅ | /15 |
| Requirements/dependencies | ✅ | /10 |
| License | ✅ | /5 |
| Badges (build, coverage, version) | ⚪ | /5 |
| Contributing link | ⚪ | /5 |
| Documentation links | ⚪ | /10 |
| Changelog link | ⚪ | /5 |
| Examples work (copy-paste test) | ✅ | /20 |

**Total: /100**

### API Documentation Checklist

| Item | Required | Score |
|------|----------|-------|
| All public classes documented | ✅ | /15 |
| All public methods documented | ✅ | /15 |
| Parameters with types and descriptions | ✅ | /15 |
| Return types documented | ✅ | /10 |
| Exceptions documented | ✅ | /10 |
| Usage examples per endpoint | ✅ | /15 |
| Request/response examples | ⚪ | /10 |
| Error responses documented | ⚪ | /10 |

**Total: /100**

### Architecture Documentation Checklist

| Item | Required | Score |
|------|----------|-------|
| System overview | ✅ | /15 |
| Component descriptions | ✅ | /15 |
| Data flow diagrams | ✅ | /15 |
| Technology stack | ✅ | /10 |
| Decision records (ADRs) | ⚪ | /15 |
| Diagrams render correctly | ✅ | /10 |
| Consistent terminology | ✅ | /10 |
| Cross-references work | ⚪ | /10 |

**Total: /100**

## Detection Patterns

### Completeness Detection

```bash
# Find undocumented public classes
Grep: "^class |^final class |^abstract class " --glob "src/**/*.php"
# Compare with: Grep: "## " --glob "docs/api/**/*.md"

# Find undocumented public methods
Grep: "public function " --glob "src/**/*.php" | wc -l
# Compare with documented count

# Check README sections
Grep: "## Installation|## Usage|## Features" --glob "README.md"
```

### Accuracy Detection

```bash
# Find version mismatches
Grep: "version.*[0-9]+\.[0-9]+" --glob "README.md"
# Compare with: Grep: '"version"' --glob "composer.json"

# Find non-existent paths in docs
Grep: "src/[A-Za-z/]+" --glob "docs/**/*.md"
# Verify each path exists

# Find outdated code examples
# Extract code blocks and verify they match current API
```

### Clarity Detection

```bash
# Find undefined acronyms
Grep: "\b[A-Z]{2,}\b" --glob "docs/**/*.md"
# Check for glossary/definition nearby

# Find jargon without explanation
# Manual review of: DDD, CQRS, VO, DTO first usage

# Find walls of text (paragraphs > 5 lines)
# Manual review recommended
```

### Navigation Detection

```bash
# Find broken internal links
Grep: "\]\((?!http)[^\)]+\)" --glob "**/*.md"
# Verify each relative path exists

# Find missing TOC in long docs (> 100 lines)
wc -l docs/**/*.md | awk '$1 > 100 {print $2}'
# Check for: Grep: "## Table of Contents|## Contents" in each

# Find orphan pages (not linked from anywhere)
# Cross-reference all .md files
```

### Diagram Quality Detection

```bash
# Find diagrams with too many elements
Grep: "^\s*[A-Za-z].*\[|^\s*[A-Za-z].*\(" --glob "**/*.md" -A 50
# Count nodes in each mermaid block

# Find diagrams without labels
Grep: "A-->B|1-->2" --glob "**/*.md"
# Should have descriptive IDs

# Find non-rendering mermaid
# Test each ```mermaid block
```

## Issue Severity Levels

### Critical (Must Fix)

```markdown
❌ Missing installation instructions
❌ Broken copy-paste examples
❌ Wrong/outdated code syntax
❌ Missing license
❌ Dead links to key resources
❌ Security-sensitive info in examples
```

### Warning (Should Fix)

```markdown
⚠️ Missing API documentation
⚠️ No usage examples
⚠️ Outdated screenshots
⚠️ Inconsistent terminology
⚠️ Missing error handling docs
⚠️ Diagrams don't match code
```

### Info (Nice to Have)

```markdown
ℹ️ No badges
ℹ️ Missing contributing guide
ℹ️ No FAQ section
ℹ️ Basic diagrams could be improved
ℹ️ Could add more examples
```

## Audit Report Template

```markdown
# Documentation Audit Report

**Project:** {name}
**Date:** {date}
**Auditor:** Claude Code

## Summary

| Metric | Score | Status |
|--------|-------|--------|
| Overall | X/100 | ⚠️ |
| Completeness | X/100 | ✅ |
| Accuracy | X/100 | ❌ |
| Clarity | X/100 | ✅ |
| Consistency | X/100 | ⚠️ |
| Navigation | X/100 | ✅ |

## Critical Issues

### 1. {Issue Title}
- **Location:** {file:line}
- **Problem:** {description}
- **Impact:** {who is affected}
- **Fix:** {recommendation}

## Warnings

### 1. {Issue Title}
- **Location:** {file}
- **Problem:** {description}
- **Recommendation:** {fix}

## Recommendations

1. {Priority action 1}
2. {Priority action 2}
3. {Priority action 3}

## Detailed Findings

### README.md
- [ ] {item}: {status}

### API Documentation
- [ ] {item}: {status}

### Architecture Documentation
- [ ] {item}: {status}

## Next Steps

1. Fix critical issues immediately
2. Address warnings in next sprint
3. Consider recommendations for roadmap
```

## Quality Improvement Guide

### Quick Wins

| Action | Impact | Effort |
|--------|--------|--------|
| Fix broken links | High | Low |
| Add missing badges | Medium | Low |
| Add code examples | High | Medium |
| Create README template | High | Medium |
| Add link checker CI | Medium | Low |

### Long-term Improvements

| Action | Impact | Effort |
|--------|--------|--------|
| Generate API docs from code | High | High |
| Implement doc-as-code | High | High |
| Create style guide | Medium | Medium |
| Add example testing | High | Medium |
| Diagram automation | Medium | High |

## Automation Opportunities

### CI/CD Integration

```yaml
# Example doc validation workflow
documentation:
  checks:
    - markdown-lint
    - link-check
    - spelling
    - code-example-test
    - mermaid-validate
```

### Tools

| Tool | Purpose |
|------|---------|
| markdownlint | Markdown style |
| markdown-link-check | Broken links |
| alex | Inclusive language |
| mermaid-cli | Diagram validation |
| doctoc | TOC generation |

## References

For detailed information, load these reference files:

- `references/audit-procedures.md` — Step-by-step audit process
- `references/scoring-rubrics.md` — Detailed scoring criteria
- `references/common-issues.md` — Frequent documentation problems
- `references/automation.md` — CI/CD integration patterns

Related Skills

documentation-templates

16
from diegosouzapw/awesome-omni-skill

Documentation templates and structure guidelines. README, API docs, code comments, and AI-friendly documentation.

documentation-structure-validator

16
from diegosouzapw/awesome-omni-skill

Validate documentation structure, check for missing sections, verify markdown syntax, ensure consistency with templates. Use when user mentions docs validation, structure check, README review, documentation quality, or wants to verify documentation completeness.

documentation-standards

16
from diegosouzapw/awesome-omni-skill

Clear technical documentation with JSDoc, READMEs, Mermaid diagrams, ISMS policy references, and comprehensive code examples

documentation-specialist

16
from diegosouzapw/awesome-omni-skill

文档专家。专注于技术文档编写、API 文档生成、README 优化和文档维护。提供清晰的文档结构、规范的格式和用户友好的内容。

documentation-research

16
from diegosouzapw/awesome-omni-skill

Enforces documentation research before implementation. Auto-loads when implementing features to ensure current best practices are followed. Researches official docs first.

documentation

16
from diegosouzapw/awesome-omni-skill

Technical writing, API docs, and documentation best practices

Documentation Hygiene

16
from diegosouzapw/awesome-omni-skill

This skill should be used when the user asks to perform "documentation hygiene", "update docs for change", "mark historical docs", "add deprecation headers", "documentation migration", or when making significant changes that affect multiple documentation files (like license migrations, tier changes, or API changes).

documentation-guidelines

16
from diegosouzapw/awesome-omni-skill

Write or update backend feature documentation that follows a repo's DOCUMENTATION_GUIDELINES.md (or equivalent) across any project. Use when asked to create/update module docs, API contracts, or backend documentation that must include architecture, endpoints, payloads, Mermaid diagrams, and seeding instructions.

documentation-generation-doc-generate

16
from diegosouzapw/awesome-omni-skill

You are a documentation expert specializing in creating comprehensive, maintainable documentation from code. Generate API docs, architecture diagrams, user guides, and technical references using AI...

create-oo-component-documentation

16
from diegosouzapw/awesome-omni-skill

Create comprehensive, standardized documentation for object-oriented components following industry best practices and architectural documentation standards.

code-documentation

16
from diegosouzapw/awesome-omni-skill

Writing effective code documentation - API docs, README files, inline comments, and technical guides. Use for documenting codebases, APIs, or writing developer guides.

code-documentation-doc-generate

16
from diegosouzapw/awesome-omni-skill

You are a documentation expert specializing in creating comprehensive, maintainable documentation from code. Generate API docs, architecture diagrams, user guides, and technical references using AI...