Claude Code Skills Marketplace
A centralized repository of reusable Claude Code skills that can be integrated into any project. These skills extend Claude's capabilities with specialized workflows, from commit automation to architecture reviews.
What is This?
This marketplace contains 30+ production-ready skills abstracted from multiple projects and designed to work anywhere. Each skill is:
- Fully abstracted - No hardcoded project-specific values
- Configurable - Per-skill configuration files you customize
- Battle-tested - Migrated from real-world production projects
- Well-documented - Complete usage examples and configuration references
Quick Start
Option 1: Install from Marketplace (Recommended)
Install all bundles or choose specific ones:
# Add the marketplace
/plugin marketplace add aigensa/claude_marketplace
# Install all bundles
/plugin install github@thesolutionarchitect_marketplace
/plugin install development-tools@thesolutionarchitect_marketplace
/plugin install architecture-quality@thesolutionarchitect_marketplace
/plugin install content-specialized@thesolutionarchitect_marketplace
# Or install just what you need
/plugin install github@thesolutionarchitect_marketplace
Available Bundles:
- github (5 skills) - git:commit, github:pull-request, github:story-create, github:story-fetch, github:story-play
- development-tools (5 skills) - bug-fix, claude:skill-creator, claude:refactor-skill, claude:sync-skills, gather-context
- architecture-quality (6 skills) - aws:architect, aws:cdk, review:security, review:performance, review:overall, arch:fitness-function
- content-specialized (12 skills) - css-architecture, ux-professional, creative-writing, editor-in-chief, mermaid-diagram, and more
Option 2: Manual Copy (For Customization)
1. Browse the Catalog
See SKILL_CATALOG.md for the complete list of available skills.
2. Copy a Skill to Your Project
# Example: Copy the commit skill to your project
cp -r .claude/skills/git:commit/ /path/to/your/project/.claude/skills/
3. Configure the Skill
cd /path/to/your/project/.claude/skills/git:commit/
# Copy the example config and customize it
cp config.example.yaml config.yaml
# Edit config.yaml with your project-specific values
vim config.yaml
4. Use the Skill
The skill is now available in your project. Invoke it via Claude Code:
/commit
Structure
claude_marketplace/
├── .claude/
│ └── skills/ # All marketplace skills (auto-discovered)
│ ├── _templates/ # Skill creation templates
│ ├── git:commit/ # Git commit automation
│ ├── github:pull-request/ # Pull request creation
│ ├── github:story-create/ # Issue creation
│ └── [30+ more skills...]
├── docs/ # Detailed guides
│ ├── abstraction-guide.md
│ ├── configuration-reference.md
│ └── migration-notes.md
├── SKILL_CATALOG.md # Complete skill index
└── USAGE_GUIDE.md # Detailed usage instructions
Skill Categories
Core Workflow
- git:commit - Automated commit creation with issue numbering
- github:pull-request - Pull request creation
- github:story-create - GitHub issue creation
- github:story-fetch - Issue fetching and management
- github:story-play - Story workflow activation
Development
- bug-fix - Bug fix workflow
- claude:skill-creator - Create new skills
- claude:refactor-skill - Refactor existing skills
- claude:sync-skills - Synchronize skills across projects
- gather-context - Code exploration and context gathering
Architecture & Quality
- aws:architect - AWS architecture guidance
- aws:cdk - CDK infrastructure as code
- review:security - Security code reviews
- review:performance - Performance analysis
- review:overall - General code reviews
- arch:fitness-function - Architecture validation
Team Orchestration
- team:agile-dev - 5-agent TDD team with story-driven workflow
Content & Specialized
- css-architecture - CSS architecture patterns
- ux-professional - UX guidance
- creative-writing - Content creation
- editor-in-chief - Editorial review
- mermaid-diagram - Diagram generation
- arch:create-adr - Architecture decision records
- gather-nfr - Non-functional requirements
- claude:hooks - Claude Code hooks configuration
How It Works
Template Variables
Skills use template variable syntax to remain project-agnostic:
# In config.yaml
project:
prefix: "MYPROJ" # Your project prefix
name: "My Cool Project"
repository:
slug: "myorg/my-repo"
default_branch: "main"
paths:
active_story: ".agile-dev-team/active-story.yaml"
commands:
type_check: "npm run type-check"
test: "npm test"
Skills reference these as {{PROJECT_PREFIX}}, {{REPO_SLUG}}, etc.
