manage-commands

Create, validate, and organize Claude slash commands with permission scoping.

4|1|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/lushly-dev/afd --skill manage-commands-lushly-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manage-commands
Source: https://github.com/lushly-dev/afd/tree/main/.claude/skills/manage-commands
Command: npx skills add https://github.com/lushly-dev/afd --skill manage-commands-lushly-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the creation, validation, and organization of Claude slash commands, ensuring consistency, proper permissions, and automated quality checks across your command library.

Core Features & Use Cases

  • Command Creation & Validation: Generate new commands from templates and lint existing ones for errors and security gaps.
  • Namespace Organization: Structure commands logically using directory hierarchies for easy discovery and management.
  • Permission Scoping: Configure allowed-tools with least privilege using precise patterns.
  • Context Injection: Automate context gathering using ! (bash) and @ (file) operators.
  • Lifecycle Hooks: Implement pre- and post-execution logic for validation and formatting.
  • Use Case: When developing a new feature that requires several related slash commands, use this Skill to create them with consistent naming, secure tool access, and proper documentation, ensuring they integrate seamlessly into your existing command structure.

Quick Start

Use the manage-commands skill to create a new slash command for fetching git status.

Frequently Asked Questions about manage-commands

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

FAQPage Schema
How do I create and validate Claude slash commands with consistent frontmatter syntax?

Creating Claude slash commands requires defining frontmatter syntax, variable injection, and tool permissions. This Skill generates commands from templates and lints existing ones, enforcing consistent patterns, automated quality checks, and secure allowed-tools configurations for deterministic execution.

What is the best way to organize slash commands into a logical namespace structure?

Organizing slash commands into namespaces uses directory hierarchies for logical grouping and easy discovery. This Skill manages command namespacing by structuring directory paths systematically, enabling maintainable command libraries that integrate seamlessly into existing project workflows.

How do I automate context injection for slash commands using bash and file operators?

Automating context injection for slash commands utilizes the `!` (bash) and `@` (file) operators to gather dynamic inputs. This Skill configures these context operators to pass variables and runtime data directly into command execution workflows automatically.

Can I scope tool permissions for Claude commands using least privilege patterns?

Scoping tool permissions for Claude commands involves configuring the `allowed-tools` frontmatter with precise patterns. This Skill enforces least privilege access by validating allowed-tools configurations against secure boundaries, preventing unauthorized tool execution during command runtime.

How do lifecycle hooks work for pre- and post-execution validation in slash commands?

Lifecycle hooks for slash commands implement pre- and post-execution logic to validate inputs and format outputs. This Skill manages these lifecycle hooks to ensure deterministic command execution, applying automated checks before triggering commands and formatting results post-execution.

Why are my custom slash commands failing validation due to frontmatter errors?

Slash command validation fails when frontmatter syntax contains errors, security gaps, or improper variable injection. This Skill lints existing commands to identify frontmatter mistakes, missing context operators, and insecure tool permissions, ensuring maintainable command execution.