home / skills / aaronontheweb / dotnet-skills / marketplace-publishing

marketplace-publishing skill

/skills/marketplace-publishing

This skill guides publishing workflows for skills and agents to the dotnet-skills marketplace, including validation, versioning, and release tagging.

npx playbooks add skill aaronontheweb/dotnet-skills --skill marketplace-publishing

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
5.9 KB
---
name: marketplace-publishing
description: Workflow for publishing skills and agents to the dotnet-skills Claude Code marketplace. Covers adding new content, updating plugin.json, validation, and release tagging.
invocable: true
---

# Marketplace Publishing Workflow

This skill documents how to publish skills and agents to the dotnet-skills Claude Code marketplace.

## Repository Structure

```
dotnet-skills/
├── .claude-plugin/
│   ├── marketplace.json      # Marketplace catalog
│   └── plugin.json           # Plugin metadata + skill/agent registry
├── .github/workflows/
│   └── release.yml           # Release automation
├── skills/
│   ├── akka/                 # Akka.NET skills
│   │   ├── best-practices/SKILL.md
│   │   ├── testing-patterns/SKILL.md
│   │   └── ...
│   ├── aspire/               # .NET Aspire skills
│   ├── csharp/               # C# language skills
│   ├── testing/              # Testing framework skills
│   └── meta/                 # Meta skills
├── agents/
│   └── *.md                  # Agent definitions
└── scripts/
    └── validate-marketplace.sh
```

## Adding a New Skill

### Step 1: Choose a Category

Skills are organized by domain:

| Category | Purpose |
|----------|---------|
| `akka/` | Akka.NET actor patterns, testing, clustering |
| `aspire/` | .NET Aspire orchestration, testing, configuration |
| `csharp/` | C# language features, coding standards |
| `testing/` | Testing frameworks (xUnit, Playwright, Testcontainers) |
| `meta/` | Meta skills about this marketplace |

Create a new category folder if none fits.

### Step 2: Create the Skill Folder

Create a folder with `SKILL.md` inside:

```
skills/<category>/<skill-name>/SKILL.md
```

Example: `skills/akka/cluster-sharding/SKILL.md`

### Step 3: Write the SKILL.md

```markdown
---
name: my-new-skill
description: Brief description of what this skill does and when to use it.
---

# My New Skill

## When to Use This Skill

Use this skill when:
- [List specific scenarios]

---

## Content

[Comprehensive guide with examples, patterns, and anti-patterns]
```

**Requirements:**
- `name` must be lowercase with hyphens (e.g., `cluster-sharding`)
- `description` should be 1-2 sentences explaining when Claude should use this skill
- Content should be 10-40KB covering the topic comprehensively
- Include concrete code examples with modern C# patterns

### Step 4: Register in plugin.json

Add the skill path to `.claude-plugin/plugin.json` in the `skills` array:

```json
{
  "skills": [
    "./skills/akka/best-practices",
    "./skills/akka/cluster-sharding"  // Add new skill here
  ]
}
```

### Step 5: Validate

Run the validation script:

```bash
./scripts/validate-marketplace.sh
```

### Step 6: Commit Together

```bash
git add skills/akka/cluster-sharding/ .claude-plugin/plugin.json
git commit -m "Add cluster-sharding skill for Akka.NET Cluster Sharding patterns"
```

---

## Adding a New Agent

### Step 1: Create the Agent File

Create a markdown file in `/agents/`:

```markdown
---
name: my-agent-name
description: Expert in [domain]. Specializes in [specific areas]. Use for [scenarios].
model: sonnet
color: blue
---

You are a [domain] specialist with deep expertise in [areas].

**Reference Materials:**
- [Official docs and resources]

**Core Expertise Areas:**
[List expertise areas]

**Diagnostic Approach:**
[How the agent analyzes problems]
```

**Requirements:**
- `name` must be lowercase with hyphens
- `model` must be one of: `haiku`, `sonnet`, `opus`
- `color` is optional (used for UI display)

### Step 2: Register in plugin.json

Add to the `agents` array:

```json
{
  "agents": [
    "./agents/akka-net-specialist",
    "./agents/my-agent-name"  // Add new agent here
  ]
}
```

### Step 3: Commit Together

