Agent skill

Plugin Creator

by lingxling in lingxling/awesome-skills-cn

Create and scaffold plugin directories for Codex with a required .codex-plugin/plugin.json, optional plugin folders/files, and baseline placeholders you can edit before publishing or testing.

Apache-2.0Auto-check passedAgent Workflows

Install Plugin Creator

skills CLI

$ npx skills add lingxling/awesome-skills-cn --skill plugin-creator -a claude-code

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

GitHub CLI

$ gh skill install lingxling/awesome-skills-cn 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/lingxling/awesome-skills-cn.git skills-src && mkdir -p .claude/skills && cp -r skills-src/openai-skills/skills/.system/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/

Paste into Claude Code

Install the "plugin-creator" agent skill from https://github.com/lingxling/awesome-skills-cn/tree/main/openai-skills/skills/.system/plugin-creator into .claude/skills/plugin-creator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-creator", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/lingxling/awesome-skills-cn/tree/main/openai-skills/skills/.system/plugin-creator

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add lingxling/awesome-skills-cn --skill plugin-creator -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install lingxling/awesome-skills-cn plugin-creator --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/lingxling/awesome-skills-cn.git skills-src && mkdir -p .agents/skills && cp -r skills-src/openai-skills/skills/.system/plugin-creator .agents/skills/plugin-creator && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "plugin-creator" agent skill from https://github.com/lingxling/awesome-skills-cn/tree/main/openai-skills/skills/.system/plugin-creator into .agents/skills/plugin-creator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-creator", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add lingxling/awesome-skills-cn --skill plugin-creator -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install lingxling/awesome-skills-cn plugin-creator --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/lingxling/awesome-skills-cn.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/openai-skills/skills/.system/plugin-creator .cursor/skills/plugin-creator && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "plugin-creator" agent skill from https://github.com/lingxling/awesome-skills-cn/tree/main/openai-skills/skills/.system/plugin-creator into .cursor/skills/plugin-creator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-creator", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/lingxling/awesome-skills-cn.git --path openai-skills/skills/.system/plugin-creator

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add lingxling/awesome-skills-cn --skill plugin-creator -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install lingxling/awesome-skills-cn plugin-creator --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/lingxling/awesome-skills-cn.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/openai-skills/skills/.system/plugin-creator .gemini/skills/plugin-creator && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "plugin-creator" agent skill from https://github.com/lingxling/awesome-skills-cn/tree/main/openai-skills/skills/.system/plugin-creator into .gemini/skills/plugin-creator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-creator", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install lingxling/awesome-skills-cn plugin-creator

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add lingxling/awesome-skills-cn --skill plugin-creator -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/lingxling/awesome-skills-cn.git skills-src && mkdir -p .github/skills && cp -r skills-src/openai-skills/skills/.system/plugin-creator .github/skills/plugin-creator && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "plugin-creator" agent skill from https://github.com/lingxling/awesome-skills-cn/tree/main/openai-skills/skills/.system/plugin-creator into .github/skills/plugin-creator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-creator", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add lingxling/awesome-skills-cn --skill plugin-creator -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install lingxling/awesome-skills-cn plugin-creator --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/lingxling/awesome-skills-cn.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/openai-skills/skills/.system/plugin-creator .opencode/skills/plugin-creator && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "plugin-creator" agent skill from https://github.com/lingxling/awesome-skills-cn/tree/main/openai-skills/skills/.system/plugin-creator into .opencode/skills/plugin-creator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-creator", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: plugin-creator
GitHub stars: 299
Token cost: ~1.6k tokens
SKILL.md length: 478 words
Files: 6 (incl. scripts, references)
Skills in repo: 3
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Create and scaffold plugin directories for Codex with a required .codex-plugin/plugin.json, optional plugin folders/files, and baseline placeholders you can edit before publishing or testing.

Works in 3 steps: Run the scaffold script → Open /.codex-plugin/plugin.json and… → Generate or update the repo marketplace…
Codex needs to create a new local plugin
SKILL.md covers Quick Start, What this skill creates, Marketplace workflow and Required behavior, plus 2 more sections
Runs Python scripts from its folder; calls python3

What it does

