This repo is provide a Claude Code marketplace template that contains reusable plugins, agents, commands, skills, and team context for extending Claude Code capabilities across multiple teams.
Pandora Marketplace is a structured repository that serves as a foundational template for teams to:
- Extend Claude Code with custom plugins, agents, and commands
- Share Reusable Components across teams and projects
- Maintain Consistency through shared team context, guidelines, and standards
- Implement Team-Specific Workflows tailored to your development practices
- Build Documentation Automation with intelligent context generation tools
This marketplace enables organizations to create a unified, scalable ecosystem for AI-assisted development while maintaining team-specific customizations and standards.
/plugin marketplace add pandora-marketplaceOr add it with a specific repository path:
# Add from local directory
/plugin marketplace add ./pandora_marketplace
# Add from GitHub repository
/plugin marketplace add owner/pandora_marketplace
# Add from Git URL
/plugin marketplace add https://github.com/your-org/pandora_marketplace.gitOnce the marketplace is added, you can discover all available plugins:
/plugin listThis will show all available plugins in the marketplace, organized by category:
- Core Plugins: Essential tools always recommended
- Integration Plugins: Third-party service integrations
- Team Plugins: Team-specific configurations
Install any plugin from the marketplace using:
/plugin install <plugin-name>@pandora-marketplaceDeepWiki - Documentation Generation System
/plugin install deepwiki@pandora-marketplaceSafeguard - Code Safety & Protection
/plugin install safeguard@pandora-marketplaceLaunchDarkly - Feature Flag Management
/plugin install launchdarkly@pandora-marketplaceAfter installation, each plugin provides specific commands. Refer to individual plugin README files for detailed usage instructions:
# Initialize wiki documentation from your codebase
/deepwiki:init ./ ./wiki
# Sync wiki to Claude Code skills (after manual edits)
/deepwiki:sync ./wiki
# Install security protections
/install
# Manage feature flags
/add-feature-flag new-feature-name# Update marketplace to latest version
/plugin marketplace update
# List installed plugins
/plugin list --installed
# Uninstall a plugin
/plugin uninstall <plugin-name>@pandora-marketplace| Task | Command |
|---|---|
| Add marketplace | /plugin marketplace add pandora-marketplace |
| List plugins | /plugin list |
| Install plugin | /plugin install <name>@pandora-marketplace |
| Update marketplace | /plugin marketplace update |
| Initialize wiki documentation | /deepwiki:init ./ ./wiki |
| Sync wiki to skills | /deepwiki:sync ./wiki |
| Setup security | /install |
| Add feature flag | /add-feature-flag <flag-name> |
The pandora hub supports team-contributed components that can be selectively installed. Teams publish agents, hooks, MCP servers, skills, slash commands, and workflows that other users can browse and install.
Each team has a dedicated directory under plugins/community/online/ with the following structure:
plugins/community/online/{team-name}/
├── manifest.json # Team metadata and component registry
├── agents/ # Claude Code agents
├── hooks/ # Event-driven hooks
├── mcp_servers/ # MCP server configurations
├── skills/ # Reusable skills
├── slash_commands/ # Slash commands
└── workflows/ # Multi-step workflows
Each team's manifest.json defines available components:
{
"team": "team-name",
"description": "Team description",
"version": "1.0.0",
"maintainers": ["maintainer@example.com"],
"components": {
"agents": [
{ "name": "agent-name", "description": "What it does", "path": "./agents/agent-name.md" }
],
"hooks": [
{ "name": "hook-name", "description": "What it does", "path": "./hooks/hook-name/" }
],
"mcp_servers": [
{ "name": "server-name", "description": "What it does", "path": "./mcp_servers/server-name/" }
],
"skills": [
{ "name": "skill-name", "description": "What it does", "path": "./skills/skill-name/" }
],
"slash_commands": [
{ "name": "command-name", "description": "What it does", "path": "./slash_commands/command-name.md" }
],
"workflows": [
{ "name": "workflow-name", "description": "What it does", "path": "./workflows/workflow-name/" }
]
}
}| Team | Description |
|---|---|
decide-team |
Decision-making tools and workflows |
find-team |
Search and discovery tools |
inspire-team |
Creative and inspiration tools |
Step 1: List available teams
/pandora:teamsStep 2: Browse a team's components
/pandora:browse decide-teamStep 3: Install components
# Interactive installation (prompts for team, type, component)
/pandora:install
# Install a specific component
/pandora:install decide-team agents hello-world
# Install all agents from a team
/pandora:install decide-team agents *
# Install all components from a team
/pandora:install decide-team *Command Syntax:
| Arguments | Behavior |
|---|---|
| (none) | Guided - prompts for team, type, component |
<team> |
Prompts for type and component |
<team> <type> |
Prompts for component |
<team> <type> <name> |
Installs directly |
<team> <type> * |
Installs all of that type |
<team> * |
Installs everything from team |
Components are installed to your ~/.claude/ directory:
| Component Type | Installation Location |
|---|---|
| agents | ~/.claude/agents/ |
| hooks | ~/.claude/hooks/ + settings.json |
| mcp_servers | ~/.claude/mcp_servers/ + settings.json |
| skills | ~/.claude/skills/ |
| slash_commands | ~/.claude/commands/ |
| workflows | ~/.claude/workflows/ |
pandora_marketplace/
├── .claude/
│ └── settings.json # Claude Code settings
├── plugins/ # All Claude Code plugins and extensions
│ ├── core/ # Core plugins (always included)
│ │ ├── deepwiki/ # Documentation generation suite
│ │ │ ├── agents/ # Planner, doc-generator, skill-generator
│ │ │ ├── commands/ # init.md, sync.md
│ │ │ └── skills/ # ASCII diagrams, templates, patterns
│ │ └── safeguard/ # Code safety and damage control
│ │ ├── commands/ # install.md
│ │ └── skills/ # Damage control hooks and cookbooks
│ ├── integrations/ # Third-party integrations
│ │ └── launchdarkly/ # LaunchDarkly feature flags
│ │ ├── commands/ # add-feature-flag.md, remove-feature-flag.md
│ │ └── mcp/ # MCP server configuration
│ └── community/ # Community-contributed components
│ └── online/ # Online teams
│ ├── decide-team/ # Decision-making tools
│ │ ├── manifest.json # Team metadata and component registry
│ │ ├── agents/ # Team agents
│ │ ├── hooks/ # Team hooks
│ │ ├── mcp_servers/ # Team MCP servers
│ │ ├── skills/ # Team skills
│ │ ├── slash_commands/ # Team slash commands
│ │ └── workflows/ # Team workflows
│ ├── find-team/ # Search and discovery tools
│ │ └── ... # Same structure as above
│ └── inspire-team/ # Creative and inspiration tools
│ └── ... # Same structure as above
├── templates/ # Templates for creating new plugins
│ ├── agents/ # Agent creation templates
│ ├── hooks/ # Hook implementation templates
│ ├── mcp_servers/ # MCP server templates
│ ├── skills/ # Skill creation templates
│ ├── slash_commands/ # Slash command templates
│ └── workflows/ # Workflow templates
├── .gitignore # Git ignore rules
└── README.md # This file
Documentation generation suite with on-demand context loading:
/deepwiki:init- Initialize wiki documentation from codebase with ASCII diagrams and cross-references/deepwiki:sync- Sync documentation to Claude Code skills for automatic context loadingdeepwiki-planner- Agent that analyzes codebase and generates documentation structuredeepwiki-doc-generator- Agent that generates individual wiki pages with diagramsdeepwiki-skill-generator- Agent that creates Claude Code skills from wiki
Code safety and damage control plugin:
- Code analysis and safety checks
- Damage control recovery utilities
- Language-specific hooks for Python and TypeScript
Third-party service integrations:
- LaunchDarkly - Feature flag management
Starting templates for extending the marketplace:
- Agents: Templates for creating custom Claude Code agents
- Skills: Templates for implementing reusable skills
- Slash Commands: Templates for creating new commands
- Workflows: Templates for complex multi-step workflows
- Hooks: Templates for event-driven automation
- MCP Servers: Templates for MCP server integration
# Clone or copy the marketplace template
git clone <marketplace-repo> pandora_marketplace
cd pandora_marketplaceClaude Code will:
- Discover all plugins in the
/pluginsdirectory - Load marketplace configuration
- Make all commands, agents, and skills available
Use DeepWiki to generate documentation from your codebase:
# Initialize wiki documentation
/deepwiki:init ./ ./wiki
# Sync to Claude Code skills for on-demand context
/deepwiki:sync ./wikiOnce registered, use Claude Code to access marketplace features:
# Initialize wiki documentation from your codebase
/deepwiki:init /path/to/your/repo ./wiki
# Sync wiki to Claude Code skills (after manual edits)
/deepwiki:sync ./wiki
# Sync custom documentation as a skill
/deepwiki:sync ./docs/team-conventions conventionsSee templates/slash_commands/slash-command-template.md for:
- Command syntax and parameters
- Tool permissions configuration
- Output format guidelines
- Examples and usage patterns
See templates/agents/subagent-template.md for:
- Agent capability definition
- Input/output specifications
- Tool access configuration
- Integration with Claude Code
See templates/skills/skill-template.md for:
- Skill structure and metadata
- Template usage examples
- Reference materials
- Helper scripts
See templates/workflows/workflow_template.md for:
- Workflow composition
- Multi-step orchestration
- Conditional logic
- Error handling
Plugins are organized by category:
plugins/
├── core/ # Essential plugins included by default
├── integrations/ # Third-party service integrations
└── community/ # Community-contributed components
└── online/ # Online teams (selectively installable)
Each plugin can contain:
- Commands (
.commands/): Slash commands and CLI-style operations - Agents (
.agents/): Autonomous Claude agents for complex tasks - Skills (
.skills/): Reusable capabilities with templates - Workflows (
.workflows/): Multi-step orchestrated processes - MCP Servers (
.mcp/): Model Context Protocol integrations
# Initialize wiki from your project
/deepwiki:init /path/to/your/project ./wiki
# Result: Complete documentation in ./wiki/
# ├── README.md - Navigation hub
# ├── overview/ - System overview, tech stack, glossary
# ├── architecture/ - System design, components, data model
# ├── features/ - Feature documentation
# ├── development/ - Setup, coding standards
# ├── testing/ - Testing strategy
# └── deployment/ - Build and environments# After manual edits to wiki, sync to skills
/deepwiki:sync ./wiki
# Creates skills at {home}/.claude/skills/
# ├── overview/SKILL.md
# ├── architecture/SKILL.md
# ├── features/SKILL.md
# └── ...
# Claude auto-loads relevant context as you work# Create custom documentation directory
mkdir -p ./docs/team-conventions
# Sync with custom skill name
/deepwiki:sync ./docs/team-conventions conventions
# Result: {home}/.claude/skills/conventions/SKILL.md# Update only architecture skill after edits
/deepwiki:sync ./wiki/architecture
# Result: Updates {home}/.claude/skills/architecture/SKILL.mdDefined in Markdown with frontmatter:
---
allowed-tools: Glob(**/*), Grep(pattern:*), Read(**/*), Write(**/*), Task(subagent_type=Explore)
argument-hint: [param1] [param2]
description: Brief description of functionality
---
## Purpose
...
## Parameters
...
## Execution Steps
...Organized by category with consistent structure:
# Topic Title
## Overview
...
## Current State
...
## Standards/Guidelines
...
## References
...- Generate Documentation with
/deepwiki:initto create wiki from your codebase - Sync to Skills with
/deepwiki:syncfor on-demand context loading - Add Team Components in
plugins/community/online/{team-name}/for team-specific tools - Share with Team and make marketplace available to all team members
- Maintain Core plugins in
plugins/core/ - Organize by Team in
plugins/community/online/{team-name}/ - Central Registry via manifest.json in each team directory
To add components to a team:
- Create component in the appropriate directory (e.g.,
plugins/community/online/decide-team/agents/) - Update the team's
manifest.jsonto register the component - Follow the templates in
templates/for proper formatting
To add new plugins or components to the marketplace:
- Use Templates: Start with relevant template in
templates/ - Follow Structure: Organize in appropriate
plugins/directory - Test: Verify plugin works with Claude Code
- Plugin Templates:
templates/directory - Core Plugins:
plugins/core/directory - Integration Examples:
plugins/integrations/directory
Pandora Marketplace v1.0.0
- Initial implementation
- Core plugins: DeepWiki, Safeguard
- Integration: LaunchDarkly
- Plugin development templates
For help:
- Check Plugin Marketplaces Documentation
- Check Plugins Documentation
- Check Discover Plugins Documentation
Pandora Marketplace - Building scalable, team-aware Claude Code ecosystems