Installation¶

CMS Cultivator can be installed in Claude Code, Claude Desktop, or OpenAI Codex — globally for all projects or per-project for team collaboration.

Prerequisites¶

Before installing CMS Cultivator, ensure you have:

• Claude Code CLI or OpenAI Codex installed and configured
• Git for version control
• GitHub CLI (gh) for PR creation commands (optional)
• DDEV (for Kanopi projects) - Install DDEV

Claude Code Installation¶

Method 1: Via Marketplace (Recommended)¶

This is the easiest method and enables automatic updates. Installs globally for all projects.

Step 1: Start Claude Code¶

cd /path/to/your/project
claude

Step 2: Add the Claude Toolbox Marketplace¶

Inside Claude Code CLI:

/plugin marketplace add kanopi/claude-toolbox

Step 3: Install CMS Cultivator¶

/plugin install cms-cultivator@claude-toolbox

Step 4: Verify Installation¶

/plugin

Select "Manage Plugins" and you should see cms-cultivator in the list of installed plugins.

Updating Via Marketplace¶

Inside Claude Code CLI:

/plugin update cms-cultivator@claude-toolbox

Method 2: Direct from GitHub¶

Install directly without adding a marketplace. Installs globally for all projects.

Inside Claude Code CLI:

/plugin install https://github.com/kanopi/cms-cultivator

This method installs the latest version from the main branch.

Updating Direct Installation¶

Inside Claude Code CLI:

/plugin update cms-cultivator

Method 3: Manual Installation (Development)¶

For plugin development or testing local changes. Installs globally for all projects.

Step 1: Clone the Repository¶

cd ~/.claude/plugins
git clone https://github.com/kanopi/cms-cultivator.git

ls -la ~/.claude/plugins/ 2>/dev/null || ls -la ~/.config/claude/plugins/

Step 2: Enable the Plugin¶

Inside Claude Code CLI:

/plugin enable cms-cultivator

Updating Manual Installation¶

cd ~/.claude/plugins/cms-cultivator
git pull origin main

Then inside Claude Code CLI:

/plugin reload cms-cultivator

Method 4: Project-Specific Installation¶

Share plugins with your team by configuring them in your project repository. Installs per-project - only available in this specific project.

Step 1: Create .claude/settings.json¶

In your project root, create or edit .claude/settings.json:

{
  "extraKnownMarketplaces": [
    {
      "name": "claude-toolbox",
      "url": "https://github.com/kanopi/claude-toolbox"
    }
  ],
  "enabledPlugins": {
    "cms-cultivator@claude-toolbox": true
  }
}

Step 2: Commit to Repository¶

git add .claude/settings.json
git commit -m "Add CMS Cultivator plugin configuration"
git push

Team Member Setup¶

When team members clone the repository and trust the folder, Claude Code will automatically:

1. Add the Kanopi marketplace
2. Install CMS Cultivator
3. Enable the plugin for the project

Project-Specific Configuration¶

Team members can override project settings in .claude/settings.local.json (not committed to git):

{
  "enabledPlugins": {
    "cms-cultivator@claude-toolbox": false
  }
}

Claude Desktop¶

Claude Desktop has three surfaces, each with its own upload path:

The marketplace install (Method 1 above) only covers Claude Code in the standalone CLI. For Claude Code inside Desktop, plus Chat and CoWork, you upload zips through Claude Desktop's UI. Every CMS Cultivator GitHub release attaches pre-built artifacts for all three surfaces so you don't have to build them yourself.

Recommended: Download from a release¶

1. Go to the latest release
2. Under Assets, download what you need:
3. cms-cultivator.zip — full plugin zip for Claude Code inside Desktop. Upload via Settings → Plugins → Add plugin.
4. cms-cultivator-skills.zip — bundle of every skill for Chat/CoWork. Unzip locally to get the individual .skill files, then upload each via Settings → Skills → Upload Skill.
5. Individual <skill-name>.skill files — if you only want specific skills for Chat or CoWork.

Alternative: Build from source¶

If you've cloned the repo, package locally:

./scripts/package-plugin.sh   # → dist/cms-cultivator.zip
./scripts/package-skills.sh   # → dist/skills/<name>.skill + dist/cms-cultivator-skills.zip

package-plugin.sh options:

./scripts/package-plugin.sh         # archive HEAD
./scripts/package-plugin.sh v1.2.1  # archive a specific tag/ref/SHA

package-skills.sh options:

./scripts/package-skills.sh                  # all skills + bundle
./scripts/package-skills.sh frd-generator    # one skill only
./scripts/package-skills.sh --list           # print the skill names
./scripts/package-skills.sh --no-bundle      # skip the all-in-one zip

