example-command

Parses user-invoked skill-command arguments with controlled tool access via SKILL.md entry point.

1|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/victorjoshi9/content--1- --skill example-command-victorjoshi9
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: example-command
Source: https://github.com/victorjoshi9/content--1-/tree/main/.claude/plugins/marketplaces/claude-plugins-official/plugins/example-plugin/skills/example-command
Command: npx skills add https://github.com/victorjoshi9/content--1- --skill example-command-victorjoshi9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It shows how to package a user-invoked skill as a self-contained command that can reliably accept arguments, use approved tools, and return a clear result.

Core Features & Use Cases

  • Argument Handling: Demonstrates how a skill reads required and optional arguments from the user.
  • Controlled Tool Access: Illustrates how to declare allowed tools so a command can work with fewer permission prompts.
  • Slash Command Layout: Serves as a reference for the skills/<name>/SKILL.md format used by user-invoked commands.

Quick Start

Invoke the example-command skill with the arguments you want the assistant to parse and execute.

Frequently Asked Questions about example-command

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

FAQPage Schema
How do I create a slash command that accepts arguments from users?

To create a slash command that accepts arguments, you package a self-contained SKILL.md entry point with frontmatter metadata, define argument hints, and specify allowed-tools for deterministic command handling.

What is the SKILL.md format for building user-invoked skills?

The SKILL.md format for user-invoked skills requires frontmatter metadata, argument hints, and allowed-tools settings to support command discovery and controlled tool access within the skills directory.

How do I control tool access and reduce permission prompts for a slash command?

You control tool access for a slash command by declaring allowed-tools in the frontmatter metadata, which ensures the command executes with fewer permission prompts during processing.

Can I use a self-contained skill command with optional and required arguments?

Yes, a self-contained skill command reads both required and optional arguments from the user by defining argument hints in the SKILL.md frontmatter for parsing and execution.

Why does my slash command workflow need frontmatter metadata?

Your slash command workflow needs frontmatter metadata to enable discovery, define argument hints, and set allowed-tools, which supports deterministic command handling and controlled tool access.