A formal evaluation framework for Claude Code sessions, implementing eval-driven development (EDD) principles. Eval-Driven Development treats evals as the "unit tests of AI development": - Define expected behavior BEFORE implementation…
This is an example of a project-specific skill. Use this as a template for your own projects. Based on a real production application: Zenith - AI-powered customer discovery platform. Reference…
Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist and patterns.
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
A comprehensive verification system for Claude Code sessions. Invoke this skill: - After completing a feature or significant code change - Before creating a PR - When you want to…
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.