Askit build command

Skill product-on-purpose/agent-skills-toolkit/skills/askit-build-command

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-build-command

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

Creates and improves Claude slash commands (commands/<name>.md) that map to a skill, to the Advanced Skill Library Standard. Use when you need to give a skill an explicit /command entry point or raise an existing command's conformance.

SKILL.md

2.5 KB, as published. Nobody here has run it

askit-build-command

Purpose

Author conformant commands. Two modes: create scaffolds a new commands/<name>.md that maps to an existing skill; improve raises an existing command toward the quality bar. On Codex a command is realized as its backing skill (Standard sec 3.2 parity), so this skill emits no Codex artifact. Follows the shared builder pattern. Authoring depth is in references/authoring-commands.md.

When to use

When the user asks to create, scaffold, or improve a slash command for a skill.

create mode

Brief interview: the command name (kebab-case, becomes /name), the skill (or workflow) it maps to, optional args, and a description mirroring the backing skill's intent. Skip if provided in context.
Copy templates/command.md into commands/<name>.md.
Fill the frontmatter: description (what AND when; Standard sec 8.1); maps-to equal to the backing skill or workflow name; optional argument-hint/allowed-tools/model; metadata.version. The filename is the command name (no name key). Write a body that invokes the backing skill, passing $ARGUMENTS.
Verify the maps-to target exists (a skill in skills/ or a workflow in _workflows/).
Register the command in library.json components.commands as { name, path, version, tier, status }.
Assess with node scripts/evaluate.mjs . --json and iterate until 0 errors (S3 components index + S7 command-contract must be clean).

improve mode

Run node scripts/evaluate.mjs . --json and read the report.
For each finding: an S3 error -> declare/undeclare the command in components.commands to match disk; an S7 error -> add the missing maps-to, fix a maps-to that does not resolve, or add a missing description. For any other finding, read its message and apply the fix it states.
Re-run evaluate to confirm.

Scope

Claude-native: a command is commands/<name>.md. Codex realizes a command as its backing skill (Standard sec 3.2), so there is no Codex artifact to generate; the backing skill is the invocable form on Codex. A command MUST map to exactly one skill or workflow.