code-analysis
Improve Code Readability
Teams often write code that only developers can follow. This skill checks names, comments, jargon, and documentation so broader teams can understand code faster.
Download the skill ZIP
Upload in Claude
Go to Settings → Capabilities → Skills → Upload skill
Toggle on and start using
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "code-analysis". A Python file with short variable names and few comments.
Expected outcome:
The report gives a moderate score, flags unclear names, and suggests fuller names with explanatory comments.
Using "code-analysis". A TypeScript file with API jargon in comments.
Expected outcome:
The report identifies unexplained technical terms and suggests plain English definitions.
Using "code-analysis". A well-documented service file.
Expected outcome:
The report gives a high score and notes that the file is accessible to non-developers.
Security Audit
Low RiskThe static weak cryptography findings are false positives caused by readability terms such as token, serialize, and hash-related wording, not cryptographic operations. The Markdown backtick findings are also false positives from fenced examples and documented CLI usage. The skill is safe to publish with a low warning because it runs a local script that reads user-selected files and may print code snippets.
Low Risk Issues (4)
Risk Factors
⚡ Contains scripts (2)
📁 Filesystem access (1)
⚙️ External commands (1)
Detected Patterns
Quality Score
What You Can Build
Review stakeholder-facing code
Check whether business logic has clear names and plain comments before a product review.
Prepare onboarding examples
Find missing explanations before sharing code with new team members.
Improve documentation quality
Identify jargon and missing What, Why, and How context in source comments.
Try These Prompts
Use the code-analysis skill to review this file for non-developer readability: [file path].
Analyze [file path] with focus on naming. Explain which names should be clearer and why.
Review [file path] for a new team member. Prioritize comments, jargon, and missing context.
Analyze [file path] with strict readability expectations. Summarize blockers before this code is shared with stakeholders.
Best Practices
- Run it on intended project files, not files that contain secrets.
- Use strict mode before sharing code with non-developer audiences.
- Review each suggestion manually before changing established domain terms.
Avoid
- Do not treat the score as proof that the code is correct.
- Do not scan private credentials, keys, or sensitive configuration files.
- Do not replace human documentation review with automated findings alone.