claude-code-analyzer_skill

Overview

This skill analyzes Claude Code projects to surface usage patterns, detect project structure, and discover relevant community resources. It helps you generate actionable recommendations for CLAUDE.md, settings, and new skills or agents. Use it to rapidly understand how tools and models are used across one or many projects.

How this skill works

The scripts inspect project directories, CLI history, and GitHub to extract structured data. analyze-claude-md.sh detects package managers, frameworks, testing tools, and missing documentation sections; analyze.sh summarizes tool and model usage; github-discovery.sh queries GitHub for community skills, agents, and commands. Outputs are JSON-friendly for automated consumption and human-readable suggestions.

When to use it

• Onboarding a new repository to generate or improve CLAUDE.md
• Auditing tool and model usage to optimize cost or permissions
• Finding community skills, agents, or examples on GitHub
• Prioritizing what to document or automate after a usage analysis
• Identifying underused features that could improve developer workflows

Best practices

• Run analyze-claude-md.sh first to capture framework and package manager details
• Use analyze.sh --current-project for focused, up-to-date usage metrics
• Add frequently used tools to autoAllowedTools when analysis shows frequent use
• Install jq (required) and gh (optional) for full script functionality
• Feed JSON outputs into CI or dashboard pipelines for continuous monitoring

Example use cases

• Generate a CLAUDE.md template with detected package manager, framework, and commands
• Detect that Read and Edit are the top tools and add them to auto-allow settings
• Find community React skills on GitHub to adapt for a Next.js project
• Spot high-cost model usage and recommend lower-cost alternatives or limits
• Identify missing documented scripts and add them to the project documentation