documentation-testing-documentation

Sub-skill of documentation: Testing Documentation.

5 stars

Best use case

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

Sub-skill of documentation: Testing Documentation.

Teams using documentation-testing-documentation 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/testing-documentation/SKILL.md --create-dirs "https://raw.githubusercontent.com/vamseeachanta/workspace-hub/main/.agents/skills/_archive/development/documentation/documentation/testing-documentation/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/testing-documentation/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How documentation-testing-documentation Compares

Feature / Agent	documentation-testing-documentation	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

Sub-skill of documentation: Testing Documentation.

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

# Testing Documentation

## Testing Documentation


Validate documentation quality:

```bash
#!/bin/bash
# test_docs.sh

test_markdown_lint() {
    markdownlint docs/**/*.md && echo "PASS: Markdown lint" || echo "FAIL: Markdown lint"
}

test_build() {
    mkdocs build --strict && echo "PASS: Build successful" || echo "FAIL: Build failed"
}

test_links() {
    find docs -name '*.md' -exec markdown-link-check -q {} \; && \
        echo "PASS: Links valid" || echo "FAIL: Broken links found"
}

test_spelling() {
    cspell docs/**/*.md && echo "PASS: Spelling" || echo "FAIL: Spelling errors"
}

# Run all tests
test_markdown_lint
test_build
test_links
test_spelling
```

Related Skills

documentation-contract-plan-hardening

from vamseeachanta/workspace-hub

Harden a documentation/contract plan before adversarial review by mapping every issue-scope requirement to independent acceptance criteria and tests, especially for routing/indexing contracts.

webapp-testing

from vamseeachanta/workspace-hub

Web application testing toolkit using Playwright with Python. Use for verifying frontend functionality, debugging UI behavior, capturing browser screenshots, viewing browser logs, and automating web interactions.

testing-tdd-london

from vamseeachanta/workspace-hub

TDD London School (mockist) specialist for mock-driven, outside-in development. Use for behavior verification testing, contract-driven development, testing object collaborations, or when focusing on HOW objects interact rather than WHAT they contain.

testing-production

from vamseeachanta/workspace-hub

Production validation specialist ensuring applications are fully implemented and deployment-ready. Use to verify no mock/stub/fake implementations remain, validate against real databases and APIs, perform end-to-end testing with actual systems, and confirm production readiness.