Sponsor Suno AI Music arrow_forward
Slash Command

Analyze Skill

Analyze skill file complexity metrics and generate modularization recommendations for splitting or progressive loading.

Type
Slash Command
GitHub stars
339
License
MIT
Repo last updated
Sep 24, 2026

What Analyze Skill is

Analyze Skill is a slash command published in the athola/claude-night-market repository on GitHub, which has about 339 stars. The repository describes itself as: “23 Claude Code plugins: TDD enforcement hooks, git/PR workflows, spec-driven development, code review, project lifecycle, fix-from-error, maintenance automation, context optimization, research, and multi-LLM delegation. 186 skills, 128 commands, 54 agents.”

A slash command is a reusable prompt saved as a markdown file and run by typing its name after a slash. In Claude Code, custom commands have been merged into skills: a file in .claude/commands/ and a skill folder in .claude/skills/ both create the same kind of command, and existing command files keep working.

Analyze Skill gives you a repeatable way to run the same instructions without retyping them, optionally with arguments.

How to install Analyze Skill

Claude Code

  1. Download analyze-skill.md from the repository.
  2. Save it to ~/.claude/commands/ (all projects) or .claude/commands/ (one project). As a skill, you can instead save it as ~/.claude/skills/<name>/SKILL.md.
  3. Run it by typing / followed by its name.

Claude Cowork

  1. Turn the command into a skill: create a folder with the file saved as SKILL.md and zip it.
  2. In Customize → Skills, click +, then upload the ZIP.
  3. Run it from any task with / and the skill name.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from plugins/abstract/commands/analyze-skill.md, shared under the repository's MIT license. Read the full file on GitHub.

Analyzes a skill file for complexity metrics and provides modularization recommendations based on the modular-skills framework.

When To Use

Use this command when you need to:

  • Assessing skill file complexity before adding content
  • Planning modularization strategies
  • Checking if a skill needs to be split
  • Validating progressive disclosure design

When NOT To Use

Avoid this command if:

  • Evaluating skill quality - use /skills-eval instead
  • Estimating token usage only - use /estimate-tokens instead
  • Creating new skills - use /create-skill instead

Usage

# Analyze specific skill file
/analyze-skill skills/my-skill/SKILL.md

# Analyze skill directory
/analyze-skill skills/my-skill

# Analyze current directory (if in a skill folder)
/analyze-skill .

What It Analyzes

The analyzer evaluates several complexity dimensions:

Metrics Collected

  • Line count: Total lines vs threshold (default: 150)
  • Word/character count: Content density indicators
  • Theme sections: Number of # level headings
  • Subsections: Number of ## level headings
  • Code blocks: Embedded code examples
  • Estimated tokens: Context window impact

Recommendations Generated

  • MODULARIZE: File exceeds thresholds, should be split
  • CONSIDER: Approaching limits, evaluate for future growth
  • OK: Within acceptable complexity bounds

Examples

/analyze-skill skills/modular-skills/SKILL.md
# Output:
# === Analysis for: skills/modular-skills/SKILL.md ===
# Line count: 180 (threshold: 150)
# Estimated tokens: 1,847
# === Recommendations ===
# MODULARIZE: File exceeds threshold (180 > 150)
# GOOD: Token usage in optimal range

/analyze-skill skills/skills-eval --verbose
# Includes detailed section breakdown

Integration with Modular Skills

This command is the first step in the modular-skills workflow:

  1. Analyze → Use this command to assess complexity
  2. Design → Plan module structure based on recommendations
  3. Estimate → Use /estimate-tokens for token budgeting
  4. Validate → Use /skills-eval for quality checks

Implementation

python3 ${CLAUDE_PLUGIN_ROOT}/scripts/skill_analyzer.py --file "${1:-.}"

Before you install

  • Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
  • Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
  • Try it in a test project or a copy of your files before pointing it at real work.
  • Pin the version you tested, and review changes before updating.
  • Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is Analyze Skill?

Analyze Skill is a slash command for Claude Code and Claude Cowork from the athola/claude-night-market repository on GitHub. Analyze skill file complexity metrics and generate modularization recommendations for splitting or progressive loading.

How do I install Analyze Skill in Claude Code?

Download analyze-skill.md from the repository. Save it to ~/.claude/commands/ (all projects) or .claude/commands/ (one project). As a skill, you can instead save it as ~/.claude/skills/<name>/SKILL.md. Run it by typing / followed by its name.

Can I use Analyze Skill in Claude Cowork?

Turn the command into a skill: create a folder with the file saved as SKILL.md and zip it. In Customize → Skills, click +, then upload the ZIP. Run it from any task with / and the skill name.

Is Analyze Skill safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under MIT. This directory is independent and not affiliated with Anthropic or the resource's authors.