Agent skill · Documentation

whole-analyzer

Pre-editing analysis for Whole documentation. Use when: (1) Starting new editing session, (2) Checking for duplicates across domains, (3) Analyzing section completeness, (4) Validating structure before bulk edits, (5) Generating analysis reports.

majiayu000github.com/majiayu000GitHub ↗
claude-coderead-onlyMIT
Install
npx skills add majiayu000/claude-skill-registry --skill whole-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: 5 KB
Bundled scripts: none
Version: 2.1.0
Declared author: Whole Project
Allowed tools: -Grep-Read-Glob-Task
Path: skills/analysis/whole-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

# Whole Content Analyzer ## Purpose Run comprehensive analysis on Whole documentation sections before editing begins. ## Integration with Agents ### When to Invoke Agents Use Task tool to invoke specialized analysis agents for deep analysis: ```javascript // For deep duplicate semantic analysis Task(subagent_type: 'whole-translator', prompt: 'Analyze semantic similarity and cultural context for potential duplicates in CF[N]') // For cross-reference graph analysis before editing Task(subagent_type: 'whole-cross-reference', prompt: 'Build reference graph and analyze connectivity patterns for CF[N]') // For comprehensive content structure validation Task(subagent_type: 'whole-content-validator', prompt: 'Pre-validate content structure and identify gaps in CF[N]') ``` ### When NOT to Use Agents - Simple concept counting → Use Grep directly - Basic duplicate detection (exact matches) → Use Grep with concept names - Format checking → Use shared utilities from `.claude/skills/shared` - Quick inventory → Use Grep pattern matching ## Analysis Types ### 1. Content Inventory - Count concepts per section - Identify incomplete 4-point descriptions - Count cross-references ### 2. Duplicate Detec

What's inside
Steps it walks through
  1. Purpose
  2. Integration with Agents
  3. When to Invoke Agents
  4. When NOT to Use Agents
  5. Analysis Types
  6. 1. Content Inventory
  7. 2. Duplicate Detection
  8. 3. Structural Check
  9. 4. Gap Analysis
  10. Analysis Workflow
  11. Phase 1: Quick Analysis (Scripts & Grep)
  12. Phase 2: Agent-Based Deep Analysis
  13. Phase 3: Report Generation
  14. Agent Integration Guide
Ships with 1 file
  • metadata.json
Commands it runs
Basic structure and format checks
grep -n "^#### \*\*[0-9]" Whole.md | wc -l  # Count concepts
grep -n "→ \*\*Liên kết:" Whole.md | wc -l   # Count cross-refs
More from claude-skill-registry
All skills →
About this skill
What does the whole-analyzer skill do?

Pre-editing analysis for Whole documentation. Use when: (1) Starting new editing session, (2) Checking for duplicates across domains, (3) Analyzing section completeness, (4) Validating structure before bulk edits, (5) Generating analysis reports.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill whole-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