# Analyze Claude Code Component Quality

Poorly described components are hard to invoke, secure, and maintain. This skill scores Claude Code components and suggests concrete improvements.

## Install

```bash
npx skillstore add c0ntr0lledcha0s/analyzing-component-quality
```

## Metadata

- - Slug: c0ntr0lledcha0s-analyzing-component-quality
- - Version: 1.0.0
- - Author: C0ntr0lledCha0s
- - GitHub username: C0ntr0lledCha0s
- - License: MIT
- - Repository: https://github.com/C0ntr0lledCha0s/claude-code-plugin-automations/tree/main/self-improvement/skills/analyzing-component-quality
- - Ref: main
- - Supported tools: Claude, Codex, Claude Code
- - Risk level: medium
- - Risk factors: scripts, filesystem, external\_commands, network
- - Quality score: 74
- - Public page: https://skillstore.pages.dev/skills/c0ntr0lledcha0s-analyzing-component-quality
- - Manifest: https://skillstore.pages.dev/api/skills/c0ntr0lledcha0s-analyzing-component-quality/manifest

## Capabilities

- Scores descriptions, tool permissions, triggers, security, and usability on a 1 to 5 scale.
- Reviews agents, skills, commands, and hooks using documented quality standards.
- Identifies unclear descriptions, excessive tools, weak triggers, and documentation gaps.
- Provides prioritized improvement suggestions with before-and-after guidance.
- Includes a Python helper for heuristic scoring of markdown component files.

## Use Cases

- Review a Skill Before Publishing: Check whether a Claude Code skill has clear triggers, suitable tools, and useful documentation.
- Audit Agent Tool Permissions: Evaluate whether an agent uses the smallest practical tool set for its stated purpose.
- Improve Internal Component Standards: Apply a consistent scoring rubric across team-created skills, agents, commands, and hooks.

## Prompt Templates

### Basic Component Review

```
Analyze this Claude Code component for quality. Score each dimension and list the top three improvements.
```

### Tool Permission Check

```
Review the tool permissions for this component. Explain which tools are justified, risky, or unnecessary.
```

### Marketplace Readiness Audit

```
Assess whether this component is ready for a marketplace. Include quality scores, security concerns, and required changes.
```

### Advanced Rubric Comparison

```
Compare these components using the quality rubric. Rank them, identify shared weaknesses, and propose standard improvements.
```

## Limitations

- Assumes the component already passed technical validation.
- Does not prove runtime safety or replace manual security review.
- Some referenced helper files are described but not included in this package.
- The scoring rubric is heuristic and may need human judgment for edge cases.

## Best Practices

- Review the component file and supporting references before assigning final scores.
- Quote exact text when explaining weak descriptions, vague triggers, or risky permissions.
- Prioritize fixes that reduce tool access, clarify invocation, or improve user outcomes.

## Anti Patterns

- Do not treat technical validity as proof of marketplace quality.
- Do not approve broad Bash, Write, Edit, or Task access without a clear need.
- Do not give generic feedback when a specific rewrite or tool change is possible.

## Security Audit

- - Safe to publish: true
- - Audited at: 2026-06-28T18:06:36.76\+00:00
- - Summary: Static analysis reported many command, weak-crypto, credential, and network patterns, but review found most are markdown examples or scoring text. No prompt injection, obfuscation, credential access, or network exfiltration was found. The remaining concern is that the skill grants Bash and ships a helper script that reads a caller-provided local path.

## Stats

- - Views: 183
- - Downloads: 4
- - Favorites: 0
- - Popularity score: 0