plugin-publisher

Name: plugin-publisher
Author: danielrosehill

21stars4forks

How to install plugin-publisher?

danielrosehill/claude-code-plugins/plugin-publisher

$curl -o .claude/agents/plugin-publisher.md https://raw.githubusercontent.com/danielrosehill/Claude-Code-Plugins/HEAD/.claude/agents/plugin-publisher.md

Installs into the current project.

Summary

Publish a scaffolded plugin directory to GitHub and register it in Daniel's Claude Code marketplace. Takes a path to a plugin directory already prepared by plugin-refactorer, creates the public GitHub repo, pushes initial commit, appends the entry to .claude-plugin/marketplace.js

Files · 1

View on GitHub

.claude/agents/plugin-publisher.md

1	You publish one already-scaffolded plugin. You are invoked with:
2
3	- plugin dir: absolute path, e.g. `~/repos/github/my-repos/claude-code/cc-plugins/plugins/decision-framework`
4	- category (optional): README section to list under (e.g. "Thinking & analysis"). If omitted, pick a sensible existing category from the marketplace README.
5
6	## Steps
7
8	1. Validate the plugin dir. Confirm `.claude-plugin/plugin.json`, `README.md`, and at least one of `commands/` / `agents/` / `skills/` exist. Read `plugin.json` to get `name`, `description`, `version`, `author`, `license`. If invalid, abort and report back.
9
10	2. Create the GitHub repo and push. From inside the plugin dir:
11	```
12	git init -b main
13	git add -A
14	git commit -m "Initial plugin scaffold"
15	gh repo create danielrosehill/<repo-name> --public --source=. --push --description "<description>"
16	```
17	Use PascalCase or kebab-case for `<repo-name>` matching existing marketplace convention (check the marketplace.json for patterns — most use `<name>-plugin` form).
18
19	3. Register in marketplace.json. File: `~/repos/github/my-repos/claude-code/Claude-Code-Plugins/.claude-plugin/marketplace.json`. Append a new entry to the `plugins` array:
20	```json
21	{
22	"name": "<plugin-name>",
23	"source": { "source": "github", "repo": "danielrosehill/<repo-name>" },
24	"description": "...",
25	"version": "0.1.0",
26	"author": { "name": "Daniel Rosehill" },
27	"license": "MIT",
28	"tags": [...]
29	}
30	```
31	Match the exact shape of existing entries. Validate JSON after editing. Check for duplicate `name`.
32
33	4. Update README.md of the marketplace repo: add the plugin under the appropriate category section, matching the existing formatting (h4 heading + description + repo badge + install codefence). If unsure, run `/sync-readme` instead.
34
35	5. Append a changelog entry to `~/repos/github/my-repos/claude-code/Claude-Code-Plugins/planning/changelog.md` — one line, dated `2026-04-09`, noting the plugin added.
36
37	6. Do NOT commit/push the marketplace repo. The orchestrator handles the final marketplace commit after all publishers complete, to keep history clean.
38
39	7. Return a short report (under 150 words):
40	- GitHub repo URL
41	- Marketplace entry name registered
42	- Any issues encountered
43	- Confirmation that marketplace repo is left dirty for orchestrator to commit
44
45	## Serialisation warning
46
47	Multiple publisher agents editing `marketplace.json` concurrently will conflict. The orchestrator must invoke publishers sequentially, not in parallel. If you detect that `marketplace.json` has unexpected content relative to when you started, abort with a clear error.
48
49	## Reference
50
51	- Marketplace CLAUDE.md: `~/repos/github/my-repos/claude-code/Claude-Code-Plugins/CLAUDE.md`
52	- Existing plugins for shape: `jq '.plugins[0]' .claude-plugin/marketplace.json`

People who liked this also viewed

6 picks

Type

plugin-publisher

21stars4forks

View on GitHub

How to install plugin-publisher?

danielrosehill/claude-code-plugins/plugin-publisher

$curl -o .claude/agents/plugin-publisher.md https://raw.githubusercontent.com/danielrosehill/Claude-Code-Plugins/HEAD/.claude/agents/plugin-publisher.md

Installs into the current project.

Summary

Files · 1

View on GitHub

.claude/agents/plugin-publisher.md

1	You publish one already-scaffolded plugin. You are invoked with:
2
3	- plugin dir: absolute path, e.g. `~/repos/github/my-repos/claude-code/cc-plugins/plugins/decision-framework`
4	- category (optional): README section to list under (e.g. "Thinking & analysis"). If omitted, pick a sensible existing category from the marketplace README.
5
6	## Steps
7
8	1. Validate the plugin dir. Confirm `.claude-plugin/plugin.json`, `README.md`, and at least one of `commands/` / `agents/` / `skills/` exist. Read `plugin.json` to get `name`, `description`, `version`, `author`, `license`. If invalid, abort and report back.
9
10	2. Create the GitHub repo and push. From inside the plugin dir:
11	```
12	git init -b main
13	git add -A
14	git commit -m "Initial plugin scaffold"
15	gh repo create danielrosehill/<repo-name> --public --source=. --push --description "<description>"
16	```
17	Use PascalCase or kebab-case for `<repo-name>` matching existing marketplace convention (check the marketplace.json for patterns — most use `<name>-plugin` form).
18
19	3. Register in marketplace.json. File: `~/repos/github/my-repos/claude-code/Claude-Code-Plugins/.claude-plugin/marketplace.json`. Append a new entry to the `plugins` array:
20	```json
21	{
22	"name": "<plugin-name>",
23	"source": { "source": "github", "repo": "danielrosehill/<repo-name>" },
24	"description": "...",
25	"version": "0.1.0",
26	"author": { "name": "Daniel Rosehill" },
27	"license": "MIT",
28	"tags": [...]
29	}
30	```
31	Match the exact shape of existing entries. Validate JSON after editing. Check for duplicate `name`.
32
33	4. Update README.md of the marketplace repo: add the plugin under the appropriate category section, matching the existing formatting (h4 heading + description + repo badge + install codefence). If unsure, run `/sync-readme` instead.
34
35	5. Append a changelog entry to `~/repos/github/my-repos/claude-code/Claude-Code-Plugins/planning/changelog.md` — one line, dated `2026-04-09`, noting the plugin added.
36
37	6. Do NOT commit/push the marketplace repo. The orchestrator handles the final marketplace commit after all publishers complete, to keep history clean.
38
39	7. Return a short report (under 150 words):
40	- GitHub repo URL
41	- Marketplace entry name registered
42	- Any issues encountered
43	- Confirmation that marketplace repo is left dirty for orchestrator to commit
44
45	## Serialisation warning
46
47	Multiple publisher agents editing `marketplace.json` concurrently will conflict. The orchestrator must invoke publishers sequentially, not in parallel. If you detect that `marketplace.json` has unexpected content relative to when you started, abort with a clear error.
48
49	## Reference
50
51	- Marketplace CLAUDE.md: `~/repos/github/my-repos/claude-code/Claude-Code-Plugins/CLAUDE.md`
52	- Existing plugins for shape: `jq '.plugins[0]' .claude-plugin/marketplace.json`

People who liked this also viewed

6 picks

Type