Create Plugin

When to use

Steps

1. Get plugin name and description from the user
2. Check for conflicts — call

   mcp__claude-flow__transfer_plugin-search

   to ensure the name isn't taken
3. Create directory structure:

   plugins/<name>/
   ├── .claude-plugin/
   │   └── plugin.json
   ├── skills/
   │   └── <skill-name>/
   │       └── SKILL.md
   ├── commands/
   │   └── <command-name>.md
   ├── agents/
   │   └── <agent-name>.md
   └── README.md

4. Generate plugin.json with name, description, version, author (do NOT include

   skills

   ,

   commands

   , or

   agents

   arrays — Claude Code auto-discovers these from directory structure)
5. Generate SKILL.md files with proper frontmatter:
   yaml

   ---
   name: skill-name
   description: What this skill does
   allowed-tools: mcp__claude-flow__tool1 mcp__claude-flow__tool2 Bash
   ---

6. Generate command files with name and description frontmatter
7. Generate agent files with name, description, and

   model: sonnet

8. Generate README.md with install instructions, features, commands, and skills
9. Update marketplace.json if adding to the ruflo marketplace

Plugin.json schema

• name

  — plugin identifier (kebab-case)

• description

  — what the plugin does

• version

  — semver

• author

  —

  { "name": "...", "url": "..." }

• homepage

  ,

  license

  ,

  keywords

skills

commands

agents

Available MCP tools to wire

mcp__claude-flow__transfer_plugin-info

• memory_*

  — storage, search, retrieval

• agentdb_*

  — 19 AgentDB controllers

• neural_*

  — neural training and prediction

• hooks_*

  — lifecycle hooks and intelligence

• browser_*

  — browser automation

• workflow_*

  — workflow management

• aidefence_*

  — safety scanning

• embeddings_*

  — vector embeddings