apm-marketplace-authoring-gotchas

Diagnose APM marketplace migration failures across packaging, formatting, linting, and commit validation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you avoid the hidden failure modes that appear when migrating Claude Code skills and plugins into an APM-managed marketplace, especially when CI, packaging, formatting, and commit hooks all seem to fail for different reasons.

Core Features & Use Cases

  • Marketplace migration troubleshooting: Diagnose stale marketplace output, schema validation failures, and version drift between local and CI APM installs.
  • Formatting and linting fixes: Prevent prettier and markdownlint from rewriting or rejecting generated marketplace files and copied SKILL.md content.
  • Authoring-path guidance: Distinguish between APM-native and CC-native plugin workflows so you do not run compile steps that are irrelevant to your source layout.
  • Commit and CI hardening: Resolve commitlint footer false positives and ensure packaging checks behave deterministically in automation.

Quick Start

Ask Claude to audit your APM marketplace migration setup, identify which of the documented gotchas apply, and propose the smallest set of fixes for your CI, formatting, and commit workflow.

Frequently Asked Questions about apm-marketplace-authoring-gotchas

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

FAQPage Schema
Why does my APM marketplace migration fail in CI with formatting errors?

APM marketplace migration fails in CI when prettier and markdownlint rewrite generated marketplace files and copied SKILL.md content. Aligning linting configurations prevents automated formatting from rejecting packaged output.

How do I fix commitlint footer false positives during marketplace migration?

Fix commitlint footer false positives by adjusting commit validation rules to recognize APM-managed build footers. This hardens commit workflows and prevents CI failures from incorrectly flagged commit messages during migration.

What is the correct way to validate APM packaging without unreliable marketplace checks?

Validate APM packaging by using dry-run packaging instead of unreliable marketplace checks. Dry-run packaging verifies version pinning and pluginRoot rewriting deterministically in CI automation.

How do I resolve schema validation failures and version drift when migrating to an APM marketplace?

Resolve schema validation failures and version drift by auditing version pinning across local and CI APM installs. Ensuring pluginRoot rewriting matches your source layout prevents stale marketplace output.

When should I distinguish between APM-native and CC-native plugin workflows?

Distinguish between APM-native and CC-native plugin workflows when moving from hand-authored marketplace files or CC-native layouts into APM-managed builds. This prevents running irrelevant compile steps for your source layout.