Agent skill

Plugin Creator

by softspark in softspark/ai-toolkit

Creates opt-in plugin packs with manifests + module scaffolding for Claude/Codex.

Apache-2.0Auto-check: notesAgent Workflows

Install Plugin Creator

skills CLI
$ npx skills add softspark/ai-toolkit --skill plugin-creator -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install softspark/ai-toolkit plugin-creator --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/softspark/ai-toolkit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/app/skills/plugin-creator .claude/skills/plugin-creator && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
plugin-creator
GitHub stars
179
Token cost
~1.4k tokens
SKILL.md length
618 words
Files
1
Skills in repo
112
Repo updated
First seen
Licence
Apache-2.0

At a glance

Creates opt-in plugin packs with manifests + module scaffolding for Claude/Codex.

  • Works in 6 steps: Capture scope -- what domain should the… → Pick packaging model -- domain pack,… → Define manifest -- name, description,… → …
  • Tasks that involve Hooks and plugins
  • SKILL.md covers Workflow, Directory Layout, Manifest Template and Authoring Rules, plus 3 more sections
  • Calls jq

What it does

Plugin Creator is an agent skill from softspark/ai-toolkit. Creates opt-in plugin packs with manifests + module scaffolding for Claude/Codex. Triggers: new plugin, plugin pack, plugin scaffold.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering Hooks and plugins and Project scaffolding. The repository describes itself as: Professional-grade AI coding toolkit: 94 skills, 44 agents, multi-platform (Claude, Cursor, Windsurf, Copilot, Gemini, Cline, Roo Code, Aider, Augment, Antigravity, Codex CLI… The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Hooks and plugins
  • Tasks that involve Project scaffolding

Example prompts

  • “Use the plugin-creator skill to create opt-in plugin packs with manifests + module scaffolding for Claude/Codex”
  • “/plugin-creator”

Requirements

  • Pre-approved tools (allowed-tools): Read, Write, Edit, Bash, Grep, Glob

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Capture scope -- what domain should the plugin pack own?
  2. Pick packaging model -- domain pack, policy pack, or hook/observability pack?
  3. Define manifest -- name, description, version, domain, compatibility, included assets
  4. Select assets -- agents, skills, rules, hooks, docs, templates
  5. Add scaffolding -- create plugin.json, README.md, and optional subdirectories
  6. Validate -- manifest JSON, included asset references, executable hooks, documentation links

What it can do on your machine

Read from SKILL.md and the folder at commit d64db2b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Bash
    • Grep
    • Glob

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • jq

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Plugin Creator loads about 1.4k tokens when it runs. Until then it costs about 37 tokens; SKILL.md has 618 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~37
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Write, Edit, Bash, Grep, Glob

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from softspark/ai-toolkit at commit d64db2b, republished under its Apache-2.0 licence (© softspark). 618 words, ~1,394 tokens.

Download SKILL.mdSave it as .claude/skills/plugin-creator/SKILL.md (or your agent's skills folder).
name
plugin-creator
description
Creates opt-in plugin packs with manifests + module scaffolding for Claude/Codex. Triggers: new plugin, plugin pack, plugin scaffold.
allowed-tools
Read, Write, Edit, Bash, Grep, Glob
effort
high
disable-model-invocation
true
argument-hint
[plugin pack name or domain]

Plugin Creator

$ARGUMENTS

Create a new experimental opt-in plugin pack following ai-toolkit conventions.

Workflow

  1. Capture scope -- what domain should the plugin pack own?
  2. Pick packaging model -- domain pack, policy pack, or hook/observability pack?
  3. Define manifest -- name, description, version, domain, compatibility, included assets
  4. Select assets -- agents, skills, rules, hooks, docs, templates
  5. Add scaffolding -- create plugin.json, README.md, and optional subdirectories
  6. Validate -- manifest JSON, included asset references, executable hooks, documentation links

Directory Layout

text
app/plugins/<plugin-name>/
├── plugin.json
├── README.md
├── agents/           # optional
├── skills/           # optional
├── hooks/            # optional
├── rules/            # optional
└── templates/        # optional

Manifest Template

json
{
  "name": "memory-pack",
  "description": "Domain plugin pack for persistent cross-session memory.",
  "version": "1.0.0",
  "domain": "memory",
  "type": "plugin-pack",
  "status": "experimental",
  "requires": {
    "ai-toolkit": ">=1.0.0",
    "claude-code": ">=1.0.33"
  },
  "includes": {
    "agents": [],
    "skills": ["mem-search"],
    "rules": [],
    "hooks": ["observation-capture.sh", "session-summary.sh"]
  },
  "hook_events": {
    "observation-capture.sh": "PostToolUse",
    "session-summary.sh": "Stop"
  }
}

The two hooks are files the pack owns, under app/plugins/memory-pack/hooks/. That is what makes this a pack rather than a bookmark: installing it puts scripts on disk and entries in the host's hook config that were not there before.

Authoring Rules

  • MUST keep packs domain-scoped — "memory-pack", "mobile-pack", not "misc-pack"
  • MUST install something the core install does not already provide. ai-toolkit install links every core skill and agent, so a pack whose includes names only core assets installs zero files and is a no-op. Verify before shipping: install core into a throwaway HOME, then install the pack, and confirm the file count changed. Nine packs were removed in v4.20.0 for failing exactly this check.
  • MUST reference existing toolkit assets rather than forking them — but referencing alone is not a pack. A pack earns its existence through hooks, scripts, or assets of its own; the reference list is context, not content.
  • MUST ship a valid plugin.json with name, description, version, domain, type, status, and includes
  • NEVER have a pack silently alter default global install behavior — experimental packs are opt-in only
  • NEVER copy an agent or skill file into a pack when referencing the toolkit-level version suffices; duplication creates drift
  • CRITICAL: optional hooks bundled in a pack must be executable (chmod +x) and documented in the pack README with their install semantics
  • MANDATORY: the pack README names supported runtimes (claude, codex, or all) and explains that the pack is not part of the default install
Show full SKILL.md (298 more words)Show less

Gotchas

  • Plugin packs are discovered by scanning app/plugins/*/plugin.json. A pack with a missing or malformed plugin.json is silently ignored — no error surfaces. Check with ls app/plugins/*/plugin.json and jq . app/plugins/*/plugin.json.
  • The status: experimental flag gates visibility in some install paths — marking a pack "stable" before it is audited can make it install by default for every user. Keep experimental until the pack has eaten its own dogfood.
  • Packs that include hooks inherit the toolkit's hook merge rules (_source: "ai-toolkit"). Hooks without the _source tag survive ai-toolkit update and can leak into other packs' merge pools.
  • Versions in plugin.json are separate from the toolkit version. A pack at v1.2 running inside toolkit v2.11 may still satisfy requires.ai-toolkit: >=1.0.0 but mean nothing about actual compatibility — test against the current toolkit before tagging.
  • Codex-runtime packs need matching .agents/rules/ and .codex/hooks.json variants; a plugin that only ships Claude assets looks broken under Codex CLI. Declare runtime support explicitly.

Validation Checklist

  • app/plugins/<plugin-name>/plugin.json exists and parses as JSON
  • The pack installs a non-zero number of files. ai-toolkit install into a throwaway HOME, then plugin install <name>, and confirm the reported file count is above zero on every runtime the pack claims. A pack reporting (0 file items) does nothing and must not ship.
  • README.md explains purpose, included assets, and opt-in flow
  • Referenced agents and skills exist or are created in the same change set
  • Optional hooks are executable and use #!/bin/bash
  • scripts/validate.py passes
  • Public docs mention the pack only after the manifest and README exist

When NOT to Use

  • For an individual skill (slash command or knowledge doc) — use /skill-creator
  • For an individual agent — use /agent-creator
  • For a single hook (not a pack) — use /hook-creator
  • For an MCP server — use /mcp-builder
  • For modifying an existing plugin pack — edit its files directly; this skill is create-only

© softspark, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in app/skills/plugin-creator of softspark/ai-toolkit.

Open the folder on GitHubat commit d64db2b

Compare with similar skills

Plugin Creator next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Plugin Creator compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Plugin Creator this skillsoftspark/ai-toolkit179—~1.4kAutomated safety check: NotesApache-2.0
Claude Code Plugin Structureanthropics/claude-plugins-official38k10 repos~3.4kAutomated safety check: PassApache-2.0
Writing Pluginsnukeop/nuclear19k—~825Automated safety check: PassAGPL-3.0
OpenCode Plugin CreatorDevin-AXIS/iPolloWork6.8k1 repos~1.3kAutomated safety check: PassCustom licence
Create Harnessruvnet/metaharness690—~777Automated safety check: PassMIT
Claude Code Plugin Developmentobra/superpowers-developing-for-claude-code142—~2.2kAutomated safety check: PassNone

Similar skills

  • Claude Code Plugin Structure

    anthropics/claude-plugins-official

    Official

    Explains the directory layout, plugin.json manifest and component organization of a Claude Code plugin, including auto-discovery and portable paths.

    38k GitHub starsUsed in 10 repos~3.4k tokens
    Agent WorkflowsAuto-check passed
  • Writing Plugins

    nukeop/nuclear

    A skill your agent uses when writing, scaffolding, or modifying Nuclear plugins.

    19k GitHub stars~825 tokensUpdated 2 days ago
    Agent WorkflowsAuto-check passed
  • OpenCode Plugin Creator

    Devin-AXIS/iPolloWork

    Scaffolds an OpenCode plugin for iPolloWork with the right async factory shape, zod-based tool definitions and hook registration, and explains where to place and register it.

    6.8k GitHub starsUsed in 1 repo~1.3k tokens
    Agent WorkflowsAuto-check passed
  • Create Harness

    ruvnet/metaharness

    Scaffold your own focused AI agent harness — pick host (Claude Code, Codex, pi.dev, Hermes), template, agents, skills, and ship a npm-publishable harness with its own npx CLI.

    690 GitHub stars~777 tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Claude Code Plugin Development

    obra/superpowers-developing-for-claude-code

    Workflows, patterns and examples for the whole Claude Code plugin lifecycle: creating, adding components, testing, troubleshooting, releasing and maintaining plugins.

    142 GitHub stars~2.2k tokensUpdated 10 mo ago
    Agent WorkflowsAuto-check passed
  • Hana Plugin Creator

    ZS520L/HanakoPro

    Create Hana plugin scaffolds and guide users through beginner or developer plugin planning, capability checks, manifest setup, runtime tools, iframe UI, SDK templates, and install-ready plugin…

    102 GitHub stars~2.6k tokensUpdated 4 mo ago
    Agent WorkflowsAuto-check passed

More from softspark/ai-toolkit

All 112 skills in this repo
  • Prepare Test Env

    softspark/ai-toolkit

    Prepare or verify a project QA environment with source identity, readiness, browser access, evidence paths and owned cleanup.

    179 GitHub stars~1.8k tokensUpdated yesterday
    Auto-check: notes
  • A11y Validate

    softspark/ai-toolkit

    Accessibility validator: WCAG 2.1 AA, EN 301 549, EAA. An agent skill from softspark/ai-toolkit.

    179 GitHub stars~3.8k tokensUpdated yesterday
    Auto-check: notes
  • Analyze

    softspark/ai-toolkit

    Analyzes code quality, complexity, patterns across codebase.

    179 GitHub stars~1k tokensUpdated yesterday
    Auto-check passed
  • Autonomous Dev

    softspark/ai-toolkit

    Drives a brief, specification, issue or existing PR through implementation, review, tests and QA to a ready PR.

    179 GitHub stars~2.6k tokensUpdated yesterday
    Auto-check: notes
  • Brand Voice

    softspark/ai-toolkit

    Direct technical voice for docs, README, user-facing text. An agent skill from softspark/ai-toolkit.

    179 GitHub stars~2.1k tokensUpdated yesterday
    Auto-check passed
  • CI

    softspark/ai-toolkit

    Detect/generate/debug CI pipeline config (GitHub Actions, GitLab CI).

    179 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check: notes

Questions about Plugin Creator

What does Plugin Creator do?

Creates opt-in plugin packs with manifests + module scaffolding for Claude/Codex. Plugin Creator is an agent skill from softspark/ai-toolkit. Creates opt-in plugin packs with manifests + module scaffolding for Claude/Codex.

When should I use Plugin Creator?

Plugin Creator fits situations like: tasks that involve Hooks and plugins; tasks that involve Project scaffolding.

How do I install Plugin Creator in Claude Code?

Run `npx skills add softspark/ai-toolkit --skill plugin-creator -a claude-code`. Or copy the skill folder (app/skills/plugin-creator in softspark/ai-toolkit) into .claude/skills/plugin-creator in your project. Claude Code loads it when a task matches its description.

How do I install Plugin Creator in Codex?

Run `npx skills add softspark/ai-toolkit --skill plugin-creator -a codex`. Or copy the skill folder (app/skills/plugin-creator in softspark/ai-toolkit) into .agents/skills/plugin-creator in your project. Codex loads it when a task matches its description.

Can I use Plugin Creator in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add softspark/ai-toolkit --skill plugin-creator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/plugin-creator, .gemini/skills/plugin-creator, .github/skills/plugin-creator and .opencode/skills/plugin-creator in your project.

What does Plugin Creator need to run?

Going by SKILL.md and its folder, Plugin Creator needs the command-line tools its instructions call (jq). Its frontmatter pre-approves these tools: Read, Write, Edit, Bash, Grep, Glob.

Does Plugin Creator access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Plugin Creator safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Plugin Creator use?

Plugin Creator is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Plugin Creator use?

About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Plugin Creator?

Skills that share tags, products or a category with Plugin Creator: Claude Code Plugin Structure (anthropics/claude-plugins-official, 38k stars), Writing Plugins (nukeop/nuclear, 19k stars), OpenCode Plugin Creator (Devin-AXIS/iPolloWork, 6.8k stars) and Create Harness (ruvnet/metaharness, 690 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Plugin Creator?

softspark (a GitHub user) maintains it in softspark/ai-toolkit, which has 179 GitHub stars. The repository holds 112 skills in this directory. The repository was last updated on October 7, 2026.

Source: softspark/ai-toolkit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.