use-command-template
Use Skill Template
Create a new Claude Code skill following established patterns.
Note: Commands have been deprecated in favor of skills. This skill creates properly formatted SKILL.md files.
Execution Steps
Consult ../python3-development/references/python3-standards.md when applying shared architecture, typing, testing, or CLI rules; full standards, graphs, and amendment process are documented there.
1. Determine Skill Type
- Parse skill purpose from arguments
- Identify appropriate category (testing/development/analysis/quality)
- Choose suitable skill name (kebab-case format)
2. Apply Template
Create SKILL.md with required structure:
---
name: skill-name
description: 'This skill should be used when the user asks to "specific trigger 1", "specific trigger 2", "specific trigger 3". Brief description of what the skill does.'
version: "1.0.0"
last_updated: "YYYY-MM-DD"
user-invocable: true # if user can invoke directly
argument-hint: "<argument_description>" # if accepts arguments
---
# Skill Title
Brief overview of the skill's purpose.
## When to Use
- Trigger condition 1
- Trigger condition 2
- Trigger condition 3
## Process/Instructions
### Step 1: First Action
{Details}
### Step 2: Second Action
{Details}
## Output Format
{Expected output structure}
## Related Skills
- **related-skill-1**: Description
- **related-skill-2**: Description
3. Skill Directory Structure
Create skill in appropriate location:
plugins/{plugin-name}/skills/{skill-name}/
└── SKILL.md
Skills must be directly under skills/ — subdirectory nesting is not supported and causes skills to silently fail to register. Do not add a skills key to plugin.json — auto-discovery handles registration.
Best Practices
Naming:
- Use kebab-case for directory and skill names
- Use clear verb-noun format when applicable
- Keep names concise but descriptive
Description:
- Use third person: "This skill should be used when..."
- Include specific trigger phrases users would say
- List 3-5 concrete examples of when to invoke
Content:
- Keep skills focused on single responsibility
- Include at least one example usage
- Define clear output format
- Reference related skills
Example Usage
/python3-development:use-command-template analyze API endpoints for rate limiting
/python3-development:use-command-template validate database migrations for safety
/python3-development:use-command-template generate Pydantic classes from schema
Migration Note
If migrating from old command format:
| Old Format | New Format |
|---|---|
title: |
name: |
command_type: |
(removed - use directory structure) |
related_docs: |
(use markdown links in content) |
@include |
(copy content directly or use references/) |
More from jamie-bitflight/claude_skills
perl-lint
This skill should be used when the user asks to lint Perl code, run perlcritic, check Perl style, format Perl code, run perltidy, or mentions Perl Critic policies, code formatting, or style checking.
24brainstorming-skill
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or when users request help with ideation, marketing, and strategic planning. Explores user intent, requirements, and design before implementation using 30+ research-validated prompt patterns.
11design-anti-patterns
Enforce anti-AI UI design rules based on the Uncodixfy methodology. Use when generating HTML, CSS, React, Vue, Svelte, or any frontend UI code. Prevents "Codex UI" — the generic AI aesthetic of soft gradients, floating panels, oversized rounded corners, glassmorphism, hero sections in dashboards, and decorative copy. Applies constraints from Linear/Raycast/Stripe/GitHub design philosophy: functional, honest, human-designed interfaces. Triggers on: UI generation, dashboard building, frontend component creation, CSS styling, landing page design, or any task producing visual interface code.
7python3-review
Comprehensive Python code review checking patterns, types, security, and performance. Use when reviewing Python code for quality issues, when auditing code before merge, or when assessing technical debt in a Python codebase.
7hooks-guide
Cross-platform hooks reference for AI coding assistants — Claude Code, GitHub Copilot, Cursor, Windsurf, Amp. Covers hook authoring in Node.js CJS and Python, per-platform event schemas, inline-agent hooks and MCP in agent frontmatter, common JSON I/O, exit codes, best practices, and a fetch script to refresh docs from official sources. Use when writing, reviewing, or debugging hooks for any AI assistant.
7agent-creator
Create high-quality Claude Code agents from scratch or by adapting existing agents as templates. Use when the user wants to create a new agent, modify agent configurations, build specialized subagents, or design agent architectures. Guides through requirements gathering, template selection, and agent file generation following Anthropic best practices (v2.1.63+).
6