tessl-labs/skill-discovery
Discover and apply best practice skills automatically. Gap analysis scans the codebase, skill-search fills gaps from the registry, skill-classifier separates proactive from reactive skills, quality-standards generates CLAUDE.md guidance, self-review compares code against checklists, and verification-strategy sets up test/lint/typecheck feedback loops.
86
Quality
86%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Securityby
Advisory
Suggest reviewing before use
quality-block-generic.mdskills/quality-standards/references/
<!-- skill-discovery:start -->
<!-- Managed by tessl-labs/skill-discovery. Do not edit manually. -->
<!-- To remove: bash .tessl/tiles/tessl-labs/skill-discovery/skills/quality-standards/scripts/remove-quality-block.sh -->
Project Quality Standards
Backend
- Use structured error classes with error-handling middleware
- Use security headers (helmet) on every HTTP server
- Validate all API inputs before processing
- Use parameterized queries, never string interpolation for SQL
- Add indexes on every foreign key column
- Include a GET /health endpoint
- Use a structured logger, not console.log
Database
- Enable WAL mode and recommended pragmas
- Use migrations rather than inline CREATE TABLE
- Add indexes on foreign key and frequently-queried columns
Frontend
- Use error boundaries to catch component errors
- Add ARIA attributes on interactive elements for accessibility
- All form inputs must have labels
- Handle loading, error, and empty states for data-fetching components
Testing
- Write tests alongside features
- Every endpoint needs at least a happy-path and error-case test