[FEATURE] Install skills from plugins

[daghb]

Is your feature request related to a problem? Please describe.

When apm installs a plugin that includes skills and instructions, these are not mapped/copied from .claude/skills, .github/skills and into the /apm_modules folder structure. It is unclear to me whether this feature is already implemented and can be classified as a bug, or if this exact feature does not exist yet.

Describe the solution you'd like

When running apm install on an apm package that includes plugins, these plugins are copied into the /apm_modules folder, but no skills are exposed in the /skills folder. If I choose to install a skill natively that skill is neatly put in the correct folder, but not if I use a plugin package

Describe alternatives you've considered

Can be bypassed by referencing the skills folder directly, for example dotnet/skills/plugins/dotnet-nuget/skills/convert-to-cpm, but it seems odd to reference the package at dotnet/skills/plugins/dotnet-nuget without the skills included being installed.

[danielmeppiel]

This has been fixed in v0.8.6 (PR #456, which includes fixes #447 and #453).

The root cause was that the skill integrator had hardcoded target paths instead of using the target registry. Plugin sub-skills (under .apm/skills/) are now promoted to all active targets that support skills -- .github/skills/, .claude/skills/, .cursor/skills/, and .opencode/skills/ -- via a unified active_targets() loop.

To get the fix: apm upgrade or install v0.8.6+. After upgrading, a fresh apm install on your plugin package should deploy its skills to the correct folders automatically.

Thanks for reporting this -- happy to reopen if you still see issues after upgrading!

[danielmeppiel]

Closing as completed -- fixed in v0.8.6.