Why the manual step exists¶

The uploads themselves aren't automatable — Anthropic doesn't expose a Desktop plugin/skill API or a marketplace for Chat/CoWork skills today. The scripts and release artifacts only handle the packaging side. Once Anthropic ships either a Desktop API or marketplace integration for those surfaces, this section will get shorter.

OpenAI Codex Installation¶

CMS Cultivator includes a .codex-plugin/plugin.json manifest and Codex-compatible TOML agent files. Install it via the Codex plugin system.

Codex Method 1: Via Marketplace (Recommended)¶

Add the Kanopi marketplace and install from the Codex plugin browser.

Step 1: Add the Kanopi Marketplace¶

codex plugin marketplace add kanopi/claude-toolbox

Step 2: Open the Plugin Browser¶

codex/plugins

Browse to CMS Cultivator, open its details, and select Install plugin.

Step 3: Start a New Thread¶

After installation, start a new Codex thread. Skills activate automatically from context, or invoke explicitly with @skill-name (e.g. @pr-create).

Updating Via Marketplace¶

codex plugin marketplace upgrade

Codex Method 2: Personal Installation (Manual)¶

Install directly to your personal Codex plugins directory. Installs globally for all your projects.

Step 1: Clone the Repository¶

git clone https://github.com/kanopi/cms-cultivator ~/.codex/plugins/cms-cultivator

Step 2: Create a Personal Marketplace File¶

Create or update ~/.agents/plugins/marketplace.json:

{
  "name": "kanopi-plugins",
  "interface": {
    "displayName": "Kanopi Plugins"
  },
  "plugins": [
    {
      "name": "cms-cultivator",
      "source": {
        "source": "local",
        "path": "./cms-cultivator"
      },
      "policy": {
        "installation": "AVAILABLE",
        "authentication": "ON_INSTALL"
      },
      "category": "Development"
    }
  ]
}

Step 3: Restart Codex and Install¶

Restart Codex, then open codex/plugins, find CMS Cultivator under the Kanopi Plugins marketplace, and install it.

Updating Manual Installation¶

cd ~/.codex/plugins/cms-cultivator
git pull origin main

Then restart Codex to pick up the changes.

Codex Method 3: Repo-Scoped Installation¶

Share the plugin with your team by configuring it in your project repository. Installs per-project - only available in this specific project.

Step 1: Add the Plugin to Your Repo¶

git clone https://github.com/kanopi/cms-cultivator plugins/cms-cultivator

Or add it as a git submodule:

git submodule add https://github.com/kanopi/cms-cultivator plugins/cms-cultivator

Step 2: Create a Repo Marketplace File¶

Create $REPO_ROOT/.agents/plugins/marketplace.json:

{
  "name": "project-plugins",
  "plugins": [
    {
      "name": "cms-cultivator",
      "source": {
        "source": "local",
        "path": "./plugins/cms-cultivator"
      },
      "policy": {
        "installation": "AVAILABLE",
        "authentication": "ON_INSTALL"
      },
      "category": "Development"
    }
  ]
}

Step 3: Commit to Repository¶

git add .agents/plugins/marketplace.json plugins/cms-cultivator
git commit -m "Add CMS Cultivator plugin for Codex"
git push

Team Member Setup¶

When team members open the project in Codex, they run codex/plugins, find CMS Cultivator under the project marketplace, and install it.

Disabling the Codex Plugin¶

To keep the plugin installed but turn it off, edit ~/.codex/config.toml:

[plugins."cms-cultivator@kanopi-plugins"]
enabled = false

Then restart Codex.

Verifying Installation¶

Test a Skill¶

Claude Code — open in any project and try a skill by name or natural language:

/code-standards-checker

Codex — start a new thread and invoke explicitly or by natural language:

@code-standards-checker

Or just say: "Does this follow Drupal coding standards?" — skills activate automatically in conversation on both platforms.

List Available Skills¶

In Claude Code, type / to see all available skills. In Codex, type @ to see installed plugin skills. CMS Cultivator skills are organized by category:

• PR Workflow: /pr-create, /pr-review, /commit-message-generator, /pr-release
• Accessibility: /accessibility-audit (with flexible modes)
• Performance: /performance-audit (with flexible modes)
• Security: /security-audit (with flexible modes)
• Live Site Auditing: /live-site-audit (parallel multi-specialist audit)
• Design Workflow: /design-to-wp-block, /design-to-drupal-paragraph
• Testing: auto-invoked (say "I need tests for this class")
• Code Quality: /quality-audit, /code-standards-checker
• Documentation: auto-invoked (say "document this function")

Optional Dependencies¶

GitHub CLI (for PR Commands)¶

