askit-capability-advisorlisted

# askit-capability-advisor ## Purpose Tell a maintainer what their target agent supports before they build, so the plan fits the agent rather than failing at release. Two modes: `advise` takes the target agents (`claude`, `codex`, or both), reports which component types are plugin-distributable on each, flags the Claude-only types and the cross-agent asymmetries, and recommends a tier path; `check` takes a specific component or a whole plugin and reports which declared targets can actually run it, so a Claude-only component shipped under a Codex target is caught before release. The full matrix is in [references/capability-matrix.md](references/capability-matrix.md). ## When to use When choosing `agent-targets`, checking whether a component is portable across agents, or deciding which conformance tier to aim for. ## advise mode 1. Read the target agents (`claude`, `codex`, or both). 2. For each, report the plugin-distributable component types and the asymmetries: subagents are Claude-only for plugin distribution (Codex ingests them only via user/project `config.toml`, Standard sec 3.3); output styles are Claude-only and the statusline differs (sec 2.3); a command's Codex form is its backing skill, explicitly invocable, not a separate artifact (sec 3.2); hooks are a Codex subset of Claude's event set (sec 3.5); skills, MCP, and AGENTS.md are portable on both (sec 3.1, 3.9, 3.10). 3. Recommend a tier path: Bronze (skills + references + AGENTS.md + MCP), Silver (adds subagents