SKILL.md--- name: skill-from-github description: Create skills by learning from high-quality GitHub projects model: sonnet --- # Skill from GitHub When users want to accomplish something, search GitHub for quality projects that solve the problem, understand them deeply, then create a skill based on that knowledge. ## When to Use When users describe a task and you want to find existing tools/projects to learn from: - "I want to be able to convert markdown to PDF" - "Help me analyze sentiment in customer reviews" - "I need to generate API documentation from code" ## Workflow ### Step 1: Understand User Intent Clarify what the user wants to achieve: - What is the input? - What is the expected output? - Any constraints (language, framework, etc.)? ### Step 2: Search GitHub Search for projects that solve this problem: ``` {task keywords} language:{preferred} stars:>100 sort:stars ``` **Search tips:** - Start broad, then narrow down - Try different keyword combinations - Include "cli", "tool", "library" if relevant **Quality filters (must meet ALL):** - Stars > 100 (community validated) - Updated within last 12 months (actively maintained) - Has README with clear documentation - Has actual code (not just awesome-list) ### Step 3: Present Options to User Show top 3-5 candidates: ```markdown ## Found X projects that can help ### Option 1: [project-name](github-url) - Stars: xxx | Last updated: xxx - What it does: one-line description - Why it's good: specific strength ### Option 2: ... Which one should I dive into? Or should I search differently? ``` **Wait for user confirmation before proceeding.** ### Step 4: Deep Dive into Selected Project Once user selects a project, thoroughly understand it: 1. **Read README** - Understand purpose, features, usage 2. **Read core source files** - Understand how it works 3. **Check examples** - See real usage patterns 4. **Note dependencies** - What it relies on 5. **Identify key concepts** - The mental model behind it Extract: - Core algorithm/approach - Input/output formats - Error handling patterns - Best practices encoded in the code ### Step 5: Summarize Understanding Present what you learned to user: ```markdown ## Understanding [project-name] ### Core Approach How it solves the problem... ### Key Techniques 1. ... 2. ... ### Limitations - ... ### What I'll encode in the skill - ... Does this look right? Should I proceed to create the skill? ``` **Wait for user confirmation.** ### Step 6: Create Skill via skill-creator Hand off to skill-creator with: 1. **Clear purpose** - What the skill does 2. **Methodology** - The approach learned from the project 3. **Step-by-step process** - Concrete instructions 4. **Quality criteria** - What good output looks like 5. **Common pitfalls** - What to avoid (learned from project issues/docs) **Important:** The skill should encode the *knowledge* from the project, not just wrap the tool.