Agent skill
quality-standards
Defines code quality benchmarks, standards compliance, and best practices for maintaining high-quality codebases
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/quality-standards
SKILL.md
Overview
This skill provides standards and benchmarks for code quality including linting rules, formatting standards, naming conventions, and quality thresholds across programming languages.
Quality Score Thresholds
- Excellent: 90-100
- Good: 70-89
- Acceptable: 50-69
- Needs Improvement: Below 50
Language-Specific Standards
Python
- PEP 8: Style guide for Python code
- Type Hints: Use for public APIs
- Docstrings: Google or NumPy style
- Line Length: Max 88-100 characters (Black standard)
JavaScript/TypeScript
- ESLint: Use recommended config + project rules
- Prettier: For consistent formatting
- Naming: camelCase for variables, PascalCase for classes
- TypeScript: Enable strict mode
Quality Components
- Tests Passing (30%): All tests must pass
- Standards Compliance (25%): Linting/formatting adherence
- Documentation (20%): Complete docstrings/comments
- Pattern Adherence (15%): Follow established patterns
- Code Metrics (10%): Complexity and duplication
When to Apply
Use when validating code quality, enforcing standards, or setting quality benchmarks for projects.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?