Claude Skills
Custom plugins and tools for Claude Code.
Background
I started building what I called "frameworks" over a year before Claude officially released Skills. Same concept, different name.
The idea came from frustration. I was tired of repeating the same instructions every conversation. Instead of starting fresh each time, I asked AI to analyze our successful interactions and create frameworks capturing recurring requirements and preferences. These became reusable project knowledge.
This approach produced results: 3 published Drupal contrib modules, 17+ blog articles, automated social media campaigns, and phase-based editorial workflows.
When Claude released Skills officially, I recognized what I'd been building. This repository translates those frameworks into proper Skills with tooling.
I wrote more about this methodology in My Journey with AI Tools.
Installation
# Add the marketplace
/plugin marketplace add https://github.com/camoa/claude-skills
# Install individual plugins
/plugin install dev-guides-navigator@camoa-skills
/plugin install drupal-dev-framework@camoa-skills
/plugin install plugin-creation-tools@camoa-skills
/plugin install brand-content-design@camoa-skills
/plugin install code-quality-tools@camoa-skills
/plugin install drupal-htmx@camoa-skills
/plugin install code-paper-test@camoa-skills
Known Issues
Skills not auto-discovered on startup
There's a known bug in Claude Code affecting git-based marketplaces. Skills may fail to load during initialization with "no such file or directory" errors because Claude Code looks for skill files in the wrong location.
Workaround: Skills still work when invoked via the Skill tool (slash commands). The issue only affects automatic discovery at startup.
Status: Awaiting fix from Anthropic.
Plugins
dev-guides-navigator (v0.1.0)
Smart guide discovery and routing for the dev-guides site. Routes AI to the correct guide using hash-based caching and KG metadata for disambiguation.
- Caches
llms.txt with hash-based freshness check — no redundant fetches
- KG metadata (
concepts/not fields) prevents wrong-guide selection (e.g., "story.yml" routes to UI Patterns, not Storybook)
- Two-hop routing:
llms.txt → topic index.md → specific guide
- 1200+ atomic decision guides across 66 topics
# Invoked automatically before design/dev tasks, or manually:
/dev-guides-navigator style guide
drupal-dev-framework (v3.6.0)
Systematic 3-phase Drupal development workflow: Research → Architecture → Implementation. Enforces SOLID, TDD, DRY, security, and code purposefulness through 5 quality gates. Requires dev-guides-navigator — loads Drupal domain guides proactively at every phase.
/plugin install dev-guides-navigator@camoa-skills # Required dependency
/plugin install drupal-dev-framework@camoa-skills
/drupal-dev-framework:new my_module # Create project
/drupal-dev-framework:next # Continue work (main entry point)
| Component | Contents |
|---|
| Commands | 11 (/new, /next, /research, /research-team, /design, /implement, /complete, /status, /validate, /pattern, /migrate-tasks) |
| Agents | 5 with cost control (maxTurns) — project-orchestrator, architecture-drafter, architecture-validator (isolated worktree), pattern-recommender, contrib-researcher |
| Skills | 16 (phase management, TDD companion, guide integration, context loading) |
| References | 6 methodology docs (SOLID, TDD, DRY, Library-First, Quality Gates, Purposeful Code) |
| Hooks | SessionStart (dependency check + project context), PreCompact (context preservation) |
Features competing agent research (/research-team) with Build/Use/Extend debate for features and competing hypothesis investigation for bugs.
See drupal-dev-framework/README.md for full documentation.
plugin-creation-tools (v2.3.0)
Complete guide for creating Claude Code plugins — skills, commands, agents, hooks, MCP servers, and configuration. Covers 18 hook events, 4 hook types (command/prompt/agent/HTTP), agent isolation and cost control, marketplace distribution with 6 source types, and pushy description optimization.
# Just describe what you want:
Create a plugin called "my-tools" with a deploy command
# Or use specific commands:
/plugin-creation-tools:create my-tools --skill --agent --hook
/plugin-creation-tools:validate ./my-tools
| Component | Contents |
|---|
| Skills | 1 (plugin-creation — 30+ reference docs, templates, examples) |
| Commands | 3 (/create, /add-component, /validate) |
| Agents | 2 (skill-quality-reviewer, plugin-structure-auditor) |
brand-content-design (v2.8.0)
