CLAUDE.md Expert Converter
This skill converts CLAUDE.md developer documentation files into SKILL.md format for the KillerSkills marketplace.
What This Skill Does
Transforms technical project documentation (CLAUDE.md files) from GitHub repositories into properly formatted SKILL.md files that can be published to the KillerSkills marketplace. The skill preserves technical accuracy, code patterns, and architectural context while adapting the structure to the SKILL.md format.
Instructions
When a user provides a CLAUDE.md file or GitHub repository containing one:
1. Analyze the Source Content
Read the entire CLAUDE.md file carefullyIdentify the project type (module, library, framework, platform, etc.)Extract key technical patterns, conventions, and architectural decisionsNote any code examples, file structures, or workflows described2. Determine Appropriate Metadata
**name**: Create a concise, descriptive name (under 50 chars)
Format: "{Project/Tool Name} Development Guide" or "{Project} Technical Assistant"Example: "FoundryVTT Module Developer" or "Next.js Platform Expert"**description**: Write a brief description (under 500 chars)
Focus on what AI assistance the skill providesMention the technology stack and primary use casesExample: "Expert assistant for developing FoundryVTT v12 modules with TypeScript, ApplicationV2 API, and D&D 5e system integration."**category**: Choose the most appropriate category:
`development` - Code development, architecture, patterns`devops` - Deployment, infrastructure, CI/CD`documentation` - Documentation writing and maintenance`testing` - Testing patterns and strategies`security` - Security practices and patterns`other` - If none of the above fit well**tags**: Select 3-10 relevant tags describing:
Primary technology (e.g., "typescript", "nextjs", "foundry-vtt")Domain area (e.g., "game-development", "web-platform", "ai-tools")Key concepts (e.g., "architecture", "patterns", "api-integration")3. Structure the Markdown Body
Organize content into clear sections:
#### **Title and Overview**
Start with `# {Skill Name}`Provide a 2-3 sentence overview of what the skill helps with#### **Project Context**
Summarize the project architectureList key technologies and dependenciesInclude critical file structure if relevant#### **Key Patterns and Conventions**
Document important code patternsInclude TypeScript/language-specific guidelinesShow common workflows and procedures#### **Technical Guidelines**
API usage patternsBuild and deployment proceduresTesting approachesCommon pitfalls and solutions#### **Code Examples**
Include minimal, illustrative code snippetsShow before/after patterns when relevantDemonstrate proper type handling and error management#### **Important Notes**
Security considerationsPerformance tipsBreaking changes or version-specific guidance4. Format for Readability
Use clear headings hierarchy (`##`, `###`, `####`)Keep paragraphs concise (2-4 sentences)Use bullet points for listsFormat code blocks with proper language tags (```typescript, ```bash, etc.)Use inline code for technical terms and file pathsAdd tables for structured data when appropriate5. Preserve Technical Accuracy
Keep all code patterns exactly as shown in sourcePreserve command-line examples verbatimMaintain technical terminologyInclude version numbers and compatibility notesKeep architectural decisions and rationale6. Output Format
Output ONLY the SKILL.md content:
Start with YAML frontmatter (--- delimited)Follow with markdown bodyNO code fences around the entire outputNO explanatory text before or afterExample Usage
**Input**: User provides CLAUDE.md from a FoundryVTT module repository
**Output**: Complete SKILL.md file with:
Frontmatter: name, description, version: "1.0.0", runtimes: ["claude-code"], category, tagsBody: Project overview, architecture, TypeScript patterns, Foundry API usage, build system, common workflows, type handling, code examplesConstraints
Description must be under 500 charactersMaximum 10 tagsOnly use valid category values listed aboveAlways set version to "1.0.0" for new skillsAlways set runtimes to ["claude-code"]Output must be valid YAML frontmatter + MarkdownNo wrapper code fences or explanations in outputQuality Checklist
Before outputting, verify:
[ ] Frontmatter is valid YAML with all required fields[ ] Description is under 500 chars[ ] Category is from approved list[ ] Tags are relevant and specific (3-10 tags)[ ] Code examples use proper language tags[ ] Technical terms are preserved accurately[ ] File paths use inline code formatting[ ] Headings create logical hierarchy[ ] No wrapper code fences around output[ ] Content is self-contained and actionable