Askit capability advisor

Skill product-on-purpose/agent-skills-toolkit/skills/askit-capability-advisor

Toolkit and Standard for building, grading, and scaling cross-agent skill libraries (Claude Code + Codex) to a tiered Bronze/Silver/Gold quality bar.

Install

npx -y skills add product-on-purpose/agent-skills-toolkit --skill askit-capability-advisor

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Reports which component types a target agent can run and recommends a conformance tier before a plugin is built, mapping Claude Code and Codex capabilities to the Advanced Skill Library Standard's component types. Use when choosing agent-targets, checking whether a component is portable across agents, or deciding which tier to aim for.

SKILL.md

3.0 KB, as published. Nobody here has run it

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.

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

Read the target agents (claude, codex, or both).
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).
Recommend a tier path: Bronze (skills + references + AGENTS.md + MCP), Silver (adds subagents, commands, workflows, chain contracts, plugin packaging, the prefix, native manifests), Gold (adds hooks, output styles, self-hosting CI).

check mode

Read the component (or every component in the plugin) and the plugin's declared agent-targets.
For each declared target, report whether the type is plugin-distributable there. Flag a Claude-only type (subagent, output style, statusline) carried under a codex target, since it cannot ship to Codex from a plugin.
Point each flag at the fix: set a per-component agent-targets: [claude] override (sec 3.7), or move the component into a Claude-only plugin.

Scope

Advisory only: it reports capability and recommends a tier; it does not author components (the askit-build-* skills do) or grade conformance (askit-evaluate does). The matrix tracks the agent versions the Standard pins per component (the load-bearing Codex subagent constraint is pinned to Codex CLI v0.135 in sec 3.3); when an agent adds a capability the matrix and this skill update together, so the advice never drifts ahead of what the agents actually support.