Does apm support installing skills into Cursor directories?

[lirantal]

I ran apm install <skill> in the Cursor IDE terminal and it placed it in .github/. I then added the --runtime cursor to the apm install command but it also placed it in .github/

[danielmeppiel]

Hey @lirantal, thanks for reporting this -- and sorry for the friction.

You were hitting two compounding issues:

1. Non-skill primitives (prompts, agents, instructions) were dispatched unconditionally to .github/ regardless of --target. This is the same root cause as [BUG] --target opencode still writes to .github/prompts/ and .github/agents #488.
2. Skills specifically had a second bug: even when --target cursor was passed, the SkillIntegrator internally called active_targets() without the explicit target, falling back to .github/ by default.

Fix: #494 overhauls the integration dispatch to be fully data-driven. Each target declares its own primitives and directory layout. The dispatch loop only fires what the target supports. For skills, we now thread the explicit targets= list through integrate_package_skill() so --target cursor is actually respected end-to-end.

Verified locally:

$ mkdir .cursor && apm install microsoft/apm-sample-package --target cursor
  |-- 1 rule(s) integrated -> .cursor/rules/
  |-- 1 agents integrated -> .cursor/agents/
  |-- 1 skill(s) integrated -> .cursor/skills/

# .github/ -> not created

This will ship in v0.8.7 once #494 merges. To answer your original question directly: yes, APM fully supports Cursor -- skills, agents, and instructions (as .mdc rules) all deploy to .cursor/. Auto-detection also works: if .cursor/ exists in your project, apm install will target it automatically without needing --target cursor.

Appreciate you taking the time to report this.