marketing

80_Skills_and_Agents

The Composable DXP plugin marketplace for Claude. 18 plugins, 182 skills, packaged for Claude Code (CLI), Claude Desktop (Cowork mode), and drag-and-drop install.

Marketplace name: composable-dxp (the value in .claude-plugin/marketplace.json) Repo: https://github.com/bpainter/composable-dxp-claude-marketplace (public, personal)

Quick install

# Cowork (Git URL — Cowork requires Git, not local paths)
claude plugin marketplace add https://github.com/bpainter/composable-dxp-claude-marketplace.git
claude plugin install <plugin>@composable-dxp

# Claude Code (also accepts the local path)
claude plugin marketplace add "/Users/bermon.painter/Library/CloudStorage/OneDrive-Slalom/Slalom Second Brain/80_Skills_and_Agents"
claude plugin install <plugin>@composable-dxp

For full install paths (Cowork, Claude Code, drag-and-drop), see INSTALL.md.

Top-level layout

80_Skills_and_Agents/
├── README.md                    # this file (conventions and structure)
├── INSTALL.md                   # how to install the marketplace and plugins
├── .claude-plugin/
│   └── marketplace.json         # marketplace manifest — lists every plugin
├── Memory/                      # cross-cutting working memory (CLAUDE.md, people, glossary, etc.)
│                                # NOT a plugin — read by Claude every session
├── Plugins/                     # built .plugin files (build artifacts)
│   └── <plugin>.plugin
└── <plugin-name>/               # one folder per plugin SOURCE (e.g., obsidian/, claude/)
    └── ... (see "Plugin layout" below)

The marketplace itself is a single Claude plugin marketplace. Tools that consume marketplaces (Claude Code CLI, Claude Desktop via Cowork) read .claude-plugin/marketplace.json to discover what's installable.

Memory/ is not a plugin. It's the user's working memory and shared knowledge base, read every session by Claude, and shared across all plugins.

Plugins/ holds built artifacts — the .plugin files (renamed ZIPs) that get dragged into Claude Desktop's Personal Plugins panel for install. The source of each plugin lives in its own folder at the marketplace root (e.g., obsidian/, claude/); the .plugin files in Plugins/ are derived from those sources via the build process described in INSTALL.md.

Plugin layout (the standard)

Every plugin under this marketplace follows this exact shape. Deviations break tooling.

<plugin-name>/                              # plugin SOURCE (lives at marketplace root)
├── README.md                              # plugin overview for humans
├── .claude-plugin/
│   └── plugin.json                        # plugin manifest for Claude (only `name` is required)
├── references/                            # plugin-wide shared references (optional)
│   └── <plugin>-foundations.md
├── skills/                                # auto-discovered by Claude
│   ├── <plugin>-<skill-name>/             # one folder per skill
│   │   ├── SKILL.md                       # required — frontmatter (name, description) + body
│   │   └── references/                    # skill-specific deep references (typical, 1–3 files)
│   │       └── <topic>.md
│   └── ... (more skills)
├── agents/                                # auto-discovered by Claude (workers)
│   └── <plugin>-<agent-name>.md           # single file per agent, Claude Code agent format
└── commands/                              # slash commands (optional)
    └── <command-name>.md

Why each piece exists

Piece	Required?	Purpose
README.md	recommended	Plugin overview, opinion, roadmap, written for humans browsing the repo
.claude-plugin/plugin.json	required	Manifest Claude reads. Only name is strictly required; version, description, author, keywords, license are optional. Don't include empty optional fields (e.g., "homepage": "") — they fail manifest validation
references/	optional	Plugin-wide shared references at the plugin root. From a SKILL.md, cite as ../../references/<file>.md
skills/	optional	Skills (one folder per skill, each with a SKILL.md). Auto-discovered by Claude
skills/<skill>/SKILL.md	required if folder exists	The skill itself — YAML frontmatter (name, description) + body
skills/<skill>/references/	optional	Skill-specific deep references (frameworks, checklists, examples). From the SKILL.md, cite as references/<file>.md
agents/	optional	Workers that act on user data — Claude Code agent file format (one file per agent)
commands/	optional	Slash commands — single Markdown files with description: frontmatter and a body that names the skill or workflow to invoke

A plugin can have any combination of skills, agents, and commands. Empty folders are fine if you intend to fill them later.

Two flavors of skills: advice vs orchestrator-shaped