marketplace-dev
Skill16 starsChanged 24 days agoMITView on GitHub
This skill MUST activate when creating, modifying, or reviewing the shipwright plugin or its marketplace entry. Triggers on: editing files under plugins/shipwright/, modifying plugin.json or .claude-plugin/marketplace.json, adding commands/skills/agents/hooks to the shipwright plugin, editing TESTING.md, reviewing or creating pull requests that touch plugins/shipwright/, or when user mentions "version bump", "release", "add command", "add skill", "add hook", "add agent", "marketplace update", "plugin checklist", "plugin.json", or "marketplace.json". This skill prevents version drift and enforces structural conventions for the shipwright plugin in this self-hosted marketplace.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- dork-labs/dorkostheir own version, first seen Sep 26, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- dork-labs/dorkos★ 11same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository3 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- shipwright-brandSkill
- verifySkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. About 0 are common, 4 are distinctive, and 11 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
11
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 58
Write correct conventional commits — semantic-release derives the bump type from them:
- Very specific: line 107
When modifying the shipwright plugin:
- Very specific: line 111
Create the component file following conventions (see references/frontmatter-schemas.md)
- Distinctive: line 112
If the plugin has a TESTING.md, add test scenarios for the new component
- Very specific: line 113
Update plugins/shipwright/README.md if it lists available commands
- Very specific: line 114
Write a feat: commit — semantic-release will derive the minor version bump on merge
- Distinctive: line 119
Update TESTING.md if test scenarios are affected
- Very specific: line 120
Write a fix: or feat: commit as appropriate — do not manually bump the version
- Very specific: line 124
Use feat!: as the commit prefix (or add BREAKING CHANGE: to the footer)
- Distinctive: line 125
Document the breaking change in the commit body
- Very specific: line 130
If you change the description in plugin.json, also sync it to:
- Very specific: line 163
Use references/ subdirectory for detailed guidance loaded on-demand
- Very specific: line 164
Use assets/templates/ for output templates
- Very specific: line 165
Keep SKILL.md under 500 lines.
- Very specific: line 203
Use "url" (not "email"), and "App Vitals" (capitalized, with space).
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Marketplace Development Guide
This skill encodes the conventions and checklists for working with the shipwright plugin
in this self-hosted single-plugin marketplace. Follow it to prevent version drift and
maintain consistency.
When This Activates
- Bumping the plugin version (new feature, bug fix, breaking change)
- Adding or modifying commands, skills, agents, or hooks
- Editing
plugins/shipwright/.claude-plugin/plugin.json - Editing
.claude-plugin/marketplace.json(once it exists — see MKT-1.2) - Updating plugin descriptions or README content
- Creating or reviewing PRs that touch
plugins/shipwright/
Version Ownership
This is the most important section. Version in this repo is owned by semantic-release
and scripts/sync-version.ts — do NOT manually bump version numbers.
How Versioning Works
Versions are determined automatically on every merge to main:
- semantic-release analyzes conventional commits since the last tag
- It calls
scripts/sync-version.ts <nextVersion>viaprepareCmdin.releaserc.json sync-version.tswrites the new version to five locations:
| # | File | Updated by |
| 1 | package.json | sync-version.ts |
| 2 | plugins/shipwright/package.json | sync-version.ts |
| 3 | metrics/package.json | sync-version.ts |
| 4 | agent/package.json | sync-version.ts |
| 5 | version.txt | sync-version.ts |
A sixth location, .claude-plugin/marketplace.json, will also be auto-synced once MKT-1.2
lands (the file does not exist yet).
What Developers Do Instead
Write correct conventional commits — semantic-release derives the bump type from them:
| Commit prefix | Bump type | Example |
fix: | Patch (1.2.0 → 1.2.1) | fix: correct hook timeout |
feat: | Minor (1.2.0 → 1.3.0) | feat: add /audit command |
feat!: or BREAKING CHANGE: | Major (1.2.0 → 2.0.0) | feat!: rename dev-task command |
docs:, chore:, ci:, build: | No release | Non-functional changes |
refactor:, test:, perf: | No release | Non-functional changes |
Never manually edit the "version" field in any package.json, plugin.json, or
marketplace.json. The automation owns these.
For a post-release verification checklist, see references/version-sync-checklist.md.
Plugin Structure
This repo is both the plugin source and the marketplace host. The single plugin is
shipwright, living at plugins/shipwright/:
plugins/shipwright/
├── .claude-plugin/
│ └── plugin.json # Plugin manifest (name, version, description, hooks)
├── commands/ # Slash commands (*.md files with YAML frontmatter)
├── skills/ # Skill definitions
│ └── <skill-name>/
│ ├── SKILL.md
│ ├── references/ # On-demand guidance docs
│ └── assets/
│ └── templates/ # Output templates
├── hooks/ # Hook implementations
│ ├── hooks.json # Hook configuration (if not in plugin.json)
│ └── <hook-impl>.sh
├── agents/ # Agent definitions (*.md)
├── scripts/ # Utility and build scripts
├── README.md # Plugin documentation
└── TESTING.md # Manual test planThe marketplace manifest lives at .claude-plugin/marketplace.json (root of repo). It
does not exist yet — it is created in MKT-1.2.
Plugin Modification Checklist
When modifying the shipwright plugin:
Adding a New Component (command, skill, agent, hook)
- Create the component file following conventions (see
references/frontmatter-schemas.md) - If the plugin has a TESTING.md, add test scenarios for the new component
- Update
plugins/shipwright/README.mdif it lists available commands - Write a
feat:commit — semantic-release will derive the minor version bump on merge
Modifying Existing Behavior
- Make the change
- Update TESTING.md if test scenarios are affected
- Write a
fix:orfeat:commit as appropriate — do not manually bump the version
Breaking Changes
- Use
feat!:as the commit prefix (or addBREAKING CHANGE:to the footer) - Document the breaking change in the commit body
- semantic-release will cut a major version bump on merge
Changing the Plugin Description
If you change the description in plugin.json, also sync it to:
- The
descriptionfield in.claude-plugin/marketplace.json(once it exists) - The opening paragraph in
plugins/shipwright/README.md
Component Conventions
Commands (commands/*.md)
---
description: Short action-oriented description # Required
argument-hint: <required-arg> [optional-arg] # Optional
allowed-tools: [Read, Glob, Grep, Bash] # Optional
---- Filename = command name +
.md(e.g.,plan-session.md->/plan-session) - Kebab-case filenames only
- For new work, consider the
skills/<name>/SKILL.mdlayout instead (preferred by Anthropic)
Skills (skills/<name>/SKILL.md)
---
name: skill-name # Required, matches directory name
description: > # Required, ~100 words
When to trigger and what it does...
---- Directory name = skill name, kebab-case
- Use
references/subdirectory for detailed guidance loaded on-demand - Use
assets/templates/for output templates - Keep SKILL.md under 500 lines; split to references if exceeding
Agents (agents/*.md)
---
name: agent-name # Required
description: > # Required
When to use this agent...
model: sonnet # Optional (sonnet, opus, haiku)
tools: # Required
- Read
- Edit
- Grep
---Hooks
Hooks can be configured in plugin.json directly (simple cases) or in hooks/hooks.json
(complex multi-matcher setups). Use shell scripts (.sh) or Python (.py) for
implementation.
For complete schemas and examples, see references/frontmatter-schemas.md.
Naming & Consistency Standards
Author Field (Standardized)
"author": {
"name": "App Vitals",
"url": "https://github.com/app-vitals"
}Use "url" (not "email"), and "App Vitals" (capitalized, with space).
Repository and Homepage
"homepage": "https://github.com/app-vitals/shipwright",
"repository": "https://github.com/app-vitals/shipwright"License
"license": "MIT"Description Sync Points
The plugin description appears in multiple places. When changing it, update all:
| Location | Format |
plugins/shipwright/.claude-plugin/plugin.json | "description" field (canonical source) |
.claude-plugin/marketplace.json | "description" in plugin entry (once it exists) |
plugins/shipwright/README.md | Opening paragraph (may be longer form) |
References
Load these for detailed guidance when needed:
references/version-sync-checklist.md— Post-release verification and a primer on semantic-release ownershipreferences/plugin-scaffolding.md— Templates for plugin component files (plugin.json, README, TESTING.md)references/frontmatter-schemas.md— Complete YAML frontmatter schemas for all component types
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
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.

