richfrem/agent-plugins-skills / plugins/agent-extension-authoring/.apm/skills/packaging-with-apm
packaging-with-apm
FlaggedPackages, installs and distributes agent extensions with APM (Agent Package Manager). Use when the user wants to create a new APM package, convert or migrate an existing plugin to APM and check it installs cleanly, compile a package into AGENTS.md, CLAUDE.md or GEMINI.md, install, update, pin or roll back packages globally or per project, or create a plugin marketplace catalog (marketplace.json). Not for authoring a single skill, plugin, sub-agent or rule (use the authoring-* skills).
references/marketplace-architecture.md
View on GitHub# Marketplace Architecture - packaging-with-apm
The marketplace mode of packaging-with-apm governs the catalog creation setup enabling custom package hosting.
## Core Concepts
### 1. Catalog Registry (`.claude-plugin/marketplace.json`)
- **Placement**: Positioned inside `.claude-plugin/` folder to satisfy manifest discovery layouts.
- **Structure**: Relies on relative definitions or standard source scopes (GitHub object maps).
### 2. Caching Scopes & Caches
- Plugins distributed are copied to an internal user/project scope cache safely.
- **Variables**: absolute paths must use absolute variables (`${CLAUDE_PLUGIN_ROOT}`) to bridge cached isolation properly.
### 3. Relative Path Source Limitation
A marketplace entry with `"source": "./plugins/my-plugin"` resolves the path relative to the marketplace repository root. This only works when the marketplace was added via a Git clone or local filesystem path. It does NOT work when added via a direct raw URL to `marketplace.json`, because there is no filesystem root to resolve the relative path against.
### 4. `strict` Field Behavior
| `strict` value | Authority |
|---------------|-----------|
| `true` (default) | Plugin's own `.claude-plugin/plugin.json` is the source of truth. Marketplace entry supplements but does not override. |
| `false` | Marketplace entry is the complete definition. Useful for overriding plugin metadata for a specific distribution. |
### 5. Lifecycle
The 2-step consumer process (Add & Install) is natively supported by Claude Code CLI and TUI (`/plugin`).Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |