agentleFS
alexsmedilealexsmedile/hormozi-skills/skills/create-plugin/SKILL.md

create-plugin

Skill208 starsChanged 3 months agoMITView on GitHub

This skill should be used when the user asks to "create a plugin", "make a GitHub plugin", "turn my repo into a plugin", "create a Claude Code plugin", "create a Codex plugin", "publish my skills as a plugin", or "set up a plugin marketplace". Scaffolds the complete file structure for a repo that works as both a Claude Code and Codex plugin with marketplace support.

  • Commits and pushes

14 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 12 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask the user these questions (all at once):

    line 16
  2. Distinctive:

    Do not proceed until you have at least: repo name, GitHub username, description, and author name.

    line 29

“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Skill: Plugin Creator (Claude Code + Codex)

Purpose

Scaffold a GitHub repo that works as a plugin for both Claude Code and Codex simultaneously. Outputs ready-to-copy file contents and git commands for every required file.


Step 1: Gather Inputs

Ask the user these questions (all at once):

  1. Repo name — kebab-case (e.g. my-skills)
  2. GitHub username or org — (e.g. alexsmedile)
  3. Plugin description — one sentence
  4. Author name
  5. What does this plugin contain? — pick all that apply:
    • Skills (skills/)
    • Agents (agents/)
    • Hooks (hooks/hooks.json)
    • MCP servers (.mcp.json)
  6. License — default: MIT

Do not proceed until you have at least: repo name, GitHub username, description, and author name.


Step 2: Generate File Structure

Show the full directory tree based on their selections, then output every file's content ready to copy.

Always-required files

.claude-plugin/plugin.json

{
  "name": "{{repo-name}}",
  "version": "1.0.0",
  "description": "{{description}}",
  "author": {
    "name": "{{author}}"
  },
  "homepage": "https://github.com/{{username}}/{{repo-name}}",
  "repository": "https://github.com/{{username}}/{{repo-name}}",
  "license": "{{license}}",
  "keywords": []
}

Skills and agents in skills/ and agents/ are auto-discovered — no paths needed in plugin.json.

.claude-plugin/marketplace.json

{
  "name": "{{repo-name}}",
  "owner": {
    "name": "{{author}}"
  },
  "metadata": {
    "description": "{{description}}",
    "version": "1.0.0"
  },
  "plugins": [
    {
      "name": "{{repo-name}}",
      "source": "./",
      "description": "{{description}}",
      "version": "1.0.0",
      "author": {
        "name": "{{author}}"
      },
      "homepage": "https://github.com/{{username}}/{{repo-name}}",
      "repository": "https://github.com/{{username}}/{{repo-name}}",
      "license": "{{license}}",
      "category": "productivity"
    }
  ]
}

.codex-plugin/plugin.json

{
  "name": "{{repo-name}}",
  "version": "1.0.0",
  "description": "{{description}}",
  "author": {
    "name": "{{author}}"
  },
  "homepage": "https://github.com/{{username}}/{{repo-name}}",
  "repository": "https://github.com/{{username}}/{{repo-name}}",
  "license": "{{license}}",
  "skills": "./skills/"
}

.codex-plugin/marketplace.json

{
  "name": "{{repo-name}}",
  "interface": {
    "displayName": "{{repo-name}}"
  },
  "plugins": [
    {
      "name": "{{repo-name}}",
      "source": {
        "source": "local",
        "path": "./"
      },
      "category": "Productivity"
    }
  ]
}

.gitignore

.DS_Store
**/.DS_Store
output/*
!output/.gitkeep

output/.gitkeep

Empty file — keeps the output/ folder tracked by git.


If skills selected: skills/example-skill/SKILL.md

---
name: example-skill
description: Replace this description with specific trigger phrases. Use when the user asks to "..."
---

# Skill: Example

Describe what this skill does and how to use it.

Rename example-skill/ to your actual skill name. Skill is invoked as /{{repo-name}}:example-skill.


If agents selected: agents/example-agent.md

---
name: example-agent
description: Replace with what this agent does and when to invoke it.
tools: Read, Write, Bash
model: sonnet
---

# Agent: Example

Describe the agent's role, expertise, and behavior here.

Rename to your actual agent name.


If hooks selected: hooks/hooks.json

{
  "hooks": {
    "PostToolUse": [
      {
        "matcher": "Write|Edit",
        "hooks": [
          {
            "type": "command",
            "command": "echo 'File changed'"
          }
        ]
      }
    ]
  }
}

If MCP servers selected: .mcp.json

{
  "mcpServers": {
    "example-server": {
      "command": "${CLAUDE_PLUGIN_ROOT}/bin/server",
      "args": []
    }
  }
}

Step 3: Critical Rules

State these clearly before the user creates any files:

RuleDetail
skills/ and agents/ at repo rootNever inside .claude-plugin/ or .codex-plugin/
Plugin name = skill namespacePlugin foo → skills run as /foo:skill-name
plugin.json is auto-discoveryNo need to list skills or agents paths unless using custom locations
Do NOT add skills/agents to marketplace.jsonCauses schema validation error with default strict: true
source: "./" in marketplace.jsonPoints at repo root — correct for single-plugin repos

Step 4: Git Setup + Install Commands

Output these exactly, substituting the user's values:

# Create repo (if not exists)
gh repo create {{username}}/{{repo-name}} --public

# Init and push
git init
git add .
git commit -m "feat: initial plugin scaffold"
git remote add origin https://github.com/{{username}}/{{repo-name}}.git
git push -u origin main

Install in Claude Code:

/plugin marketplace add {{username}}/{{repo-name}}
/plugin install {{repo-name}}@{{repo-name}}

Reload after changes:

/reload-plugins

Test locally without installing:

claude --plugin-dir ./

Step 5: After Install

Skills are namespaced: /{{repo-name}}:skill-name
Agents appear in /agents

To update: push to GitHub, then /plugin marketplace update {{repo-name}}

Bump version in plugin.json and marketplace.json with each release — Claude Code uses version to detect updates.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.