integration
Cadrianmae Marketplace Integration
Generate documentation for installed marketplace plugins and add to CLAUDE.md.
Quick Example
# Scans ~/.claude/marketplaces/cadrianmae-claude-marketplace/plugins/
# Generates marketplace-plugins.md with skills and commands from each plugin
# Adds import to ~/.claude/CLAUDE.md
Overview
This skill helps integrate marketplace plugins into your workflow by:
- Scanning installed plugins from cadrianmae-claude-marketplace
- Extracting skills and commands from each plugin
- Generating a structured reference section
- Adding to user-level or project-level CLAUDE.md
When to Use
- After installing new marketplace plugins
- Setting up a new project
- Updating documentation of available tools
- Creating project-specific plugin references
Workflow
1. Ask User for Scope
Use AskUserQuestion to determine integration level:
Question: "Where should I add the marketplace plugin documentation?"
Options:
- "User-level (~/.claude/CLAUDE.md)" - Available in all projects
- "Project-level (./CLAUDE.md)" - Only this project
2. Scan Installed Plugins
MARKETPLACE_DIR=~/.claude/marketplaces/cadrianmae-claude-marketplace/plugins
# List all installed plugins
for plugin in "$MARKETPLACE_DIR"/*/; do
plugin_name=$(basename "$plugin")
echo "Found: $plugin_name"
done
3. Extract Plugin Information
For each plugin, read:
plugin.json- Plugin metadata (name, version, description)skills/*/SKILL.md- Skill informationcommands/*.md- Slash command list
4. Generate Documentation File
Create separate markdown file with plugin documentation:
File: marketplace-plugins.md
# Cadrianmae Marketplace Plugins
Available plugins from cadrianmae-claude-marketplace.
## Plugin: semantic-search
**Version:** 1.0.0
**Description:** Semantic search across codebases using odino
**Skills:**
- `semantic-search` - Natural language code search with query inference
**Commands:**
- `/semq:search <query>` - Search indexed codebase
- `/semq:here <query>` - Search with directory traversal
- `/semq:index [path]` - Create semantic index
- `/semq:status` - Show index stats
**Usage:** Auto-invokes on "where is..." or "find code that..." queries
---
## Plugin: pandoc
**Version:** 1.0.0
**Description:** Document conversion toolkit
**Skills:**
- `pandoc` - Document conversion with templates and validation
**Commands:**
- `/pandoc:help` - Plugin overview
- `/pandoc:template` - Generate templates
- `/pandoc:validate` - Validate frontmatter
- `/pandoc:convert` - Convert documents
- `/pandoc:restyle` - Transform document styles
**Usage:** Auto-invokes for document conversion tasks
---
*Last updated: 2025-11-19*
*Generated by cadrianmae-integration skill*
5. Add Import to CLAUDE.md
Use import syntax: @ path/to/file (no space between @ and path).
Supports up to 5 nesting levels. Imports inside code blocks are ignored.
User-level:
CLAUDE_FILE=~/.claude/CLAUDE.md
PLUGINS_DOC=~/.claude/marketplace-plugins.md
# Write plugin documentation to separate file
cat > "$PLUGINS_DOC" << 'EOF'
# Cadrianmae Marketplace Plugins
...
EOF
# Add import to CLAUDE.md if not already present
IMPORT_LINE="@ ~/.claude/marketplace-plugins.md"
if ! grep -q "@ ~/.claude/marketplace-plugins.md" "$CLAUDE_FILE"; then
echo "" >> "$CLAUDE_FILE"
echo "# Marketplace Plugins" >> "$CLAUDE_FILE"
echo "$IMPORT_LINE" >> "$CLAUDE_FILE"
fi
Project-level:
CLAUDE_FILE=./CLAUDE.md
PLUGINS_DOC=./marketplace-plugins.md
# Write plugin documentation
cat > "$PLUGINS_DOC" << 'EOF'
# Project-Specific Plugin Documentation
...
EOF
# Create CLAUDE.md if doesn't exist
if [[ ! -f "$CLAUDE_FILE" ]]; then
echo "# Project CLAUDE.md" > "$CLAUDE_FILE"
echo "" >> "$CLAUDE_FILE"
fi
# Add import
IMPORT_LINE="@ ./marketplace-plugins.md"
if ! grep -q "@ ./marketplace-plugins.md" "$CLAUDE_FILE"; then
echo "" >> "$CLAUDE_FILE"
echo "# Marketplace Plugins" >> "$CLAUDE_FILE"
echo "$IMPORT_LINE" >> "$CLAUDE_FILE"
fi
Import syntax rules:
- Format:
@ path(@ immediately followed by path, space for display only) - Relative:
@ ./file.mdor@ subdir/file.md - Absolute:
@ /absolute/path/file.md - Home dir:
@ ~/.claude/file.md - Code blocks: Imports in backticks/code blocks are ignored
- Nesting: Max 5 levels deep
- Verify: Use
/memorycommand to check loaded imports
Benefits:
- Clean separation of concerns
- Update plugin docs without touching CLAUDE.md
- Easier to maintain and regenerate
- Can share plugin docs across multiple CLAUDE.md files
Output Format
After completion, show:
✓ Marketplace integration complete
Files created:
~/.claude/marketplace-plugins.md (plugin documentation)
Import added to:
~/.claude/CLAUDE.md
Added line:
@ ~/.claude/marketplace-plugins.md
Plugins documented:
• semantic-search (1.0.0)
• pandoc (1.0.0)
• cadrianmae-integration (1.0.0)
3 plugins, 3 skills, 11 commands
Plugin docs will be loaded in all Claude Code sessions!
Verify with: /memory
Edge Cases
No plugins installed:
No marketplace plugins found in:
~/.claude/marketplaces/cadrianmae-claude-marketplace/plugins/
Install plugins first, then run this skill.
Section already exists: Ask user:
- Replace existing section
- Append to existing section
- Cancel
File locations:
- User-level:
~/.claude/CLAUDE.md(affects all projects) - Project-level:
./CLAUDE.md(workspace root, affects only this project)
Best Practices
- Run after installing plugins - Keep documentation current
- Choose scope wisely:
- User-level: Plugins you use in all projects
- Project-level: Project-specific plugin workflows
- Update regularly - Re-run when adding/removing plugins
- Review generated section - Verify accuracy before committing
Example Integration
User-level CLAUDE.md:
# CLAUDE.md (Global)
## User Context
...
## Coding Preferences
...
## Cadrianmae Marketplace Plugins
Available plugins from cadrianmae-claude-marketplace.
### Plugin: semantic-search
...
### Plugin: pandoc
...
Project-level CLAUDE.md:
# Project: Data Pipeline
## Project Context
This project uses semantic-search for finding algorithm implementations
and pandoc for generating reports.
## Cadrianmae Marketplace Plugins
### Plugin: semantic-search
**Primary use:** Finding ML algorithm implementations in knowledge base
**Commands used:** /semq:search, /semq:here
### Plugin: pandoc
**Primary use:** Converting weekly reports to PDF
**Commands used:** /pandoc:convert, /pandoc:validate
Related
- Global CLAUDE.md:
~/.claude/CLAUDE.md - Project CLAUDE.md:
./CLAUDE.md(workspace root) - Plugin directory:
~/.claude/marketplaces/cadrianmae-claude-marketplace/plugins/
More from cadrianmae/claude-marketplace
datetime
Use the `date` command via Bash tool whenever you or the user mention time, dates, or temporal concepts. Verify current date/time before ANY temporal response, as environment context may be outdated. Parse expressions like "tomorrow", "next week", "3 days", "in 2 weeks", "next Monday at 3pm". Proactively invoke for deadlines, schedules, time-sensitive tasks, week numbers, or any date/time reference.
70pandoc
Automatically assist with Pandoc document conversions when user mentions converting markdown to PDF/DOCX/HTML or other formats. Validate YAML frontmatter, check dependencies (bibliography, images), and provide format-specific conversion guidance. Use when user asks about citations, academic papers, presentations, or document generation from markdown.
6update
Update the current development session with progress notes
5list
List all development sessions
5nvr-list
This skill should be used when the user asks to "list neovim instances", "show all nvim", "what neovim processes are running", "list all editors", "show all active neovim", or wants to see all running neovim instances across all projects.
5current
Show the current session status
5