cli-wiring

Identify and route unimplemented CLI commands using wiring checklists.

Updated May 10, 2026
One-click install
npx skills add https://github.com/AshleyHollis/agentic-identity-lab --skill cli-wiring-ashleyhollis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cli-wiring
Source: https://github.com/AshleyHollis/agentic-identity-lab/tree/main/.copilot/skills/cli-wiring
Command: npx skills add https://github.com/AshleyHollis/agentic-identity-lab --skill cli-wiring-ashleyhollis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the issue of commands being implemented in a CLI but not correctly routed, which can lead to inefficiencies and missed functionality in development processes.

Core Features & Use Cases

  • Command Identification: Identifies commands that are implemented but not routed in the CLI entry point.
  • Checklist for Command Addition: Provides a step-by-step checklist for adding new CLI commands, including creating command files, adding routing blocks, and updating help text.
  • Wiring Patterns: Offers guidance on different wiring patterns for various command types, such as standard commands, placeholder commands, utility modules, and subcommands.
  • Common Import Pattern: Recommends a dynamic import pattern for command modules to maintain fast startup times.

Quick Start

Run the skill to review the checklist for adding a new CLI command and follow the steps outlined in the documentation.

Frequently Asked Questions about cli-wiring

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

FAQPage Schema
Why are my implemented CLI commands not showing up in the development workflow?

Commands implemented in a CLI may not be correctly routed in the entry point, causing them to be missed. This Skill identifies unrouted commands and provides a checklist to integrate them into the CLI workflow properly.

How do I add a new command to a CLI step by step?

To add a new CLI command, follow a checklist that includes creating the command file, adding the appropriate routing block in the entry point, and updating the help text to ensure the command is fully wired.

What is the best way to structure CLI command routing for different command types?

CLI command routing requires different wiring patterns based on the command type. You should use specific guidelines for standard commands, placeholder commands, utility modules, and subcommands to ensure efficient integration.

How can I maintain fast startup times when wiring multiple command modules into a CLI?

To maintain fast startup times during CLI command routing, you should use a dynamic import pattern for command modules. This delays loading command code until it is actually needed by the user.

Do I need any specific frameworks to use dynamic imports for CLI command routing?

No specific frameworks are required to use dynamic imports for CLI command routing. This Skill provides structured guidelines and common patterns that can be applied directly to your development workflow using standard scripts.

When should I not use standard command routing patterns in my CLI?

You should deviate from standard routing patterns when dealing with placeholder commands or utility modules. These command types require specific wiring patterns to prevent them from being executed as standard commands.