Description
Currently, when installing a skill, APM creates a skill.md file at the root of the project. Additionally, it seems to modify the original skill file by injecting metadata.
I would like to propose the following changes to improve project cleanliness and preserve source integrity:
- Stop creating
skill.md at the root: Skills should be managed internally within the APM structure (e.g., in a cache or a dedicated hidden folder) rather than polluting the project's root directory.
- Preserve Source Integrity: APM should perform a "clean download" of the skill file. It should not modify the content or inject metadata into the downloaded file. The original content from the source (GitHub/Azure DevOps) should remain untouched.
Use Case
- Clean Workspace: Keeping the root directory free of generated files that are only used during the compilation phase.
- Auditability: Ensuring that the skill used in the project is an exact bit-for-bit copy of the one hosted on the remote repository.
Description
Currently, when installing a skill, APM creates a
skill.mdfile at the root of the project. Additionally, it seems to modify the original skill file by injecting metadata.I would like to propose the following changes to improve project cleanliness and preserve source integrity:
skill.mdat the root: Skills should be managed internally within the APM structure (e.g., in a cache or a dedicated hidden folder) rather than polluting the project's root directory.Use Case