From lpclaude-config
Walks through creating a complete Claude Code skill: extracts intent, scaffolds directory structure, generates SKILL.md with discovery-optimized metadata, and configures optional reference files.
How this command is triggered — by the user, by Claude, or both
Slash command
/lpclaude-config:create [description of what the skill should do] (skill name optional - can be embedded in description or will be generated)skills/This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
## Skill Creation Process Parse the user's input to extract: 1. **Skill description**: What capability the skill should provide 2. **Skill name**: Extract from patterns like "called [name]", "named [name]", or generate from description (lowercase-hyphenated) 3. **Scope**: Default to project-local (`.claude/skills/`) unless "global", "personal", or "all projects" mentioned ## Requirements Analysis From the description, determine: - Core capability and when Claude should use it - Whether tool restrictions are appropriate (`allowed-tools`) - Supporting files needed based on keywords: - "r...
Parse the user's input to extract:
.claude/skills/) unless "global", "personal", or "all projects" mentionedFrom the description, determine:
allowed-tools)reference.mdexamples.mdscripts/ directory with placeholdertemplates/ directory with placeholderSkills are directories containing a SKILL.md file plus optional supporting resources:
skill-name/
|-- SKILL.md (required - main instructions)
|-- reference.md (optional - detailed documentation)
|-- examples.md (optional - usage examples)
|-- scripts/ (optional - utility scripts)
| |-- README.md (placeholder explaining purpose)
|-- templates/ (optional - reusable templates)
|-- README.md (placeholder explaining purpose)
---
name: skill-name
description: What it does AND when Claude should use it (critical for discovery)
allowed-tools: Tool1, Tool2 # Optional - only include if restrictions needed
---
# Skill Name
## Overview
Brief explanation of the skill's purpose and value.
## Instructions
Step-by-step guidance for Claude when this skill is active.
## When to Use
Specific triggers and contexts where this skill applies.
## References
Links to supporting files if they exist.
The description field is critical for Claude's automatic discovery. A good description:
Includes WHAT the skill does:
Includes WHEN to use it:
Bad examples (too vague):
Only add allowed-tools when the skill should be limited:
Read-only skills:
allowed-tools: Read, Grep, Glob
Analysis skills (no file modification):
allowed-tools: Read, Grep, Glob, Bash(git log:*), Bash(git diff:*)
Omit allowed-tools for skills that need full capabilities - Claude will ask for permission as normal.
mkdir -p [scope]/skills/[skill-name]
# [Skill Name] Reference
## Detailed Documentation
[Add comprehensive reference material here]
## API/Tool Reference
[Add relevant API documentation or tool references]
## Best Practices
[Add domain-specific best practices]
# [Skill Name] Examples
## Basic Usage
[Add simple examples]
## Advanced Usage
[Add complex examples with explanations]
## Common Patterns
[Add frequently used patterns]
# Scripts
This directory contains utility scripts for the [skill-name] skill.
## Available Scripts
- Add your scripts here
## Usage
Describe how Claude should use these scripts.
# Templates
This directory contains reusable templates for the [skill-name] skill.
## Available Templates
- Add your templates here
## Usage
Describe how Claude should use these templates.
After creating the skill, remind the user:
$ARGUMENTS
npx claudepluginhub lpasqualis/lpclaude --plugin lpclaude-config/create-skillCreates a new Claude Code skill directory from skill name, description/purpose, and optional documentation URLs. Generates SKILL.md with YAML frontmatter, quick start guide, critical rules, and known issues prevention.
/create-skillCreates a new Claude Skill with YAML frontmatter in personal or project directory. Validates inputs, checks existence, analyzes for bundled resources, and adds scripts/, references/, or assets/ directories as needed.
/createCreates a new beads issue interactively or via title, type (bug/feature/task/epic/chore/decision), and priority args. Uses beads MCP create tool, shows ID/details, offers linking.
/createProduces SEO/GEO content end-to-end: brief, draft, series, refresh, and CMS-neutral publish package from one entry point.
/createLaunches Socratic workflow designer subagent to create orchestration workflows from natural language descriptions using interactive questioning. Accepts optional initial description argument.
/createCreates a new scaffold template in .scaffold/<name> with scaffold.yaml config, Go template files for project or template scaffolds, and validates via lint and dry-run generation.