cc-skills

Claude Code Skills Marketplace: Meta-skills and foundational tools for Claude Code.

Run these commands in your terminal (not inside Claude Code):

# 1. Add the cc-skills marketplace
claude plugin marketplace add terrylica/cc-skills

# 2. Install all plugins (one-liner)
for p in itp plugin-dev gh-tools link-tools devops-tools dotfiles-tools doc-tools quality-tools productivity-tools mql5 itp-hooks alpha-forge-worktree ru iterm2-layout-config statusline-tools notion-api asciinema-tools git-town-workflow quant-research gmail-commander; do claude plugin install "$p@cc-skills"; done

# 3. Sync hooks to settings.json (requires cloning the repo)
git clone https://github.com/terrylica/cc-skills.git /tmp/cc-skills
/tmp/cc-skills/scripts/sync-hooks-to-settings.sh

# 4. Restart Claude Code to activate hooks
claude

claude plugin marketplace add terrylica/cc-skills

This clones the marketplace to ~/.claude/plugins/marketplaces/cc-skills/.

Verify installation:

claude plugin marketplace list
# Should show: cc-skills - Source: GitHub (terrylica/cc-skills)

# Install core plugins
claude plugin install itp@cc-skills
claude plugin install plugin-dev@cc-skills
claude plugin install gh-tools@cc-skills

# Install all remaining plugins
claude plugin install link-tools@cc-skills
claude plugin install devops-tools@cc-skills
claude plugin install dotfiles-tools@cc-skills
claude plugin install doc-tools@cc-skills
claude plugin install quality-tools@cc-skills
claude plugin install productivity-tools@cc-skills
claude plugin install mql5@cc-skills
claude plugin install itp-hooks@cc-skills
claude plugin install alpha-forge-worktree@cc-skills
claude plugin install ru@cc-skills
claude plugin install iterm2-layout-config@cc-skills
claude plugin install statusline-tools@cc-skills
claude plugin install notion-api@cc-skills
claude plugin install asciinema-tools@cc-skills
claude plugin install git-town-workflow@cc-skills
claude plugin install quant-research@cc-skills

Hooks provide pre/post tool use enforcement and session events. They must be explicitly synced to ~/.claude/settings.json:

# Clone the repository (if not already cloned)
git clone https://github.com/terrylica/cc-skills.git ~/cc-skills-temp

# Run the hook sync script
~/cc-skills-temp/scripts/sync-hooks-to-settings.sh
# Output: ✓ Hooks synced: PreToolUse=7, PostToolUse=3, Stop=5

Hooks require a restart to take effect:

# Exit any running Claude Code sessions, then:
claude

# Check marketplace is registered
claude plugin marketplace list

# Inside Claude Code, verify commands are available
# Type "/" and look for itp:go, plugin-dev:create, etc.

When new versions are released:

# Update the marketplace repository
cd ~/.claude/plugins/marketplaces/cc-skills
git pull

# Reinstall updated plugins (or specific ones)
claude plugin install itp@cc-skills

# Re-sync hooks
./scripts/sync-hooks-to-settings.sh  # From the repo directory

Cause: Marketplace repository is out of sync or has stale data.

Fix:

# Update the marketplace
cd ~/.claude/plugins/marketplaces/cc-skills
git pull

# Retry installation
claude plugin install plugin-name@cc-skills

Cause: Plugins installed but commands not discovered.

Fix:

1. Verify plugin is installed:

   # Check installed_plugins.json
   cat ~/.claude/plugins/installed_plugins.json | grep "cc-skills"

2. Restart Claude Code (fresh session required)

3. If still not working, clear cache and reinstall:

   rm -rf ~/.claude/plugins/cache/cc-skills
   claude plugin install plugin-name@cc-skills

Cause: Hooks not synced to settings.json.

Fix:

# Sync hooks
cd /path/to/cc-skills
./scripts/sync-hooks-to-settings.sh

# Restart Claude Code

Verify hooks are registered:

cat ~/.claude/settings.json | jq '.hooks | keys'
# Should show: ["PreToolUse", "PostToolUse", "Stop"]

Cause: Known Claude Code issue with SSH clone failures.

Fix:

# Remove and re-add with explicit clone
claude plugin marketplace remove cc-skills
rm -rf ~/.claude/plugins/marketplaces/cc-skills

# Clone manually via HTTPS
git clone https://github.com/terrylica/cc-skills.git ~/.claude/plugins/marketplaces/cc-skills

# Re-add to known_marketplaces.json
# Add this entry to ~/.claude/plugins/known_marketplaces.json:
# "cc-skills": {
#   "source": {"source": "github", "repo": "terrylica/cc-skills"},
#   "installLocation": "$HOME/.claude/plugins/marketplaces/cc-skills",
#   "lastUpdated": "2026-01-13T00:00:00.000Z"
# }

Cause: Cache has old plugin version.

Fix:

# Check current cached version
ls ~/.claude/plugins/cache/cc-skills/itp/

# Clear specific plugin cache
rm -rf ~/.claude/plugins/cache/cc-skills/itp

