Skip to content
cccskills
FreePublished on GitHub

nw-quality-validation

Type-specific validation checklists, six quality characteristics, and quality gate thresholds for documentation assessment

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (1)

  • SKILL.md2.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Quality Validation

Six Quality Characteristics

  • Accuracy: Factually correct, technically sound, current | Validation: expert review, automated testing
  • Completeness: All necessary info present for doc type | Validation: checklist, gap analysis
  • Clarity: Easy to understand, logical flow, appropriate level | Validation: Flesch 70-80
  • Consistency: Uniform terminology, formatting, structure | Validation: style guide compliance
  • Correctness: Proper grammar, spelling, punctuation | Validation: automated check, zero errors
  • Usability: User achieves goal efficiently | Validation: task success, DIVIO type purpose served

Quality Gate Thresholds

MetricThreshold
Readability (Flesch)70-80
Spelling errors0
Broken links0
Style compliance95%+
Type purity80%+ single type

Type-Specific Validation Checklists

Tutorial Checklist

  • Completable without external references | [ ] Steps numbered and sequential
  • Each step has verifiable outcome | [ ] No assumed prior knowledge | [ ] Builds confidence

How-to Checklist

  • Clear goal stated upfront | [ ] Assumes fundamentals known
  • Single task focus | [ ] Ends with completion indicator | [ ] No basics teaching

Reference Checklist

  • All parameters documented | [ ] Return values specified
  • Error conditions listed | [ ] Examples per entry | [ ] No narrative

Explanation Checklist

  • Addresses "why" not "what" | [ ] Provides context and reasoning
  • Discusses alternatives | [ ] No task steps | [ ] Builds conceptual model

Verdict Criteria

  • approved: Passes all type-specific validation, no collapse violations, meets quality gates
  • needs-revision: Minor issues fixable in place (clarity, missing examples, small gaps)
  • restructure-required: Collapse detected requiring split, or fundamental type mismatch

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Review dimensions for validating agent quality - template compliance, safety, testing, and priority validation

The English summary is being prepared. Showing the original description.

nWave-ai/nWave622Updated Sep 16, 2026

Review dimensions for validating agent quality - template compliance, safety, testing, and priority validation

The English summary is being prepared. Showing the original description.

nWave-ai/nWave622Updated Sep 16, 2026

Review dimensions for acceptance test quality - happy path bias, GWT compliance, business language purity, coverage completeness, walking skeleton user-centricity, priority validation, observable behavior assertions, traceability coverage, and walking skeleton boundary proof

The English summary is being prepared. Showing the original description.

nWave-ai/nWave622Updated Sep 16, 2026

Detailed 5-phase workflow for creating agents - from requirements analysis through validation and iterative refinement

The English summary is being prepared. Showing the original description.

nWave-ai/nWave622Updated Sep 16, 2026

5-layer testing approach for agent validation including adversarial testing, security validation, and prompt injection resistance

The English summary is being prepared. Showing the original description.

nWave-ai/nWave622Updated Sep 16, 2026

Architectural style selection decision matrices, trade-off analysis, structural enforcement rules, and combination patterns. Load when choosing or evaluating architecture styles.

The English summary is being prepared. Showing the original description.

nWave-ai/nWave622Updated Sep 16, 2026

See all skills by nWave-ai

Report a problem with this skill