To use /pr-create and other PR commands:

brew install gh
gh auth login

# Debian/Ubuntu
sudo apt install gh

# Fedora/RHEL
sudo dnf install gh

gh auth login

winget install --id GitHub.cli
gh auth login

Lighthouse (for Performance Analysis)¶

For /performance-audit lighthouse:

npm install -g lighthouse

Configuration¶

Global Configuration¶

Global plugin settings are stored in: - Settings: ~/.claude/settings.json - Local overrides: ~/.claude/settings.local.json

Project Configuration¶

Project-specific settings: - Team settings: .claude/settings.json (committed to git) - Personal overrides: .claude/settings.local.json (gitignored)

Example .gitignore entry:

.claude/settings.local.json

Uninstalling¶

Remove from Marketplace¶

Inside Claude Code CLI:

/plugin uninstall cms-cultivator@claude-toolbox

Remove Manual Installation¶

Inside Claude Code CLI:

/plugin disable cms-cultivator

Then remove the files:

rm -rf ~/.claude/plugins/cms-cultivator

Remove from Project¶

Remove or edit .claude/settings.json in your project:

{
  "enabledPlugins": {
    "cms-cultivator@claude-toolbox": false
  }
}

Troubleshooting¶

Commands Not Showing Up¶

Inside Claude Code CLI:

# Check plugin status
/plugin

# Verify plugin is enabled
/plugin enable cms-cultivator

# Reload plugin
/plugin reload cms-cultivator

Marketplace Not Found¶

If the marketplace fails to load:

# Verify marketplace URL
curl https://raw.githubusercontent.com/kanopi/claude-toolbox/main/.claude-plugin/marketplace.json

Inside Claude Code CLI:

# Remove and re-add marketplace
/plugin marketplace remove claude-toolbox
/plugin marketplace add kanopi/claude-toolbox

Permission Denied¶

# Ensure the plugins directory exists
mkdir -p ~/.claude/plugins

# Check ownership
ls -la ~/.claude/plugins/

# Fix permissions if needed
chmod -R 755 ~/.claude/plugins/cms-cultivator

Plugin Not Loading¶

# Check for errors in plugin.json
cat ~/.claude/plugins/cms-cultivator/.claude-plugin/plugin.json

# Verify directory structure
ls ~/.claude/plugins/cms-cultivator/skills/

# Check plugin integrity
cd ~/.claude/plugins/cms-cultivator
git status

Project Settings Not Working (Claude Code)¶

1. Verify trust: Ensure the project folder is trusted in Claude Code
2. Check JSON syntax: Validate .claude/settings.json with a JSON linter
3. Restart Claude Code: Close and reopen Claude Code after changing settings
4. Check marketplace availability: Ensure extraKnownMarketplaces is configured correctly

Codex Plugin Not Appearing¶

1. Verify marketplace file: Check that marketplace.json is valid JSON and source.path is correct
2. Restart Codex: Codex reads marketplace files on startup
3. Check config: Verify ~/.codex/config.toml doesn't have the plugin set to enabled = false

Kanopi Projects Setup¶

If you're working on Kanopi projects with DDEV add-ons, see the Kanopi Tools guide for additional integration features:

• Composer Scripts: ddev composer code-check, phpstan, rector-check
• DDEV Commands: ddev theme-build, ddev cypress-run, ddev critical-run
• Database Tools: ddev db-refresh, ddev db-backup

Migrating from Pre-v1.0 Names¶

Before v1.0, CMS Cultivator used a commands/ directory with slash-command names. v1.0 moved entirely to skills and renamed everything. If you have muscle memory or stale docs referencing old names, here are the most common changes:

• /audit-a11y → /accessibility-audit
• /audit-perf → /performance-audit
• /audit-security → /security-audit
• /quality-analyze → /quality-audit
• /pr-commit-msg → /commit-message-generator
• /docs-generate → /documentation-generator
• /test-generate → /test-scaffolding
• /test-plan → /test-plan-generator
• /audit-live-site → /live-site-audit
• /design-to-block → /design-to-wp-block
• /design-to-paragraph → /design-to-drupal-paragraph

No aliases are registered for the old names — invoking a pre-v1.0 name produces no result. You can also just describe what you want in natural language; the right skill will activate automatically.

For the complete mapping and the rationale behind the renaming, see the Skill Naming Convention reference page.

Next Steps¶

• Quick Start Guide - Learn common workflows
• Skills Overview - Explore all available skills
• Skill Naming Convention - Why skills are named the way they are
• Kanopi Tools - Integrate with DDEV add-ons
• Contributing - Contribute to the project

Installation Support: - Issues: GitHub Issues - Marketplace: Claude Toolbox