skill-seekerslisted

# Skill Seekers — Documentation → Claude Skill Converter Convert any documentation source into a Claude skill. ## Process ### Step 1 — Analyze the Source Before writing anything, understand what the source contains: - What is the primary use case? - What are the most common tasks a developer would do with this? - What are the non-obvious patterns / gotchas that aren't in the happy path? - What does someone need to know that they *can't* easily find by searching? ### Step 2 — Determine Skill Type Choose the right skill structure based on the source: | Source Type | Best Skill Structure | |-------------|---------------------| | API Reference | Cheat sheet + common patterns | | Framework docs | Workflow guide + gotchas | | GitHub README | Quickstart + architecture notes | | Tutorial | Distilled steps + adaptation notes | | Design system | Component usage + constraints | ### Step 3 — Extract What Matters Prioritize: 1. **Patterns** — the idiomatic way to do the most common 20% of tasks 2. **Gotchas** — what breaks, what's counterintuitive, what the docs bury 3. **Configuration** — the parameters/options that actually matter 4. **Examples** — concrete code or step sequences, not conceptual explanations Do NOT include: - Comprehensive coverage of every feature (skill context is limited) - Content that's easily searchable (basic concepts, definitions) - Installation instructions (one-time, not recurring) ### Step 4 — Write the SKILL.md Template: ```markdown --- name: [kebab