Contributing to Dapi Marketplace banner
dapi dapi

Contributing to Dapi Marketplace

Development community intermediate

Description

Thank you for your interest in contributing! This guide will help you add new agents, skills, and plugins to the marketplace.

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

Repository README

This is the README for dapi/claude-code-marketplace, shared by 4 entries in this directory. It describes the repository, not this entry specifically.

Contributing to Dapi Marketplace

Thank you for your interest in contributing! This guide will help you add new agents, skills, and plugins to the marketplace.

Table of Contents

Creating New Agents

Agents are specialized AI assistants for specific development tasks.

Agent File Structure

Create a new markdown file in the plugin's `agents/` directory:

plugin-name/agents/agent-name.md

Agent Template

---
name: agent-name
description: |
  Clear description of when to use this agent and what it does.
  Include specific use cases and triggering scenarios.
  Maximum 1024 characters.
---

You are a specialized agent for [specific domain].

Your expertise includes:
- [Specific capability 1]
- [Specific capability 2]
- [Specific capability 3]

When invoked, you should:
1. [Step-by-step process]
2. [Clear methodology]
3. [Expected output format]

Key principles:
- [Important guideline 1]
- [Important guideline 2]
- [Important guideline 3]

Agent Best Practices

**Naming Conventions:**

  • Use lowercase with hyphens: code-architect, test-strategist
  • Be descriptive and specific
  • Maximum 64 characters

**Description Guidelines:**

  • Start with "Use when..." to clearly define triggers
  • Include specific keywords for discovery
  • Mention the agent's unique value proposition
  • Keep under 1024 characters

**Content Quality:**

  • Define clear scope and boundaries
  • Provide systematic methodology
  • Include concrete examples
  • Avoid vague generalizations

Creating New Skills

Skills are model-initiated capabilities that Claude uses automatically.

Skill Directory Structure

Create a new directory in the plugin's `skills/` folder:

plugin-name/skills/skill-name/
├── SKILL.md              # Required: Main skill definition
├── reference.md          # Optional: Detailed documentation
├── examples.md           # Optional: Usage examples
└── templates/            # Optional: Code templates

Skill Template (SKILL.md)

---
name: skill-name
description: |
  Critical: When should Claude use this skill?
  Include triggering scenarios and keywords.
  This determines automatic activation.
allowed-tools: Read, Grep, Glob, Bash  # Optional: Restrict tools
---

# Skill Name

## When to Use

This skill activates when:
- [Specific scenario 1]
- [Specific scenario 2]
- [Triggering keywords or patterns]

## Methodology

### Phase 1: [First Phase Name]

[Step-by-step instructions]
- Concrete actions
- Expected outcomes
- Quality gates

### Phase 2: [Second Phase Name]

[Detailed process]

### Phase 3: [Final Phase Name]

[Completion criteria]

## Quality Standards

- [Standard 1]
- [Standard 2]
- [Standard 3]

## Anti-Patterns to Avoid

- ❌ [Common mistake 1]
- ❌ [Common mistak