nw-collapse-detection

Detect documentation collapse and provide remediation guidance for mixed content.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/StudentCristian/nWave-github --skill nw-collapse-detection
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nw-collapse-detection
Source: https://github.com/StudentCristian/nWave-github/tree/main/.github/skills/nw-collapse-detection
Command: npx skills add https://github.com/StudentCristian/nWave-github --skill nw-collapse-detection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation collapse occurs when content from multiple documentation quadrants (tutorials, how-tos, references, and explanations) is merged into a single doc, confusing audiences and diluting intent.

Core Features & Use Cases

  • Detection Rules: Rules to flag content that blends tutorial, how-to, reference, and explanation in one doc.
  • Bad Examples for Calibration: Concrete examples illustrating common collapse patterns to calibrate reviewers.
  • Remediation Strategies: Guidelines to split content into distinct, audience-aligned documents and map to user needs.
  • Use Case: Content teams auditing large documentation sets to ensure each document serves a single purpose.

Quick Start

Run a quick audit on a documentation set to flag mixed-pattern documents and apply the remediation guidelines.

Frequently Asked Questions about nw-collapse-detection

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

FAQPage Schema
What is documentation collapse and how does it affect content quality?

Documentation collapse occurs when tutorials, how-tos, references, and explanations are merged into a single document, confusing audiences and diluting intent. It degrades content quality by misaligning audience targets and obscuring the document's primary purpose.

How do I audit my knowledge base for mixed content anti-patterns?

You can audit a knowledge base by applying detection rules to flag content that blends multiple documentation quadrants. The process categorizes anti-patterns and provides structured remediation strategies to split mixed content into distinct, single-purpose documents.

What is the best way to fix type-mixing in technical documentation?

The best way to fix type-mixing is to split the merged content into distinct, audience-aligned documents based on structured remediation guidelines. This ensures each document serves a single purpose and maps correctly to specific user needs.

Can I run a content audit on an entire documentation set?

Yes, you can run an audit on an entire documentation set to flag mixed-pattern documents across the whole knowledge base. It identifies misaligned audience targets and merged sections for systematic remediation.

When should I split a document into separate tutorials and references?

You should split a document when detection rules identify that it blends tutorials, how-tos, references, and explanations. Separating these quadrants removes audience confusion and ensures each document serves a single, clear purpose.