integration
Integrate cadrianmae marketplace plugins into CLAUDE.md. Scans installed plugins and generates documentation section listing available skills and commands. User chooses between user-level (global) or project-level (current project only) integration.
What this skill does
# Cadrianmae Marketplace Integration
Generate documentation for installed marketplace plugins and add to CLAUDE.md.
## Quick Example
```bash
# Scans ${CLAUDE_PLUGIN_ROOT}/../ (marketplace plugins directory)
# 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:
1. Scanning installed plugins from cadrianmae-claude-marketplace
2. Extracting skills and commands from each plugin
3. Generating a structured reference section
4. 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
```bash
MARKETPLACE_DIR="${CLAUDE_PLUGIN_ROOT}/.."
# 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 information
- `commands/*.md` - Slash command list
### 4. Generate Documentation File
Create separate markdown file with plugin documentation:
**File:** `marketplace-plugins.md`
```markdown
# 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:**
```bash
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:**
```bash
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.md` or `@ 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 `/memory` command 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_PLUGIN_ROOT}/../
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
1. **Run after installing plugins** - Keep documentation current
2. **Choose scope wisely:**
- User-level: Plugins you use in all projects
- Project-level: Project-specific plugin workflows
3. **Update regularly** - Re-run when adding/removing plugins
4. **Review generated section** - Verify accuracy before committing
## Example Integration
**User-level CLAUDE.md:**
```markdown
# 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:**
```markdown
# 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_PLUGIN_ROOT}/../` (parent of any installed plugin)
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.