CLAUDE.md to SKILL.md Converter

Converts GitHub repository CLAUDE.md instruction files into properly formatted SKILL.md files for the Claude Code skills marketplace.

Purpose

CLAUDE.md files provide context and guidance to Claude Code when working with specific repositories. This skill transforms those instructions into the SKILL.md format used by the KillerSkills marketplace, preserving all technical details while adding proper frontmatter and structure.

Instructions

When converting a CLAUDE.md file to SKILL.md format:

1. **Analyze the source content**

- Read through the entire CLAUDE.md file

- Identify the project type, tech stack, and primary purpose

- Note key commands, architecture patterns, and conventions

- Extract testing strategies and debugging approaches

2. **Generate YAML frontmatter**

- `name`: Create a concise skill name (under 60 chars) describing the repository/project

- `description`: Write a brief description (under 500 chars) summarizing what the skill helps with

- `version`: Set to "1.0.0"

- `runtimes`: Use the provided runtime array (typically `["claude-code"]`)

- `category`: Choose from: development, devops, writing, data, design, testing, security, documentation, automation, other

- `tags`: Extract 3-10 relevant tags from the content (tech stack, frameworks, languages, concepts)

3. **Structure the markdown body**

- Start with a clear H1 title (# Skill Name)

- Add a brief overview section describing the project

- Preserve all command blocks with proper markdown formatting

- Maintain architecture explanations and design patterns

- Keep all code examples with syntax highlighting

- Preserve file references and directory structures

- Include testing and debugging sections

- Add any important conventions or guidelines

4. **Preserve technical accuracy**

- Keep all commands exactly as written

- Maintain code snippets verbatim

- Preserve file paths and references

- Keep configuration details accurate

- Maintain language-specific conventions

5. **Format for readability**

- Use proper markdown headers (H2, H3, H4)

- Format commands in code blocks with language tags

- Use bullet points for lists

- Use tables for structured data when appropriate

- Add horizontal rules to separate major sections

6. **Output requirements**

- Output ONLY the SKILL.md content (frontmatter + body)

- No surrounding code fences

- No explanatory text before or after

- No comments about the conversion process

Example Output Structure

```

---

name: "Project Name Assistant"

description: "Brief description of what this skill helps with"

version: "1.0.0"

runtimes:

- claude-code

category: development

tags:

- tech-stack

- framework

- language

---

Project Name Assistant

Overview paragraph describing the project and what this skill helps with.

Development Commands

Setup

```bash

Commands here

```

Architecture

Detailed architecture explanations...

Key Patterns

Important patterns and conventions...

Testing

Testing strategies...

Important Files

Reference to key files...

```

Quality Guidelines