How do I install the Nw Collapse Detection skill?

Run npx skillmds add thedixitjain/nw-collapse-detection in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Nw Collapse Detection safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Nw Collapse Detection?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Nw Collapse Detection free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Nw Collapse Detection?

thedixitjain (@thedixitjain) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Nw Collapse Detection by thedixitjain

Name: Nw Collapse Detection
Rating: 4.5 (4 reviews)
Author: thedixitjain

File contents

Collapse Detection

Documentation collapse = types merge inappropriately, serving no audience well.

Anti-Patterns

Tutorial Creep

Description: Tutorial explains "why" extensively | Detection: explanation >20% | Fix: extract to separate doc, link back

How-to Bloat

Description: How-to teaches basics first | Detection: teaching fundamentals before steps | Fix: link to tutorial, assume baseline

Reference Narrative

Description: Reference includes conversational prose | Detection: prose paragraphs in entries | Fix: move to explanation doc, keep factual

Explanation Task Drift

Description: Explanation ends with "do this" steps | Detection: step-by-step in explanation | Fix: move steps to how-to, link

Hybrid Horror

Description: Single doc tries all four types | Detection: 3+ quadrants in one doc | Fix: split with clear boundaries

Detection Rules

Flag collapse when:

20% content from adjacent quadrant | Two user needs served simultaneously | Ambiguous user journey stage
"Why" in tutorials | Task steps in explanations | Teaching in how-tos | Narrative in references

Bad Examples for Calibration

Tutorial with Task Focus

# Getting Started
If you need to deploy to production, follow these steps...

Problem: Assumes user knows what "deploy to production" means. A tutorial should assume nothing.

How-to Teaching Basics

# How to Configure Authentication
First, let's understand what authentication is. Authentication is...

Problem: Should assume user knows what authentication is. Link to a tutorial instead.

Reference with Opinions

## login(username, password)
This is probably the most important function you'll use...

Problem: Reference should be factual, not opinionated. Remove "probably the most important" editorializing.

Explanation with Steps

# Why We Use Microservices
... therefore, you should: 1. Create a service, 2. Deploy it...

Problem: Steps belong in a how-to guide. The explanation should end with reasoning and link to the how-to for action.

Source: nWave-ai/nWave → nWave/skills/nw-collapse-detection/SKILL.md

Also appears in: nWave-ai/nWave/plugins/nw/skills/nw-collapse-detection/SKILL.md

---name: nw-collapse-detectiondescription: Documentation collapse anti-patterns - detection rules, bad examples, and remediation strategies for type-mixing violations---# Collapse DetectionDocumentation collapse = types merge inappropriately, serving no audience well.## Anti-Patterns### Tutorial CreepDescription: Tutorial explains "why" extensively | Detection: explanation >20% | Fix: extract to separate doc, link back### How-to BloatDescription: How-to teaches basics first | Detection: teaching fundamentals before steps | Fix: link to tutorial, assume baseline### Reference NarrativeDescription: Reference includes conversational prose | Detection: prose paragraphs in entries | Fix: move to explanation doc, keep factual### Explanation Task DriftDescription: Explanation ends with "do this" steps | Detection: step-by-step in explanation | Fix: move steps to how-to, link### Hybrid HorrorDescription: Single doc tries all four types | Detection: 3+ quadrants in one doc | Fix: split with clear boundaries## Detection RulesFlag collapse when:- >20% content from adjacent quadrant | Two user needs served simultaneously | Ambiguous user journey stage- "Why" in tutorials | Task steps in explanations | Teaching in how-tos | Narrative in references## Bad Examples for Calibration### Tutorial with Task Focus```markdown# Getting StartedIf you need to deploy to production, follow these steps...```**Problem**: Assumes user knows what "deploy to production" means. A tutorial should assume nothing.### How-to Teaching Basics```markdown# How to Configure AuthenticationFirst, let's understand what authentication is. Authentication is...```**Problem**: Should assume user knows what authentication is. Link to a tutorial instead.### Reference with Opinions```markdown## login(username, password)This is probably the most important function you'll use...```**Problem**: Reference should be factual, not opinionated. Remove "probably the most important" editorializing.### Explanation with Steps```markdown# Why We Use Microservices... therefore, you should: 1. Create a service, 2. Deploy it...```**Problem**: Steps belong in a how-to guide. The explanation should end with reasoning and link to the how-to for action.---**Source:** [`nWave-ai/nWave`](https://github.com/nWave-ai/nWave) → `nWave/skills/nw-collapse-detection/SKILL.md`**Also appears in:** `nWave-ai/nWave/plugins/nw/skills/nw-collapse-detection/SKILL.md`

Frequently asked questions