Plugin Creator is an agent skill from lingxling/awesome-skills-cn. Create and scaffold plugin directories for Codex with a required .codex-plugin/plugin.json, optional plugin folders/files, and baseline placeholders you can edit before publishing or testing. Use when Codex needs to create a new local plugin, add optional plugin structure, or generate or update repo-root .agents/plugins/marketplace.json entries for plugin ordering and availability metadata.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including scripts and reference files (for example `SKILL_CN.md`, `agents/openai.yaml` and `references/plugin-json-spec.md`).

It sits in Agent Workflows, covering Hooks and plugins. The repository describes itself as: 热门Skills中文cn学习版+教程，提供7000+Skills，集成claude skills (11w+Star) | awesome-openclaw-skills (4w+Star) | ui-ux-pro-max-skill (4w+Star)等10余个热门Skill项目. The licence is Apache-2.0.

When your agent uses it

Codex needs to create a new local plugin
Add optional plugin structure
Update repo-root .agents/plugins/marketplace.json entries for plugin ordering and availability metadata

Example prompts

“/plugin-creator”

Requirements

Python 3

Workflow steps

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

Run the scaffold script
Open /.codex-plugin/plugin.json and replace [TODO: ...] placeholders.
Generate or update the repo marketplace entry when the plugin should appear in Codex UI ordering

What it can do on your machine

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

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
- python3
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.6k tokens when it runs, and up to ~3.4k if it reads all its reference files. Until then it costs about 103 tokens; SKILL.md has 478 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~103
When it runs · the whole SKILL.md, loaded when a task matches: ~1.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~3.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 passed

The automated check found no risky patterns in SKILL.md.

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); the scripts in this folder are not scanned.

SKILL.md

The full file from lingxling/awesome-skills-cn at commit 68105dd, republished under its Apache-2.0 licence (© lingxling). 478 words, ~1,595 tokens.

Download SKILL.mdSave it as .claude/skills/plugin-creator/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.

name: plugin-creator
description: Create and scaffold plugin directories for Codex with a required `.codex-plugin/plugin.json`, optional plugin folders/files, and baseline placeholders you can edit before publishing or testing. Use when Codex needs to create a new local plugin, add optional plugin structure, or generate or update repo-root `.agents/plugins/marketplace.json` entries for plugin ordering and availability metadata.

Plugin Creator

Quick Start

Run the scaffold script:

bash

  # Plugin names are normalized to lower-case hyphen-case and must be <= 64 chars.
  # The generated folder and plugin.json name are always the same.
# Run from repo root (or replace .agents/... with the absolute path to this SKILL).
# By default creates in <repo_root>/plugins/<plugin-name>.
python3 .agents/skills/plugin-creator/scripts/create_basic_plugin.py <plugin-name>

Open <plugin-path>/.codex-plugin/plugin.json and replace [TODO: ...] placeholders.
Generate or update the repo marketplace entry when the plugin should appear in Codex UI ordering:

bash

# marketplace.json always lives at <repo-root>/.agents/plugins/marketplace.json
python3 .agents/skills/plugin-creator/scripts/create_basic_plugin.py my-plugin --with-marketplace

For a home-local plugin, treat <home> as the root and use:

bash

python3 .agents/skills/plugin-creator/scripts/create_basic_plugin.py my-plugin \
  --path ~/plugins \
  --marketplace-path ~/.agents/plugins/marketplace.json \
  --with-marketplace

Generate/adjust optional companion folders as needed:

bash

python3 .agents/skills/plugin-creator/scripts/create_basic_plugin.py my-plugin --path <parent-plugin-directory> \
  --with-skills --with-hooks --with-scripts --with-assets --with-mcp --with-apps --with-marketplace

<parent-plugin-directory> is the directory where the plugin folder <plugin-name> will be created (for example ~/code/plugins).

What this skill creates

If the user has not made the plugin location explicit, ask whether they want a repo-local plugin or a home-local plugin before generating marketplace entries.
Creates plugin root at /<parent-plugin-directory>/<plugin-name>/.
Always creates /<parent-plugin-directory>/<plugin-name>/.codex-plugin/plugin.json.
Fills the manifest with the full schema shape, placeholder values, and the complete interface section.
Creates or updates <repo-root>/.agents/plugins/marketplace.json when --with-marketplace is set.
- If the marketplace file does not exist yet, seed top-level name plus interface.displayName placeholders before adding the first plugin entry.
<plugin-name> is normalized using skill-creator naming rules:
- My Plugin → my-plugin
- My--Plugin → my-plugin
- underscores, spaces, and punctuation are converted to -
- result is lower-case hyphen-delimited with consecutive hyphens collapsed
Supports optional creation of:
- skills/
- hooks/
- scripts/
- assets/
- .mcp.json
- .app.json

