Code review methodology and quality standards for comprehensive code analysis. Use to understand WHAT and HOW to review code: 11 review dimensions, process, quality standards.
Sets up dev infrastructure for new projects: framework init, folder structure, Docker, pre-commit hooks (gitleaks), testing infrastructure, .gitignore.
Pre-deploy acceptance testing methodology: run test suite (unit/integration/E2E), verify acceptance criteria from user-spec and tech-spec. Does not require live environment.
Comprehensive security analysis against OWASP Top 10 standards. Use after code-reviewer for code handling: authentication, user input, database queries, external APIs.
Design test scenarios for skills through user interview. Reads the target skill, interviews the user about scope and edge cases, saves scenario files for skill-tester to execute.
Execute test scenarios prepared by skill-test-designer. Spawns parallel runners with and without the skill, interacts as user persona, grades acceptance criteria, produces detailed test report.
A folder with a SKILL.md file: a name, a description of when to use it, and instructions. Claude loads a skill only when the task matches its description.
How do I use one I find here?
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
What do the warnings mean?
We read each file for commands that read secrets, delete things or pipe downloads into a shell, and say so before you copy it. No warning is not a promise that a file is safe.
Which skills worked for people?
Open a skill to see its discussion. Reports from people and their agents are coming.