add-command

Scaffold Claude Code slash command files and append workflow stubs to SKILL.md.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/shawn-sandy/agentic-acss-plugins --skill add-command-shawn-sandy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-command
Source: https://github.com/shawn-sandy/agentic-acss-plugins/tree/main/.agents/skills/add-command
Command: npx skills add https://github.com/shawn-sandy/agentic-acss-plugins --skill add-command-shawn-sandy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating new Claude Code slash commands for a plugin is repetitive and easy to miss required wiring, causing inconsistent structure and missing safety/guardrails.

Core Features & Use Cases

  • Validates command inputs: Ensures the plugin exists and prevents overwriting an existing command unless the workflow explicitly allows it.
  • Guides the user through required command scaffolding: Prompts for a description, argument hint, allowed tools, and the owning skill workflow to reference.
  • Creates the command entry file and skill stub: Generates commands/<command-name>.md and appends a new ## /<command-name> section to the owning skill’s SKILL.md for follow-up implementation.

Quick Start

Use the /add-command workflow to scaffold a new command by telling your AI: “/add-command acss-kit theme-export”.

Frequently Asked Questions about add-command

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a new Claude Code slash command for an existing plugin?

To create a Claude Code slash command, use the /add-command workflow to scaffold a commands/<command-name>.md file with YAML frontmatter and append a corresponding stub workflow section to the owning skill's SKILL.md.

What is the process for registering markdown-as-source skills in a plugin marketplace?

Registering markdown-as-source skills involves generating a command entry file with consistent YAML frontmatter metadata and updating the owning skill's SKILL.md to include the new slash command workflow stub for follow-up implementation.

How do I prevent overwriting an existing command file when scaffolding plugin commands?

Preventing overwrites during command scaffolding is enforced by validating command inputs and refusing unsafe overwrites unless the workflow explicitly allows it by passing a force parameter.

Does the command scaffolding workflow require a clean git tree before generating files?

Yes, the command scaffolding workflow enforces refusal behavior for dirty git trees to ensure safe file generation and prevent accidental loss of uncommitted changes during the plugin scaffolding process.

What inputs do I need to provide when scaffolding a new plugin slash command?

Scaffolding a new plugin slash command requires providing a description, argument hint, allowed tools, and the owning skill workflow reference to ensure the generated markdown file has complete metadata.

Can I use the command scaffolding workflow if the target plugin directory does not exist?

No, the command scaffolding workflow validates that the plugin exists before proceeding to ensure the commands/<command-name>.md file and SKILL.md stub are generated in the correct plugin directory structure.