Marketplace workflow

marketplace.json always lives at <repo-root>/.agents/plugins/marketplace.json.
For a home-local plugin, use the same convention with <home> as the root: ~/.agents/plugins/marketplace.json plus ./plugins/<plugin-name>.
Marketplace root metadata supports top-level name plus optional interface.displayName.
Treat plugin order in plugins[] as render order in Codex. Append new entries unless a user explicitly asks to reorder the list.
displayName belongs inside the marketplace interface object, not individual plugins[] entries.
Each generated marketplace entry must include all of:
- policy.installation
- policy.authentication
- category
Default new entries to:
- policy.installation: "AVAILABLE"
- policy.authentication: "ON_INSTALL"
Override defaults only when the user explicitly specifies another allowed value.
Allowed policy.installation values:
- NOT_AVAILABLE
- AVAILABLE
- INSTALLED_BY_DEFAULT
Allowed policy.authentication values:
- ON_INSTALL
- ON_USE
Treat policy.products as an override. Omit it unless the user explicitly requests product gating.
The generated plugin entry shape is:

Show full SKILL.md (169 more words)Show less

json

{
  "name": "plugin-name",
  "source": {
    "source": "local",
    "path": "./plugins/plugin-name"
  },
  "policy": {
    "installation": "AVAILABLE",
    "authentication": "ON_INSTALL"
  },
  "category": "Productivity"
}

Use --force only when intentionally replacing an existing marketplace entry for the same plugin name.
If <repo-root>/.agents/plugins/marketplace.json does not exist yet, create it with top-level "name", an "interface" object containing "displayName", and a plugins array, then add the new entry.
For a brand-new marketplace file, the root object should look like:

json

{
  "name": "[TODO: marketplace-name]",
  "interface": {
    "displayName": "[TODO: Marketplace Display Name]"
  },
  "plugins": [
    {
      "name": "plugin-name",
      "source": {
        "source": "local",
        "path": "./plugins/plugin-name"
      },
      "policy": {
        "installation": "AVAILABLE",
        "authentication": "ON_INSTALL"
      },
      "category": "Productivity"
    }
  ]
}

Required behavior

Outer folder name and plugin.json "name" are always the same normalized plugin name.
Do not remove required structure; keep .codex-plugin/plugin.json present.
Keep manifest values as placeholders until a human or follow-up step explicitly fills them.
If creating files inside an existing plugin path, use --force only when overwrite is intentional.
Preserve any existing marketplace interface.displayName.
When generating marketplace entries, always write policy.installation, policy.authentication, and category even if their values are defaults.
Add policy.products only when the user explicitly asks for that override.
Keep marketplace source.path relative to repo root as ./plugins/<plugin-name>.

Reference to exact spec sample

For the exact canonical sample JSON for both plugin manifests and marketplace entries, use:

references/plugin-json-spec.md

Validation

After editing SKILL.md, run:

bash

python3 <path-to-skill-creator>/scripts/quick_validate.py .agents/skills/plugin-creator

Files

SKILL.md and 5 other files (scripts, references) in openai-skills/skills/.system/plugin-creator of lingxling/awesome-skills-cn.

SKILL.md
LICENSE.txt
SKILL_CN.md
agents/openai.yaml
references/plugin-json-spec.md
scripts/create_basic_plugin.py

Open the folder on GitHubat commit 68105dd

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
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Plugin Creator this skilllingxling/awesome-skills-cn	299	—	~1.6k	Automated safety check: Pass	Apache-2.0	today
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official	37k	11 repos	~4.1k	Automated safety check: Notes	Apache-2.0	today
Claude Code Agent Developmentanthropics/claude-plugins-official	37k	8 repos	~2.8k	Automated safety check: Pass	Apache-2.0	today
Claude Code Skill Developer Guidediet103/claude-code-infrastructure-showcase	10k	10 repos	~3.5k	Automated safety check: Pass	MIT	2 mo ago
Plugin Settings Patternanthropics/claude-plugins-official	37k	7 repos	~3k	Automated safety check: Pass	Apache-2.0	today
MCP Integration for Pluginsanthropics/claude-plugins-official	37k	11 repos	~3.1k	Automated safety check: Pass	Apache-2.0	today