# Reinstall
claude plugin install itp@cc-skills

~/.claude/plugins/
├── known_marketplaces.json      # Registered marketplaces
├── installed_plugins.json       # Installed plugins with versions
├── marketplaces/
│   └── cc-skills/               # Cloned marketplace repository
│       ├── .claude-plugin/
│       │   └── marketplace.json # Plugin registry (SSoT)
│       └── plugins/
│           ├── itp/
│           ├── plugin-dev/
│           └── ...
└── cache/
    └── cc-skills/               # Cached plugin copies
        ├── itp/
        │   └── <version>/       # Version-specific cache
        └── ...

The known_marketplaces.json entry for cc-skills:

{
  "cc-skills": {
    "source": {
      "source": "github",
      "repo": "terrylica/cc-skills"
    },
    "installLocation": "$HOME/.claude/plugins/marketplaces/cc-skills",
    "lastUpdated": "<timestamp>"
  }
}

Based on compatibility with Claude Code's plugin loader:

DO NOT use trailing slashes in source paths:

// CORRECT
"source": "./plugins/itp"

// WRONG - causes "Source path does not exist" error
"source": "./plugins/itp/"

The author field must be an object, not a string:

// CORRECT
"author": {
  "name": "Your Name",
  "url": "https://github.com/username"
}

// WRONG - causes validation error
"author": "Your Name"

Only standard fields are allowed. These cause validation errors:

// WRONG - unrecognized keys
"commands_dir": "commands",
"references_dir": "references",
"scripts_dir": "scripts"

{
  "name": "my-plugin",
  "version": "<version>",
  "description": "Plugin description (min 10 chars)",
  "keywords": ["keyword1", "keyword2"],
  "author": {
    "name": "Your Name",
    "url": "https://github.com/username"
  }
}

{
  "name": "my-plugin",
  "description": "Plugin description",
  "version": "<version>",
  "source": "./plugins/my-plugin",
  "category": "development",
  "author": {
    "name": "Your Name",
    "url": "https://github.com/username"
  },
  "keywords": ["keyword1", "keyword2"],
  "strict": false
}

# Validate marketplace structure
bun scripts/validate-plugins.mjs

# Check for schema errors
bun scripts/validate-plugins.mjs --fix

Understanding the architectural hierarchy:

Hierarchy:

Plugin (Container)
├── commands/           → Slash commands (/plugin:command)
├── skills/             → Bundled skills (copied to ~/.claude/skills/ on install)
│   └── skill-name/
│       ├── SKILL.md    → Skill definition (frontmatter + instructions)
│       ├── scripts/    → Executable helpers
│       └── references/ → Supporting docs
├── hooks/              → Hook definitions (hooks.json)
├── scripts/            → Plugin-level utilities
└── references/         → Plugin-level documentation

Key distinctions:

• install → Acquire packages/tools via package manager (brew install, npm install)
• setup → Verify environment post-installation (/itp:setup checks dependencies)
• init → Create initial directory structure (one-time scaffolding)
• configure → Adjust settings in config files (iterative customization)

Some plugins use skills from other plugins. Install dependencies first for full functionality.

Note: doc-tools and itp have a circular dependency (both provide diagram tools). Install both for full functionality.

Run bun scripts/validate-plugins.mjs --deps to see the full dependency graph.

Marketplace plugin commands display with the plugin:command format:

Why the colon format?

• Display: Claude Code always shows the full plugin:command namespace in autocomplete and command lists
• Invocation: You may type /go, /setup, or /hooks directly if no naming conflicts exist with other installed plugins
• Clarity: The namespace identifies which plugin provides each command

Important edge case: When the command name equals the plugin name (e.g., /foo:foo), you must use the full format. Typing /foo alone is interpreted as the plugin prefix, not the command.

cc-skills/
├── .claude-plugin/
│   ├── plugin.json          # Marketplace metadata
│   └── marketplace.json     # Plugin registry (23 plugins) - SSoT
├── plugins/
│   ├── itp/                       # ADR-driven development workflow (11 bundled skills)
│   ├── plugin-dev/                # Plugin development + skill architecture
│   ├── gh-tools/                  # GitHub workflow automation
│   ├── link-tools/                # Comprehensive link validation
│   ├── devops-tools/              # Doppler, secrets, MLflow, Telegram, recovery
│   ├── dotfiles-tools/            # Chezmoi dotfile management
│   ├── doc-tools/                 # ASCII diagrams, standards, LaTeX, Pandoc PDF
│   ├── quality-tools/             # Code clones, E2E validation, profiling, schema
│   ├── productivity-tools/        # Slash command generation
│   ├── mql5/                      # MQL5 development (indicators + mql5.com)
│   ├── itp-hooks/                 # ITP workflow enforcement hooks
│   ├── alpha-forge-worktree/      # Git worktree management
│   ├── ru/                        # Autonomous loop mode (Ralph Universe)
│   ├── iterm2-layout-config/      # iTerm2 workspace layout configuration
│   ├── statusline-tools/          # Custom status line with indicators
│   ├── notion-api/                # Notion API integration
│   ├── asciinema-tools/           # Terminal recording automation
│   ├── git-town-workflow/         # Prescriptive git-town workflow
│   └── quant-research/            # Quantitative research metrics
├── scripts/
│   ├── sync-hooks-to-settings.sh  # Hook synchronization
│   ├── validate-plugins.mjs       # Plugin validation
│   └── marketplace.schema.json    # JSON Schema for marketplace.json
├── .mise/tasks/                   # Release automation tasks
│   ├── release:full               # Complete 4-phase release
│   ├── release:sync               # Sync hooks and marketplace
│   └── ...
├── plugin.json                    # Root plugin config
├── package.json                   # Node.js + semantic-release
└── README.md

