contributing-a-plugin-component
/contributing-a-plugin-component
Places a new agent, skill or plugin in this marketplace — which plugin owns it, whether it clears the tsh-core admission bar, and what to name it. Use when adding or moving anything under plugins/, before writing the file.
- Author
- thesoftwarehouse ↗
- Repository
- agentic-collections ↗
- Licence
- MIT
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Places a new agent, skill or plugin in this marketplace — which plugin owns it, whether it clears the tsh-core admission bar, and what to name it. Use when adding or moving anything under plugins/, before writing the file.
Original author description
Places a new agent, skill or plugin in this marketplace — which plugin owns it, whether it clears the tsh-core admission bar, and what to name it. Use when adding or moving anything under plugins/, before writing the file.
How it works
- Step 1 — What are you adding?
- Step 2 — Which plugin owns it?
- Step 3 — Name it
- Step 4 — Write it
- Step 5 — Ship it
- Before opening the PR
SKILL.md preview
---
name: contributing-a-plugin-component
description: "Places a new agent, skill or plugin in this marketplace — which plugin owns it, whether it clears the tsh-core admission bar, and what to name it. Use when adding or moving anything under plugins/, before writing the file."
when_to_use: "Trigger on: adding a skill or agent to any tsh-* plugin, creating a new plugin, moving a component between plugins, or any question of the form \"where does this belong in this repo?\""
---
# Contributing a plugin component
This skill answers **where it goes and what it is called**. It does not teach how to
write a `SKILL.md` or an agent file — that belongs to
`/tsh-core:authoring-claude-extensions`, which this skill hands off to at step 4.
(That skill ships in the `tsh-core` plugin; install it if the command is not
available.)
Run this **before creating the file.** The conventions below live in
`.claude/rules/`, which fires when Claude *reads* a matching file — so it cannot reach
you while you are creating one. That is the whole reason this skill exists.
## Step 1 — What are you adding?
| | Use when | Invoked as |
| :-- | :-- | :-- |
| **Agent** | Self-contained work whose intermediate reasoning should stay out of the conversation — audits, reviews, investigations. It hands back a report. | `@tsh-product-testing:a11y-auditor` |
| **Skill** | A procedure the main agent should follow inline, with full access to what the conversation knows. It changes how the conversation proceeds. | `/tsh-product-testing:audit-page` |
| **Plugin** | Neither fits an existing plugin's scope — see step 2 before concluding this. | — |
## Step 2 — Which plugin owns it?
Apply the routing predicate in `CLAUDE.md` — *ask in order, stop at the first yes*.
It is already in context; do not restate it here.
Then, depending on where it lands:
- **`tsh-core`** → read `.claude/rules/core-plugin-admission.md` **now**, before
writing anything. Admission is by elimination *plus evidence*: the PR must name
which three of the five disciplines would invoke it in a normal month, and report
the plugin's routing footprint before and after. **Ties go to a discipline plugin.**
- **`tsh-stack-*`** → read `.claude/rules/stack-plugin-conventions.md`. A stack is a
runtime target, not a language, and duplication between stack plugins is deliberate.
- **A discipline plugin** → no extra gate. This is the default, and it is meant to be.
- **A new plugin** → it also needs an entry in `.claude-plugin/marketplace.json`, or
nobody can install it. See `.claude/rules/plugin-manifests-and-marketplace.md`.
## Step 3 — Name it
- Kebab-case, **without** a `tsh-` prefix — the plugin already namespaces it.
- Agent filename matches its frontmatter `name`. A skill's directory name *is* its name.
- **No framework version in the name**: `implementing-nestjs-api`, never
`implementing-nestjs-11-api`. The name is the invocation command, so a pinned major
forces a rename on every upgrade, and a rename is a `major` bump.
- **Keep it tech-qualified**: `implementing-nestjs-api`, not `implementing-api`. The
model routes on descriptions, and two near-identical ones are a coin flip.
## Step 4 — Write it
Hand off to **`/tsh-core:authoring-claude-extensions`** for the mechanics: frontmatter,
writing a `description` that routes, progressive disclosure above ~150 lines, the
Reference Loading table's **Load when** column, and the fields a plugin-shipped agent
may not declare.
Two constraints from this repo that apply while writing:
- **Cross-link only inside your own plugin.** `./references/<topic>.md`, or
`${CLAUDE_PLUGIN_ROOT}/…` between skills of the same plugin. A path into another
plugin is a silent dead link when that plugin is not installed.
- **A `CLAUDE.md` inside a plugin is not loaded.** Ship instructions as a skill;
per-plugin human docs go in that plugin's `README.md`.
## Step 5 — Ship it
Invoke **`/releasing-a-plugin-change`**. Merging is releasing here, so the version
bump and the `CHANGELOG.md` entry land in the same commit as the change.
## Before opening the PR
```text
- [ ] The owning plugin was chosen with the CLAUDE.md predicate, not by feel
- [ ] If tsh-core: three disciplines named, routing footprint reported before and after
- [ ] Name is kebab-case, unprefixed, tech-qualified, carries no framework version
- [ ] A new plugin has a marketplace.json entry, and the announcement names
`/plugin marketplace update tsh-agentic-collections`
- [ ] No cross-plugin links
- [ ] `claude plugin validate ./plugins/<name>` and `claude plugin validate .` pass
- [ ] Version bumped and CHANGELOG entry written, in this same commit
```
Versions
The database has no other skills named contributing-a-plugin-component.
Database snapshot: 13.11.2026 · package version d6af24cf9c69 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90create-plugin
Scaffold a new AI agent plugin directory with valid manifest, component directories, and marketplace wiring. Use when starting a new plugin, adding a plugin to a multi-plugin repository, or reviewing a plugin before submission. - 100skills-creator
Create plugin components (skills, agents, commands, full plugins) and decide skill vs agent architecture. TRIGGER WHEN: creating, adding or scaffolding a new skill, agent, command or plugin ("new skill", "new agent", "new plugin", "skills-creator"). DO NOT TRIGGER WHEN: auditing… - 100add-plugin
Guide for adding a new plugin to this marketplace. Use when creating or scaffolding a new plugin. - 100cc-plugin-development
Build, validate, and publish Claude Code plugins — manifest schema, skill/command/agent/hook authoring, MCP server integration, marketplace publishing, version management. Use this skill whenever creating a new plugin, adding a skill/command/agent to an existing plugin,… - 100create-plugin
Use this skill when the user asks to "create a plugin", "add a plugin", "make a new plugin", "build a plugin", or wants to package skills into an installable plugin for this marketplace. Guides creating a properly structured plugin under plugins/. - 100skills-creator
Create plugin components (skills, agents, commands, full plugins) and decide skill vs agent architecture. TRIGGER WHEN: creating, adding or scaffolding a new skill, agent, command or plugin ("new skill", "new agent", "new plugin", "skills-creator"). DO NOT TRIGGER WHEN: auditing…