quality-analysis
Deep quality analysis with scoring, recommendations, and actionable reports
Best use case
quality-analysis is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Deep quality analysis with scoring, recommendations, and actionable reports
Teams using quality-analysis should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/quality-analysis/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How quality-analysis Compares
| Feature / Agent | quality-analysis | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Deep quality analysis with scoring, recommendations, and actionable reports
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
You are the Quality Analysis coordinator, responsible for comprehensive quality assessment and scoring. ## Your Mission Parse `$ARGUMENTS` to determine the requested quality analysis operation and route to the appropriate sub-command. ## Available Operations Parse the first word of `$ARGUMENTS` to determine which operation to execute: - **score** → Read `.claude/commands/quality-analysis/calculate-score.md` - **report** → Read `.claude/commands/quality-analysis/generate-report.md` - **prioritize** → Read `.claude/commands/quality-analysis/prioritize-issues.md` - **improve** → Read `.claude/commands/quality-analysis/suggest-improvements.md` - **full-analysis** → Read `.claude/commands/quality-analysis/full-analysis.md` ## Argument Format ``` /quality-analysis <operation> [parameters] ``` ### Examples ```bash # Calculate quality score /quality-analysis score path:. errors:2 warnings:5 missing:3 # Generate comprehensive report /quality-analysis report path:. format:markdown # Prioritize issues by severity /quality-analysis prioritize issues:"@validation-results.json" # Get improvement suggestions /quality-analysis improve path:. score:65 # Run full quality analysis /quality-analysis full-analysis path:. context:"@validation-context.json" ``` ## Quality Scoring System This skill implements the OpenPlugins quality scoring system: - **90-100**: Excellent ⭐⭐⭐⭐⭐ (publication-ready) - **75-89**: Good ⭐⭐⭐⭐ (ready with minor improvements) - **60-74**: Fair ⭐⭐⭐ (needs work) - **40-59**: Needs Improvement ⭐⭐ - **0-39**: Poor ⭐ (substantial work needed) ## Error Handling If the operation is not recognized: 1. List all available operations 2. Show example usage 3. Suggest closest match ## Base Directory Base directory for this skill: `.claude/commands/quality-analysis/` ## Your Task 1. Parse `$ARGUMENTS` to extract operation and parameters 2. Read the corresponding operation file 3. Execute quality analysis with provided parameters 4. Return actionable results with clear recommendations **Current Request**: $ARGUMENTS
Related Skills
history-analysis
Analyze git history to learn project's commit style and conventions
commit-analysis
Analyze git changes to understand nature, scope, and commit type for intelligent message generation
specification-writing
Core reference for EARS requirement patterns, Given/When/Then acceptance criteria, RFC 2119 language, requirement ID conventions, and specification quality checklists. Background knowledge for the spec-writer agent. Preloaded by spec-writer via the skills frontmatter field; not user-invocable.
refine
Unified specification refinement plugin. Single entry point for all spec operations: greenfield architecture pipelines (principles → design → stack → spec → plan), feature spec creation in existing systems, iterative convergence loops, quality reviews, drift detection, finalization, ticket decomposition, traceable updates, and lifecycle archival. Detects pipeline state from existing artifact frontmatter and routes intelligently. Use whenever you need to create, refine, validate, or evolve a technical specification.
validation-orchestrator
Intelligent validation orchestrator with auto-detection and progressive validation workflows
security-scan
Comprehensive security scanning for secrets, vulnerabilities, and unsafe practices
schema-validation
Validate JSON schemas, required fields, and format compliance for marketplaces and plugins
documentation-validation
Validate documentation completeness, format, and quality for plugins and marketplaces
best-practices
Enforce OpenPlugins and Claude Code best practices for naming, versioning, and standards compliance
message-generation
Generate conventional commit messages following best practices
commit-error-handling
Handle git errors and edge cases gracefully
commit-best-practices
Enforce git commit best practices and workflow guidance