-
-
Notifications
You must be signed in to change notification settings - Fork 286
Troubleshooting
Common issues and how to fix them.
Symptom: You installed a plugin but Claude does not recognize its skills or commands.
Fixes:
- Restart Claude Code. Some changes require a fresh session to be discovered.
- Verify the plugin directory structure is correct:
ls ~/.claude/plugins/my-plugin/.claude-plugin/plugin.json - Check that
plugin.jsonis valid JSON:cat ~/.claude/plugins/my-plugin/.claude-plugin/plugin.json | python3 -m json.tool
- Run
ccpi doctorto check for configuration issues.
Symptom: You say something that should trigger a skill, but Claude uses general capabilities instead.
Fixes:
-
Check the description: The
descriptionfield in frontmatter must include "Use when..." and trigger phrases. If the trigger phrases do not match what you are saying, Claude will not activate the skill. -
Check frontmatter syntax: Ensure the YAML between
---delimiters is valid. A missing colon or broken indentation will prevent parsing. -
Check the name: The
namefield must be kebab-case and match the folder name. -
Check discovery location: Verify the skill is in one of the four discovery paths:
~/.claude/skills/.claude/skills/- Inside a plugin's
skills/directory - Built-in
-
Try manual invocation: Type
/skill-nameto invoke it directly. If that works, the issue is with trigger phrase matching. -
Check allowed-tools: If
allowed-toolsis malformed (e.g., missing quotes, unscoped Bash), the skill may fail silently.
Symptom: Running ccpi returns "command not found".
Fixes:
- Verify global installation:
pnpm list -g @intentsolutionsio/ccpi
- If not installed, install it:
pnpm add -g @intentsolutionsio/ccpi
- Check that pnpm's global bin directory is in your PATH:
Add that directory to your shell's PATH if it is missing.
pnpm bin -g
- If you use
nvmor another Node version manager, make sure you are on the same Node version where you installed ccpi.
Symptom: ccpi search returns stale or no results.
Fixes:
- Re-add the marketplace:
/plugin marketplace remove claude-code-plugins /plugin marketplace add jeremylongshore/claude-code-plugins - Run
ccpi updateto pull the latest catalog. - Check your internet connection -- the CLI fetches from GitHub Pages.
Symptom: A plugin's scripts or MCP server fail with "Permission denied".
Fixes:
- Make shell scripts executable:
chmod +x path/to/script.sh
- For MCP server plugins, the compiled
dist/index.jsmust be executable:chmod +x plugins/mcp/my-plugin/dist/index.js
- Verify the file has a proper shebang line (
#!/usr/bin/env nodefor Node.js scripts).
Symptom: An MCP plugin's tools are not available, or Claude reports a connection error.
Fixes:
-
Check the build: MCP plugins must be compiled before use:
cd plugins/mcp/my-plugin && pnpm build
-
Check .mcp.json: The MCP configuration file must point to the correct
dist/index.jspath. -
Check dependencies: Run
pnpm installinside the plugin directory. - Check Node version: MCP plugins require Node.js >= 18.
-
Test manually: Run the server directly to see error output:
node plugins/mcp/my-plugin/dist/index.js
Symptom: pnpm build or marketplace build fails.
Fixes:
-
Clean install: Remove
node_modulesand reinstall:rm -rf node_modules && pnpm install -
Check package manager: The root uses pnpm, but the
marketplace/directory uses npm. Do not mix them.# Root pnpm install && pnpm build # Marketplace cd marketplace && npm install && npm run build
-
Run validation first:
pnpm run sync-marketplace ./scripts/validate-all-plugins.sh
-
Check TypeScript errors:
pnpm typecheck
Symptom: The validator reports errors for your SKILL.md file.
Common issues:
| Error | Fix |
|---|---|
| "Name must be kebab-case" | Rename to lowercase-with-hyphens |
| "Missing required field" | Add all 6 required frontmatter fields |
| "Bash must be scoped" | Change Bash to Bash(git:*) or similar |
| "Version must be SemVer" | Use x.y.z format (e.g., 1.0.0) |
| "Body exceeds 500 lines" | Move content to references/ directory |
| "Missing required section" | Add all 7 body sections (Overview through Resources) |
| "Use CLAUDE_SKILL_DIR" | Replace ${CLAUDE_PLUGIN_ROOT} with ${CLAUDE_SKILL_DIR}
|
Run the full validator with details:
python3 scripts/validate-skills-schema.py --verbose --skills-onlyIf these steps do not resolve your issue:
- GitHub Discussions: Ask a question -- community Q&A and troubleshooting
- Issue Tracker: Report a bug -- for confirmed bugs and feature requests
- Discord: Claude Developers Discord -- 40,000+ members, real-time help
- Email: jeremy@intentsolutions.io -- for security issues or private inquiries
When reporting an issue, include:
- Your Node.js version (
node --version) - Your ccpi version (
ccpi --version) - The exact error message or unexpected behavior
- Steps to reproduce the problem
- Installation -- setup walkthrough
- CLI Quick Reference -- all commands
- Your First Plugin -- plugin structure guide
- Your First Skill -- skill creation guide
tonsofskills.com | GitHub | Discussions | Report Issue | v4.17.0
SKILL.md Specification Skill Template Skill Creator
- Plugin Structure
- Frontmatter Reference
- Tool Permissions Guide
- Templates & Examples
- Validation & Grading
- MCP Server Plugins
- Playbook Index
- 01 Multi-Agent Rate Limits
- 02 Cost Caps & Budgets
- 03 MCP Reliability
- 04 Ollama Migration
- 05 Incident Debugging
- 06 Self-Hosted Stack
- 07 Compliance & Audit
- 08 Team Presets
- 09 Cost Attribution
- 10 Progressive Enhancement
- 11 Advanced Tool Use