Explain expert
全球最大的 Claude Code 技能聚合库 · 收录 3900+ 来自 12+ 来源的技能，提供在线搜索与趋势分析看板 / The world's largest Claude Code skill aggregation hub — 3900+ skills from 12+ sources with online search and trend dashboard
npx -y skills add bg-szy/TOP-SKILLS --skill explain-expertAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Analyze codebases and provide technical overviews covering core components, interactions, deployment architecture, and runtime behavior. Use when the user asks for codebase analysis, project overview, technical architecture explanation, or system documentation.
SKILL.md
2.1 KB, as published. Nobody here has run it
Explain Expert
Provide comprehensive technical codebase analysis following a structured approach. Stay focused on providing a technical overview that helps a developer quickly understand how the system works. Avoid personal opinions or implementation suggestions unless specifically asked.
Analysis Framework
When analyzing a codebase, follow these steps:
- Scan the repository structure - Identify main directories, configuration files, and entry points
- Read key files - Examine package.json, requirements.txt, docker files, README, and main source files
- Map dependencies - Note external libraries and frameworks used
- Trace execution flow - Follow how the application starts and processes requests
Core Components Analysis
Describe the major components or modules, their responsibilities, and any key classes or functions they contain. Note any relevant design patterns or architectural approaches.
Component Interactions
Explain how the components interact, including data and control flow, communication methods, and any APIs or interfaces used. Highlight use of dependency injection or service patterns if applicable.
Deployment Architecture
Deployment Architecture: Summarize the deployment setup, including build steps, external dependencies, required environments (e.g., dev, staging, prod), and infrastructure or containerization details.
Runtime Behavior
Describe how the application initializes, handles requests and responses, runs business workflows, and manages errors or background tasks.
When to Use This Skill
Apply this analysis when:
- User asks "explain this codebase"
- User requests "project overview"
- User needs "technical documentation"
- User asks "how does this system work"
- User requests "architecture analysis"