apm-plugin-distribution-paths

Clarify canonical `.apm/` source layouts for Claude Code and APM plugin files.

Updated Nov 18, 2025
One-click install
npx skills add https://github.com/cajias/claude-skills --skill apm-plugin-distribution-paths
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: apm-plugin-distribution-paths
Source: https://github.com/cajias/claude-skills/tree/main/plugins/cc-authoring/skills/apm-plugin-distribution-paths
Command: npx skills add https://github.com/cajias/claude-skills --skill apm-plugin-distribution-paths

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill clears up where Claude Code and APM plugin files belong, so you can author skills, commands, and agents without confusing source layout with generated output.

Core Features & Use Cases

  • Canonical APM authoring: Explains the correct .apm/ source layout for skills, agents, commands, and prompts.
  • Layout decision support: Helps you choose between a single-skill repo, a multi-primitive package, or consuming an existing Claude plugin.
  • Distribution guidance: Covers install flows, marketplace publishing, and the difference between source files and deployed copies.
  • Validation troubleshooting: Clarifies common APM command errors and how to verify packaging results.

Quick Start

Ask for a clear migration plan that moves your Claude skill files into the canonical .apm/ layout and explains how to verify the package with APM.

Frequently Asked Questions about apm-plugin-distribution-paths

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the canonical .apm/ directory layout for Claude Code and APM skills?

The canonical .apm/ directory layout is the required source structure for authoring Claude Code skills, agents, commands, and prompts. It separates source files from generated output to prevent deployment confusion during APM plugin packaging.

How do I package Claude skills for APM distribution without layout errors?

To package Claude skills correctly, author your files within the canonical .apm/ source layout and validate the results using APM packaging commands. This ensures your skill, agent, and prompt primitives deploy correctly without confusing source files with generated copies.

Should I use a single-skill repository or a multi-primitive package for Claude plugins?

Choose a single-skill repository for isolated Claude skills or a multi-primitive package when bundling skills, agents, commands, and prompts together. APM distribution paths support both layouts, allowing you to select the structure that matches your workflow requirements.

Why does my APM plugin deployment fail with incorrect package layouts?

APM plugin deployment fails when source layout is confused with generated output. Migrating your Claude skill files into the canonical .apm/ structure and verifying the package with APM validation commands resolves these incorrect package layout errors.

Do I need APM validation to publish Claude skills to a marketplace?

Yes, APM validation is required to verify packaging results before publishing Claude skills to a marketplace. Running APM validation commands ensures your plugin bundle meets the canonical .apm/ distribution path requirements and avoids common deployment errors.