This marketplace uses semantic-release with mise task automation:

# Check release status
mise run release:status

# Full release workflow (preflight → version → sync → verify)
mise run release:full

# Dry run (no changes)
mise run release:dry

# Manual hook sync only
mise run release:hooks

# Sync marketplace to ~/.claude after release
mise run release:sync

Implement-The-Plan workflow: ADR-driven 4-phase development.

Execute approved plans from Claude Code's Plan Mode through a structured workflow:

• Preflight: ADR + Design Spec creation with graph-easy diagrams
• Phase 1: Implementation with engineering standards
• Phase 2: Format & Push to GitHub
• Phase 3: Release (semantic-release) & Publish (PyPI)

Commands: /itp:go, /itp:setup, /itp:release, /itp:hooks

Bundled Skills: adr-code-traceability, adr-graph-easy-architect, bootstrap-monorepo, code-hardcode-audit, graph-easy, impl-standards, implement-plan-preflight, mise-configuration, mise-tasks, pypi-doppler, semantic-release

Plugin and skill development: structure validation, silent failure auditing, skill architecture meta-skill.

• skill-architecture - Meta-skill for creating skills (YAML frontmatter, TodoWrite templates)
• plugin-validator - Validate plugin structure, manifests, and detect silent script failures

Commands: /plugin-dev:create

Autonomous AI orchestration with Ralph Wiggum technique.

Features:

• RSSI (Recursively Self-Improving Super Intelligence) loop mode
• Multi-signal task completion detection
• Validation exhaustion scoring
• Plan archive preservation
• Runtime limit configuration

Commands: /ru:start, /ru:stop, /ru:status, /ru:settings, /ru:hooks

Additional setup required: See plugins/ru/README.md

GitHub workflow automation with intelligent GFM link validation.

• Detects broken repository-relative links
• Auto-fixes common link patterns
• Integrates with gh CLI workflows

Link validation: portability checks, broken link detection, path policy linting.

• link-validator - Validates relative path usage for cross-installation compatibility
• link-validation - Broken link detection with path policy linting (on-demand)

Doppler credentials, Firecrawl self-hosted, ML pipelines, MLflow queries, notifications, and session recovery.

17 bundled skills: clickhouse-cloud-management, clickhouse-pydantic-config, claude-code-proxy-patterns, disk-hygiene, distributed-job-safety, doppler-workflows, doppler-secret-validation, dual-channel-watchexec, firecrawl-research-patterns, ml-data-pipeline-architecture, ml-failfast-validation, mlflow-python, project-directory-migration, pueue-job-orchestration, python-logging-best-practices, session-chronicle, session-recovery

Comprehensive documentation: ASCII diagrams, markdown standards, LaTeX build, Pandoc PDF generation.

Nine bundled skills: ascii-diagram-validator, documentation-standards, glossary-management, latex-build, latex-setup, latex-tables, pandoc-pdf-generation, plotext-financial-chart, terminal-print

Code quality and validation tools: clone detection, E2E validation, profiling, schema testing.

Six bundled skills: clickhouse-architect, code-clone-assistant, multi-agent-e2e-validation, multi-agent-performance-profiling, schema-e2e-validation, symmetric-dogfooding

ITP workflow enforcement via PreToolUse and PostToolUse hooks.

• Hard block on manual ASCII art
• Ruff Python linting reminders
• Graph-easy skill reminders
• ADR/Design Spec sync reminders

Custom Claude Code status line with git status indicators.

• Git status indicators (modified, deleted, staged, untracked)
• Remote tracking (ahead/behind commits)

Commands: /statusline-tools:setup

See individual plugin READMEs for detailed documentation:

• dotfiles-tools - Chezmoi dotfile management
• productivity-tools - Slash command generation
• mql5 - MQL5 development
• alpha-forge-worktree - Git worktree management
• iterm2-layout-config - iTerm2 workspace configuration
• notion-api - Notion API integration
• asciinema-tools - Terminal recording automation
• git-town-workflow - Prescriptive git-town workflow

1. Fork the repository
2. Create a plugin in plugins/your-plugin/
3. Add entry to .claude-plugin/marketplace.json
4. Ensure plugin.json follows the schema (see For Plugin Developers)
5. Run bun scripts/validate-plugins.mjs
6. Submit a pull request

MIT