154+ methodology skills providing systematic approaches to development workflows and best practices.
Skills are reusable methodologies that guide how Claude approaches problems. They auto-activate based on context and provide frameworks, patterns, and best practices without executing code directly.
Key Concept: Skills provide methodology (HOW), Agents provide execution (WHO).
# Install all skills
git clone https://github.com/I-Onlabs/claude-code-skills.git
cp -r claude-code-skills/*/ ~/.claude/skills/
# Install specific skills
cp -r claude-code-skills/systematic-debugging ~/.claude/skills/
cp -r claude-code-skills/api-design-patterns ~/.claude/skills/Systematic processes for development tasks
| Skill | Purpose | When It Activates |
|---|---|---|
| systematic-debugging | 4-phase debugging framework | Bug fixing, troubleshooting |
| test-driven-development | RED-GREEN-REFACTOR cycle | Writing tests, TDD approach |
| task-tracking | Auto todo management | Complex multi-step tasks (3+) |
| quality-gates | Pre-completion verification | Before claiming work complete |
| verification-before-completion | Prove success with evidence | Final validation |
| pipeline-pm-spec | INVEST user stories | Feature planning |
| pipeline-arch-review | Architecture Decision Records | Design decisions |
| pipeline-implement | TDD-driven implementation | Feature development |
| pipeline-test-verify | Comprehensive quality gates | Testing workflows |
Design patterns and best practices
| Skill | Purpose | Use For |
|---|---|---|
| api-design-patterns | 5-layer API pattern | REST/GraphQL API structure |
| python-best-practices | Modern Python 3.11+ patterns | Pythonic code |
| defense-in-depth | Multi-layer validation | Security, data integrity |
| intelligent-gate | Risk assessment framework | Risky operations |
| token-optimization | Efficiency patterns | Cost optimization |
| code-refactor | Bulk refactoring patterns | Large-scale changes |
Framework-specific guidance
AWS:
aws-agentic-ai- Bedrock AgentCore (Gateway, Runtime, Memory, Identity)aws-cdk-development- Infrastructure as Code with CDKaws-cost-operations- Cost optimization and monitoringaws-serverless-eda- Serverless patterns (Lambda, API Gateway, EventBridge)
Kubernetes:
kubernetes-patterns- K8s best practices, deployment patterns
Web Frameworks:
- React, Next.js, Vue patterns
- Component architecture, state management
Language idioms and best practices
- Python - Type hints, async/await, data science
- TypeScript - Type safety, modern patterns
- Go - Concurrency, interfaces, idiomatic Go
- Rust - Ownership, lifetimes, memory safety
- Java - Modern Java features
Productivity and integration
| Skill | Purpose |
|---|---|
| local-models | Ollama integration guide (gpt-oss, qwen3-coder) |
| escalation-reasoning | 5-tier reasoning (/think, /megathink, /ultrathink) |
| intelligent-decision-making | Multi-model consensus |
| code-execution | Local Python execution for cost savings |
| github-code-review | GitHub PR workflows |
| playwright-skill | Browser automation |
Specialized expertise by domain
Security:
- Security patterns, OWASP compliance, vulnerability scanning
Performance:
- Profiling, optimization, caching strategies
Data:
agentdb-*- Vector search, memory patterns, learning algorithms- Data engineering - ETL pipelines, schema design
DevOps:
- CI/CD patterns, container orchestration
Quality:
- Code review methodology, testing strategies
Content creation and design
content-creator- SEO-optimized marketing contentalgorithmic-art- Generative art with p5.jscanvas-design- Visual designarchitecture-diagram-creator- System architecture diagramsdashboard-creator- KPI dashboards
Data processing and visualization
agentdb-vector-search- Semantic search and embeddingsagentdb-memory-patterns- Persistent memory for agentscsv-data-summarizer- Quick data analysismeeting-insights-analyzer- Extract insights from transcripts
Complex multi-phase workflows
| Skill | Phases | Use For |
|---|---|---|
| hoa-orchestrator | G0βG1βSβG2βG3βG4βM | Quality-gated deliverables with formal verification |
| vibe-coding-coordinator | Preparation phase | Understanding vague requests |
| bootstrap-orchestrator | Auto-configuration | New project initialization |
| task-orchestrator | Task breakdown | Complex multi-task features |
Skills activate automatically based on:
- Keywords in your request (triggers)
- Task context (debugging, testing, API design, etc.)
- Description matching (similar task patterns)
Examples:
You: "Fix this bug"
β systematic-debugging auto-activates
β Guides through 4-phase framework
You: "Create an API endpoint"
β api-design-patterns auto-activates
β Provides 5-layer structure
You: "This task is complex"
β task-tracking auto-activates
β Creates todo list for tracking
Each skill directory contains:
skill-name/
βββ SKILL.md # Methodology and usage
βββ CLAUDE.md # (Optional) Additional context
βββ examples/ # (Optional) Example files
SKILL.md frontmatter:
---
name: skill-name
description: Brief description of when/how to use
triggers:
- keyword1
- keyword2
- keyword3
---
# Methodology content...- systematic-debugging - 4-phase root cause analysis
- root-cause-tracing - Deep investigation patterns
- error-detective (agent) - Automated debugging
- task-tracking - Break into steps
- pipeline-pm-spec - Write user stories
- pipeline-implement - TDD implementation
- pipeline-test-verify - Quality verification
- api-design-patterns - 5-layer structure
- test-driven-development - Test-first approach
- quality-gates - Pre-deployment checks
- verification-before-completion - Prove success
- quality-gates - Systematic verification
- code-reviewer (agent) - Automated review
# Sync latest changes from local skills
cd claude-code-skills/
./sync-from-local.sh
# Commit and push
git add .
git commit -m "Update skills from local"
git push- Create skill directory:
mkdir my-skill - Create
my-skill/SKILL.mdwith YAML frontmatter - Document methodology (not implementation)
- Add clear triggers for auto-activation
- Test with real scenarios
Template:
---
name: my-skill
description: Brief description of when/how to use
triggers:
- keyword1
- keyword2
---
# My Skill
## Purpose
What this skill helps with
## When to Use
Specific scenarios where this applies
## Methodology
Step-by-step approach to applyContributions welcome! When adding or modifying skills:
- Skills provide methodology, not code execution
- Use clear triggers for auto-activation
- Document when and how to use
- Keep focused on single responsibility
- Test with realistic scenarios
MIT License - See LICENSE for details
Repository: 154+ methodology skills Categories: Workflow β’ Patterns β’ Frameworks β’ Languages β’ Tools β’ Domains β’ Creative β’ Data β’ Orchestration Activation: Automatic based on triggers and context