Skill Creator
obra
58 published skills · 534,570 GitHub stars across the catalog. View on GitHub ↗
writing-clearly-and-concisely
Apply Strunk's timeless writing rules to ANY prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Makes your writing clearer, stronger, and more professional.
mcp-cli
Use MCP servers on-demand via the mcp CLI tool - discover tools, resources, and prompts without polluting context with pre-loaded MCP integrations
using-tmux-for-interactive-commands
Use when you need to run interactive CLI tools (vim, git rebase -i, Python REPL, etc.) that require real-time input/output - provides tmux-based approach for controlling interactive sessions through detached sessions and send-keys
browsing
Use when you need direct browser control - teaches Chrome DevTools Protocol for controlling existing browser sessions, multi-tab management, form automation, and content extraction via use_browser MCP tool
example-workflow
Use when demonstrating plugin workflow features - shows how skills can guide multi-step processes
developing-claude-code-plugins
Use when working on Claude Code plugins (creating, modifying, testing, releasing, or maintaining) - provides streamlined workflows, patterns, and examples for the complete plugin lifecycle
working-with-claude-code
Use when working with Claude Code CLI, plugins, hooks, MCP servers, skills, configuration, or any Claude Code feature - provides comprehensive official documentation for all aspects of Claude Code
exploring-alternatives
Try 2-3 different approaches before implementing - don't settle for first design you think of
commenting-intent
Comment WHY code exists and non-obvious decisions, not WHAT code does (mechanics)
test-driven-development-tdd
Write the test first, watch it fail, write minimal code to pass
testing-anti-patterns
Never test mock behavior. Never add test-only methods to production classes. Understand dependencies before mocking.
defense-in-depth-validation
Validate at every layer data passes through to make bugs impossible
maintaining-consistent-abstractions
Class interfaces present one cohesive abstraction - don't mix domain logic with serialization, persistence, or unrelated concerns
encapsulating-complexity
Hide implementation details behind interfaces - work at domain level (what), not implementation level (how)
writing-evergreen-comments
Write comments explaining WHAT and WHY, never temporal context or history
brainstorming-ideas-into-designs
Interactive idea refinement using Socratic method to develop fully-formed designs
refactoring-safely
Refactor with tests first, one change at a time, never mix refactoring with bug fixes or new features
domain-focused-naming
Name code by what it does in the domain, not how it's implemented or its history
getting-started-with-skills
Skills wiki intro - mandatory workflows, search tool, brainstorming triggers
validating-inputs
Check all external inputs for validity - garbage in, nothing out, never garbage out
single-purpose-variables
Use each variable for exactly one purpose - no hybrid coupling or hidden meanings
simplifying-control-flow
Flatten nested conditionals with early returns or table-driven methods - keep nesting depth under 3 levels
root-cause-tracing
Systematically trace bugs backward through call stack to find original trigger
gardening-skills-wiki
Maintain skills wiki health - check links, naming, cross-references, and coverage