Is your feature request related to a problem? Please describe.
Yes. Files in the current project’s .apm/ folder are not picked up the same way as files from installed dependencies. Generally, I'm importing skills from a central repo, but if I want to add a specific skill for this repo alone within the apm setup, it does not work. This is confusing. If I add local skills, instructions, agents, prompts, or hooks under .apm/, I would expect apm install to include them automatically, but today extra steps are needed.
Describe the solution you'd like
Make apm install also include supported local content from the current project’s .apm/ folder. This should work for skills, instructions, agents, prompts, hooks, and other APM primitives, and deploy them to the right target folders automatically.
Describe alternatives you've considered
The current workaround is to install local paths manually or move local content into a separate package and add it to apm.yml. This works, but it adds extra setup for files that are already part of the project.
Additional context
This would make APM easier to understand and more consistent. The .apm/ folder already feels like the right place for project-local APM content, so it would be helpful if apm install handled it directly
Is your feature request related to a problem? Please describe.
Yes. Files in the current project’s
.apm/folder are not picked up the same way as files from installed dependencies. Generally, I'm importing skills from a central repo, but if I want to add a specific skill for this repo alone within the apm setup, it does not work. This is confusing. If I add local skills, instructions, agents, prompts, or hooks under.apm/, I would expectapm installto include them automatically, but today extra steps are needed.Describe the solution you'd like
Make
apm installalso include supported local content from the current project’s.apm/folder. This should work for skills, instructions, agents, prompts, hooks, and other APM primitives, and deploy them to the right target folders automatically.Describe alternatives you've considered
The current workaround is to install local paths manually or move local content into a separate package and add it to
apm.yml. This works, but it adds extra setup for files that are already part of the project.Additional context
This would make APM easier to understand and more consistent. The
.apm/folder already feels like the right place for project-local APM content, so it would be helpful ifapm installhandled it directly