```bash
git add agents/my-agent-name.md .claude-plugin/plugin.json
git commit -m "Add my-agent-name agent for [domain] expertise"
```

---

## Publishing a Release

### Versioning

Update the version in `.claude-plugin/plugin.json`:

```json
{
  "version": "1.1.0"
}
```

Use semantic versioning (`MAJOR.MINOR.PATCH`):
- **MAJOR**: Breaking changes (renamed/removed skills)
- **MINOR**: New skills or agents added
- **PATCH**: Fixes or improvements to existing content

### Release Process

1. **Update version in plugin.json**

2. **Validate**
   ```bash
   ./scripts/validate-marketplace.sh
   ```

3. **Commit version bump**
   ```bash
   git add .claude-plugin/plugin.json
   git commit -m "Bump version to 1.1.0"
   ```

4. **Create and push tag**
   ```bash
   git tag v1.1.0
   git push origin master --tags
   ```

5. **GitHub Actions will automatically:**
   - Validate the marketplace structure
   - Create a GitHub release with auto-generated notes

---

## User Installation

Users install the complete plugin (all skills and agents):

```bash
# Add the marketplace (one-time)
/plugin marketplace add Aaronontheweb/dotnet-skills

# Install the plugin (gets everything)
/plugin install dotnet-skills

# Update to latest version
/plugin marketplace update
```

---

## Validation Checklist

Before committing:

- [ ] SKILL.md has valid YAML frontmatter with `name` and `description`
- [ ] Skill folder is under appropriate category
- [ ] Path added to `plugin.json` skills array
- [ ] For agents: `model` is specified (haiku/sonnet/opus)
- [ ] `./scripts/validate-marketplace.sh` passes

---

## Troubleshooting

### Skill not appearing after install

- Verify the path in plugin.json matches the folder structure
- Check that SKILL.md exists in the folder
- Try reinstalling: `/plugin uninstall dotnet-skills && /plugin install dotnet-skills`

### Validation errors

- Ensure JSON is valid: `jq . .claude-plugin/plugin.json`
- Check for trailing commas in arrays
- Verify all referenced folders contain SKILL.md

### Release not created

- Ensure tag follows semver format (`v1.0.0`)
- Check GitHub Actions logs for errors
- Verify plugin.json version matches the tag

Overview

This skill documents a repeatable workflow to publish skills and agents to the dotnet-skills Claude Code marketplace. It covers creating content, registering entries in plugin metadata, running validation, and tagging releases for automated publishing. The guide is focused on .NET developer content and CI-driven releases.

How this skill works

You create a skill or agent document with YAML frontmatter describing name, description, and required metadata, then add its path to the plugin metadata file under the appropriate array. A validation script checks structure and metadata before commits. Releases are produced by bumping the version, tagging with semver, and letting CI create a GitHub release and marketplace update.

When to use it

  • Adding a new .NET-focused skill or sub-agent to the marketplace catalog
  • Updating metadata or content for an existing skill or agent
  • Preparing a release that should trigger automated publishing
  • Running pre-commit validation to catch structural or metadata errors

Best practices

  • Place content in a clear category folder that matches the domain (e.g., csharp, testing, akka)
  • Use lowercase, hyphenated names for entries and include a 1–2 sentence description in frontmatter
  • Include concrete, modern C# examples and keep content comprehensive but focused
  • Register new content paths in the plugin metadata file and run the validation script before committing
  • Bump version using semantic versioning and create a matching git tag (vMAJOR.MINOR.PATCH)

Example use cases

  • Add a new clustering patterns skill under an akka category with code examples and register it in metadata
  • Create a domain specialist agent file (name, model: haiku|sonnet|opus) and list it in the agents array
  • Update plugin metadata version, validate, tag v1.2.0, and push to trigger CI release notes
  • Diagnose why a skill did not appear after install by validating path entries and re-running the validation script

FAQ

What metadata is required for a skill document?

Provide a lowercase hyphenated name and a 1–2 sentence description in YAML frontmatter; include comprehensive content and examples.

Which models are allowed for agents?

Agents must specify one of the permitted models: haiku, sonnet, or opus.

What causes CI to create a release?

Pushing a git tag that matches semantic versioning (e.g., v1.1.0) after updating the metadata version triggers the automated release workflow.