How do I install the Askit Build Command skill?

Run npx skillmds@latest add product-on-purpose/askit-build-command in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Askit Build Command safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Askit Build Command?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Askit Build Command free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Askit Build Command?

product-on-purpose (@product-on-purpose) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Askit Build Command by product-on-purpose

Name: Askit Build Command
Author: product-on-purpose

Askit Build Command

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.

product-on-purpose b264e71 4 files · 9.3 KB Updated Sep 17, 2026

File contents

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: the LABEL a caller sees beside the slash command, stating what invoking it does. It is not a trigger surface, so do not ask for use-when phrasing (Standard sec 3.2). Skip if provided in context.
Copy templates/command.md into commands/<name>.md.
Fill the frontmatter: description (the caller-facing label: what invoking it does, non-empty; Standard sec 3.2 - NOT the sec 8.1 skill bar, which does not apply to commands); 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.

---name: askit-build-commanddescription: 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.---# askit-build-command## PurposeAuthor 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](../../docs/reference/builder-pattern.md). Authoring depth is in [references/authoring-commands.md](references/authoring-commands.md).## When to useWhen the user asks to create, scaffold, or improve a slash command for a skill.## create mode1. Brief interview: the command name (kebab-case, becomes `/name`), the skill (or workflow) it maps to, optional args, and a description: the LABEL a caller sees beside the slash command, stating what invoking it does. It is not a trigger surface, so do not ask for use-when phrasing (Standard sec 3.2). Skip if provided in context.2. Copy `templates/command.md` into `commands/<name>.md`.3. Fill the frontmatter: `description` (the caller-facing label: what invoking it does, non-empty; Standard sec 3.2 - NOT the sec 8.1 skill bar, which does not apply to commands); `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`.4. Verify the `maps-to` target exists (a skill in `skills/` or a workflow in `_workflows/`).5. Register the command in `library.json` `components.commands` as `{ name, path, version, tier, status }`.6. Assess with `node scripts/evaluate.mjs . --json` and iterate until 0 errors (S3 components index + S7 command-contract must be clean).## improve mode1. Run `node scripts/evaluate.mjs . --json` and read the report.2. 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.3. Re-run evaluate to confirm.## ScopeClaude-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.

Frequently asked questions