Agent skill · Documentation

Dark Matter Analyzer

Analyze repositories to reveal unseen patterns, strategic drift, and organizational health. Use when assessing repository coherence, diagnosing project issues, identifying documentation inflation, or understanding why a codebase feels misaligned with its stated goals.

majiayu000github.com/majiayu000GitHub ↗
claude-codecan modify filesMIT
Install
npx skills add majiayu000/claude-skill-registry --skill dark-matter-analyzer --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 13 KB
Bundled scripts: none
Version: 1.0.0
Allowed tools: ReadGrepGlobBashTask
Path: skills/analysis/dark-matter-analyzer/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Dark Matter Analyzer ## Purpose Dark Matter Mode reveals what is **unseen, unsaid, and unmeasured** in repositories and codebases. It goes beyond code quality metrics to illuminate the invisible architectures shaping system behavior — identifying strategic drift, documentation inflation, execution gaps, and organizational health patterns that traditional tools miss. > "Every repo is a psyche made visible." This skill helps diagnose **why** a repository feels off, not just **what** is wrong technically. ## When to Use This Skill - Repository feels misaligned but traditional metrics look fine - Documentation is extensive but team still feels confused - Stated goals don't match actual work being done - Need to understand organizational patterns in codebase structure - Project velocity is high but coherence feels low - Planning significantly outpaces execution - Multiple overlapping documents on same topics - Need to assess "Repository Coherence Index" (RCI) - Preparing for major refactor or reorganization - **When NOT to use:** Simple bug fixes, feature additions, or standard code reviews ## Core Methodology ### Step 1: Sensing — Signal Ingest **Objective:** Capture ambient signals

What's inside
Steps it walks through
  1. Purpose
  2. When to Use This Skill
  3. Core Methodology
  4. Step 1: Sensing — Signal Ingest
  5. Step 2: Pattern Detection — Weak Signal Mapping
  6. Step 3: Reflection — Meaning Extraction
  7. Step 4: Action Routing — Coherence Restoration
  8. Step 5: Repository Coherence Index (RCI)
  9. Key Principles
  10. Decision Framework
  11. Output Format
  12. Dark Matter Report Structure
  13. MCP Integration
  14. Examples
Ships with 1 file
  • metadata.json
Commands it runs
Count documentation files
find . -name "*.md" -type f | wc -l
Find technical debt markers
grep -r "TODO\|FIXME\|HACK" --include="*.ts" --include="*.js"
Check commit patterns
git log --oneline --since="1 month ago" | head -20
Find documentation inflation
find DOCS -name "*.md" -exec wc -l {} \; | awk '{sum+=$1} END {print sum}'
More from claude-skill-registry
All skills →
About this skill
What does the Dark Matter Analyzer skill do?

Analyze repositories to reveal unseen patterns, strategic drift, and organizational health. Use when assessing repository coherence, diagnosing project issues, identifying documentation inflation, or understanding why a codebase feels misaligned with its stated goals.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill dark-matter-analyzer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going