Claude Code Instructions Converter
Converts CLAUDE.md instruction files from GitHub repositories into the structured SKILL.md format used by the KillerSkills marketplace.
What This Skill Does
This skill analyzes CLAUDE.md files (instruction files for Claude Code) and transforms them into properly formatted SKILL.md files with YAML frontmatter and structured markdown content. It extracts key information like project overview, architecture details, development workflows, and coding guidelines.
Instructions for AI Agent
When converting a CLAUDE.md file to SKILL.md format, follow these steps:
1. Analyze the Source Content
Read through the entire CLAUDE.md file carefullyIdentify the main project type (web app, static site, API, CLI tool, etc.)Extract key technologies, frameworks, and tools mentionedNote any specific workflows, commands, or processes describedIdentify the target audience and use cases2. Create YAML Frontmatter
Structure the frontmatter with these required fields:
```yaml
---
name: "Descriptive Skill Name (under 60 chars)"
description: "Brief description under 500 characters explaining what this skill helps with"
version: "1.0.0"
runtimes: ["claude-code"]
category: development
tags:
- relevant-tag-1
- relevant-tag-2
- max-10-tags
---
```
**Category Selection:**
`development` - For coding, architecture, frameworks`devops` - For deployment, infrastructure, CI/CD`documentation` - For docs-focused projects`testing` - For QA, testing frameworks`security` - For security-focused contexts**Tag Guidelines:**
Include primary programming language(s)Include main framework(s)Include project type keywordsInclude relevant workflow keywordsMax 10 tags, prioritize most relevant3. Structure the Markdown Body
Organize content into clear sections:
#### Title and Overview
```markdown
[Skill Name]
Clear 1-2 sentence description of what working with this project involves.
```
#### Project Context Section
Extract and summarize:
Project type and purposeTechnology stackKey architectural decisionsDomain/business context if relevant#### Development Workflow Section
Document:
Common commands (install, build, test, deploy)Development server setupBuild processesTesting procedures#### Architecture and Structure Section
Describe:
Directory structureKey files and their purposesModule organizationConfiguration files#### Coding Guidelines Section
Extract:
Code style preferencesNaming conventionsBest practicesFramework-specific patternsCommon pitfalls to avoid#### Key Implementation Details
Highlight:
Critical technical detailsIntegration patternsAPI usageDatabase schema infoExternal services4. Content Transformation Guidelines
**Keep:**
Specific commands and workflowsArchitecture detailsTechnical constraintsBest practicesTool configurations**Simplify:**
Long company background stories (condense to 1-2 sentences)Extensive content checklists (extract principles)Detailed marketing copy (focus on technical implications)**Remove:**
Proprietary business informationInternal company detailsPersonal contact informationSpecific client names (unless public references)**Generalize:**
Project-specific names to [Project Name] placeholders where helpfulSpecific paths to pattern examplesHardcoded values to configuration patterns5. Formatting Standards
Use `##` for main sectionsUse `###` for subsectionsUse code blocks with language tags for commandsUse bullet points for listsUse tables for structured comparison dataKeep paragraphs concise (2-4 sentences)Use bold for emphasis on key termsUse inline code for file names, commands, variables6. Quality Checklist
Before finalizing, verify:
[ ] YAML frontmatter is valid and complete[ ] Description is under 500 characters[ ] Name is descriptive and under 60 characters[ ] All sections have clear headings[ ] Code examples are properly formatted[ ] No proprietary/sensitive information included[ ] Content is actionable for an AI agent[ ] Markdown is properly structured[ ] Tags are relevant and within limit (max 10)7. Output Format
**CRITICAL:** Output ONLY the complete SKILL.md file content. Do not wrap in code fences. Do not add explanations before or after. The output should start with `---` (frontmatter) and end with the last line of markdown content.
Examples of Good Conversions
**Example 1: Static Site Project**
```
name: "Static HTML Corporate Site Development"
category: development
tags: [html, css, javascript, static-site, github-pages]
```
**Example 2: Full-Stack App**
```
name: "Next.js Full-Stack App Development"
category: development
tags: [nextjs, react, typescript, postgresql, drizzle-orm]
```
**Example 3: DevOps Context**
```
name: "Railway Multi-Environment Deployment"
category: devops
tags: [railway, deployment, postgres, environment-management]
```
Important Notes
Always set `runtimes: ["claude-code"]` unless explicitly told otherwiseFocus on technical guidance, not business contextMake content reusable beyond the specific project when possiblePreserve exact commands and file paths that are generally applicableRemove or genericize company-specific detailsEnsure the skill would be useful for similar projects, not just the source project