Feature request: add a KiroCrew platform target/profile
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.8k
- Forks
- 362
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 132
Description
What
Add KiroCrew (https://github.com/kirodotdev/KiroCrew) as a supported deploy target/profile in APM, so apm install <pkg> can place skills where KiroCrew reads them.
Why
APM detects and deploys to the platform directories it knows: .github/ (Copilot), .cursor/, .claude/, .opencode/, and for the Kiro family it writes skills to ~/.kiro/skills/ (global) or <project>/.kiro/skills/.
KiroCrew — an agent-management layer several teams run on top of Kiro — discovers skills from a different root: ~/.kiro/crew/skills/. So a package installed with APM today is invisible to KiroCrew's injected skill index. Users currently bridge the gap with per-skill symlinks from ~/.kiro/skills/* into ~/.kiro/crew/skills/*, which is a manual, drift-prone step.
Proposed behaviour
A kirocrew platform profile whose output path is the KiroCrew global skills directory:
- Detect KiroCrew by the presence of
~/.kiro/crew/(analogous to detecting.claude/for Claude Code). - Deploy skill packages into
~/.kiro/crew/skills/<slug>/(a directory-per-skill layout matching KiroCrew's existing convention). - Support it as an explicit
--target kirocrewvalue as well as auto-detection, matching how the other platforms behave.
Workaround that exists today (why this is a nicety, not a blocker)
KiroCrew added a skills.extra_paths config key that lets it load skills read-only from an additional directory. Pointing that at ~/.kiro/skills makes APM-installed skills load into KiroCrew with no symlinks. A first-class kirocrew target would remove even that config step and make the two tools symmetric.
Context
Raised from a Flutter-Global internal effort to make an APM marketplace the single source of truth for agent skills across both Kiro and KiroCrew.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the platform detection and --target handling used by apm install <pkg>, then trace the existing Kiro profile and its global skill-directory deployment. Add the kirocrew profile for ~/.kiro/crew/skills/<slug>/, detect ~/.kiro/crew/, and support explicit targeting. Done means both auto-detection and --target kirocrew deploy packages to the requested directory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100