GitHub
getting-started-with-skills
Skills wiki intro - mandatory workflows, search tool, brainstorming triggers
☆ 38View skill
obra AI Skills
GitHub ↗Browse published AI skills maintained by obra. Compare skill descriptions and follow each source repository for setup instructions.
Author statistics
Indexed skills
60Repository stars across indexed skills
624,117Repository forks
48,432Average repository stars per indexed skill
10,402Repository stars may repeat across skills from the same repository.
Popular categories
Recent indexing activity
Browse skills
GitHub
localizing-variables
Declare variables in smallest possible scope, initialize close to first use, minimize span and live time
☆ 38View skill
GitHub
root-cause-tracing
Systematically trace bugs backward through call stack to find original trigger
☆ 38View skill
GitHub
simplifying-control-flow
Flatten nested conditionals with early returns or table-driven methods - keep nesting depth under 3 levels
☆ 38View skill
GitHub
systematic-debugging
Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions.
☆ 38View skill
GitHub
verification-before-completion
Run verification commands and confirm output before claiming success
☆ 38View skill
GitHub
installing-skills-system
Fork, clone to ~/.clank, run installer, edit CLAUDE.md
☆ 38View skill
GitHub
domain-focused-naming
Name code by what it does in the domain, not how it's implemented or its history
☆ 38View skill
GitHub
keeping-routines-focused
Each routine does one thing and does it well - extract when routines have multiple responsibilities
☆ 38View skill
GitHub
maintaining-consistent-abstractions
Class interfaces present one cohesive abstraction - don't mix domain logic with serialization, persistence, or unrelated concerns
☆ 38View skill
GitHub
exploring-alternatives
Try 2-3 different approaches before implementing - don't settle for first design you think of
☆ 38View skill
GitHub
encapsulating-complexity
Hide implementation details behind interfaces - work at domain level (what), not implementation level (how)
☆ 38View skill
GitHub
writing-plans
Create detailed implementation plans with bite-sized tasks for engineers with zero codebase context
☆ 38View skill
GitHub
testing-skills-with-subagents
RED-GREEN-REFACTOR for process documentation - baseline without skill, write addressing failures, iterate closing loopholes
☆ 38View skill
GitHub
single-purpose-variables
Use each variable for exactly one purpose - no hybrid coupling or hidden meanings
☆ 38View skill
GitHub
commenting-intent
Comment WHY code exists and non-obvious decisions, not WHAT code does (mechanics)
☆ 38View skill
GitHub
reducing-complexity
Managing complexity is software's primary technical imperative - all other goals are secondary
☆ 38View skill
GitHub
designing-before-coding
Design in pseudocode first, iterate approaches, then translate to code
☆ 38View skill
GitHub
remembering-conversations
Search previous Claude Code conversations for facts, patterns, decisions, and context using semantic or text search
☆ 38View skill
GitHub
naming-variables
Choose names that fully and accurately describe what the variable represents
☆ 38View skill
GitHub
brainstorming-ideas-into-designs
Interactive idea refinement using Socratic method to develop fully-formed designs
☆ 38View skill
GitHub
subagent-driven-development
Execute implementation plan by dispatching fresh subagent for each task, with code review between tasks
☆ 38View skill
GitHub
requesting-code-review
Dispatch code-reviewer subagent to review implementation against plan or requirements before proceeding
☆ 38View skill
GitHub
executing-plans
Execute detailed plans in batches with review checkpoints
☆ 38View skill
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.