Similar skills

Hook Development for Claude Code Plugins
anthropics/claude-plugins-official
Official
Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.
37k GitHub starsUsed in 11 repos~4.1k tokens
Agent WorkflowsAuto-check: notes
Claude Code Agent Development
anthropics/claude-plugins-official
Official
Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.
37k GitHub starsUsed in 8 repos~2.8k tokens
Agent WorkflowsAuto-check passed
Claude Code Skill Developer Guide
diet103/claude-code-infrastructure-showcase
A guide to creating and managing Claude Code skills with auto-activation: skill-rules.json triggers, hooks, enforcement levels, YAML frontmatter and progressive disclosure.
10k GitHub starsUsed in 10 repos~3.5k tokens
Agent WorkflowsAuto-check passed
Plugin Settings Pattern
anthropics/claude-plugins-official
Official
Shows how Claude Code plugins keep per-project settings and state in .claude/plugin-name.local.md files with YAML frontmatter and a markdown body.
37k GitHub starsUsed in 7 repos~3k tokens
Agent WorkflowsAuto-check passed
MCP Integration for Plugins
anthropics/claude-plugins-official
Official
Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.
37k GitHub starsUsed in 11 repos~3.1k tokens
Agent WorkflowsAuto-check passed
Claude Code Command Development
anthropics/claude-plugins-official
Official
Explains how to write Claude Code slash commands: Markdown files with YAML frontmatter, arguments, file references, bash context and interactive prompts.
37k GitHub starsUsed in 10 repos~4.8k tokens
Agent WorkflowsAuto-check passed

Questions about Plugin Creator

What does Plugin Creator do?

Create and scaffold plugin directories for Codex with a required .codex-plugin/plugin.json, optional plugin folders/files, and baseline placeholders you can edit before publishing or testing. Plugin Creator is an agent skill from lingxling/awesome-skills-cn.json, optional plugin folders/files, and baseline placeholders you can edit before publishing or testing.

When should I use Plugin Creator?

Plugin Creator fits situations like: Codex needs to create a new local plugin; add optional plugin structure; update repo-root .agents/plugins/marketplace.json entries for plugin ordering and availability metadata.

How do I install Plugin Creator in Claude Code?

Run `npx skills add lingxling/awesome-skills-cn --skill plugin-creator -a claude-code`. Or copy the skill folder (openai-skills/skills/.system/plugin-creator in lingxling/awesome-skills-cn) 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 lingxling/awesome-skills-cn --skill plugin-creator -a codex`. Or copy the skill folder (openai-skills/skills/.system/plugin-creator in lingxling/awesome-skills-cn) 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 lingxling/awesome-skills-cn --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 Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.

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 no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Plugin Creator use?

Plugin Creator is published under the Apache-2.0 licence (from the LICENSE file in the skill folder). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Plugin Creator use?

About 1.6k tokens (SKILL.md is roughly 6.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.8k tokens, read only when the agent opens those files.

What are the alternatives to Plugin Creator?

Skills that share tags, products or a category with Plugin Creator: Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 37k stars), Claude Code Agent Development (anthropics/claude-plugins-official, 37k stars), Claude Code Skill Developer Guide (diet103/claude-code-infrastructure-showcase, 10k stars) and Plugin Settings Pattern (anthropics/claude-plugins-official, 37k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Plugin Creator?

lingxling (a GitHub user) maintains it in lingxling/awesome-skills-cn, which has 299 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 7, 2026.

Source: lingxling/awesome-skills-cn on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Plugin Creator

Install Plugin Creator

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Plugin Creator

Quick Start

What this skill creates

Marketplace workflow

Required behavior

Reference to exact spec sample

Validation

Files

Compare with similar skills

Similar skills

Hook Development for Claude Code Plugins

Claude Code Agent Development

Claude Code Skill Developer Guide

Plugin Settings Pattern

MCP Integration for Plugins

Claude Code Command Development

More from lingxling/awesome-skills-cn

Openai Docs

Define Goal

Questions about Plugin Creator

Install Plugin Creator

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Plugin Creator

Quick Start

What this skill creates

Marketplace workflow

Required behavior

Reference to exact spec sample

Validation

Files

Compare with similar skills

Similar skills

More from lingxling/awesome-skills-cn

Related

Questions about Plugin Creator