Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.
git clone https://github.com/yusufkaraaslan/Skill_Seekers.git--- name: skill-builder description: Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources. --- # Skill Builder You have access to the Skill Seekers MCP server which provides 40 tools for converting knowledge sources into AI-ready skills. ## When to Use This Skill Use this skill when the user: - Wants to create an AI skill from a documentation site, GitHub repo, PDF, video, or other source - Needs to convert documentation into a format suitable for LLM consumption - Wants to update or sync existing skills with their source documentation - Needs to export skills to vector databases (Weaviate, Chroma, FAISS, Qdrant) - Asks about scraping, converting, or packaging documentation for AI ## Source Type Detection Automatically detect the source type from user input: | Input Pattern | Source Type | Tool to Use | |---------------|-------------|-------------| | `https://...` (not GitHub/YouTube) | Documentation | `scrape_docs` | | `owner/repo` or `github.com/...` | GitHub | `scrape_github` | | `*.pdf` | PDF | `scrape_pdf` | | YouTube/Vimeo URL or video file | Video | `scrape_video` | | Local directory path | Codebase | `scrape_codebase` | | `*.ipynb`, `*.html`, `*.yaml` (OpenAPI), `*.adoc`, `*.pptx`, `*.rss`, `*.1`-`.8` | Various | `scrape_generic` | | JSON config file | Unified | Use config with `scrape_docs` | ## Recommended Workflow 1. **Detect source type** from the user's input 2. **Generate or fetch config** using `generate_config` or `fetch_config` if needed 3. **Estimate scope** with `estimate_pages` for documentation sites 4. **Scrape the source** using the appropriate scraping tool 5. **Enhance** with `enhance_skill` if the user wants AI-powered improvements 6. **Package** with `package_skill` for the target platform 7. **Export to vector DB** if requested using `export_to_*` tools ## Available MCP Tools ### Config Management - `generate_config` — Generate a scraping config from a URL - `list_configs` — List available preset configs - `validate_config` — Validate a config file ### Scraping (use based on source type) - `scrape_docs` — Documentation sites - `scrape_github` — GitHub repositories - `scrape_pdf` — PDF files - `scrape_video` — Video transcripts - `scrape_codebase` — Local code analysis - `scrape_generic` — Jupyter, HTML, OpenAPI, AsciiDoc, PPTX, RSS, manpage, Confluence, Notion, chat ### Post-processing - `enhance_skill` — AI-powered skill enhancement - `package_skill` — Package for target platform - `upload_skill` — Upload to platform API - `install_skill` — End-to-end install workflow ### Advanced - `detect_patterns` — Design pattern detection in code - `extract_test_examples` — Extract usage examples from tests - `build_how_to_guides` — Generate how-to guides from tests - `split_config` — Split large configs into focused skills - `export_to_weaviate`, `export_to_chroma`, `export_to_faiss`, `export_to_qdrant` — Vector DB export
[{"step":"Prepare your source material. Gather all relevant files (e.g., for a repo: README.md, code comments, config files; for a PDF: scan or upload the document). Ensure the source is accessible (uploaded, linked, or pasted).","tip":"For videos, provide a transcript or timestamped notes. For PDFs, ensure text is extractable (not scanned images)."},{"step":"Use the prompt template to specify the source type, topic, and task. Replace [SOURCE_TYPE], [TOPIC], [TASK], and [SPECIFIC_OUTPUT_FORMAT] with your requirements. Paste or link the source material directly into the prompt.","tip":"Be specific with [TASK]. For example, 'summarize key points' vs. 'generate a step-by-step guide'. Include constraints like 'in under 200 words' or 'focus on security risks'."},{"step":"Run the prompt in your AI tool (e.g., Claude, ChatGPT). Review the generated skill structure and output format. Test the skill with sample queries to validate accuracy.","tip":"If the output is too generic, refine the prompt by adding more details about the desired tone, audience, or specific sections to prioritize (e.g., 'focus on the 'Deployment' section')."},{"step":"Iterate and refine. Use the AI's output as a starting point, then manually adjust the skill's logic or add missing context. For example, if the skill misses a critical feature, regenerate with: 'Include a section on [MISSING_FEATURE] based on the 'Advanced Config' chapter.'","tip":"For complex sources (e.g., multi-repo projects), break the task into smaller prompts. Start with one repo or document, then combine results."},{"step":"Deploy the skill. Copy the generated skill code or instructions into your AI platform (e.g., LangChain, custom API). Configure any necessary integrations (e.g., database connections, API keys).","tip":"Save the prompt template for future use. Store it in a knowledge base or template library to quickly rebuild skills for similar sources."}]
No install command available. Check the GitHub repository for manual installation instructions.
git clone https://github.com/yusufkaraaslan/Skill_Seekers/tree/development/skills/skill-seekersCopy the install command above and run it in your terminal.
Launch Claude Code, Cursor, or your preferred AI coding agent.
Use the prompt template or examples below to test the skill.
Adapt the skill to your specific use case and workflow.
I have [SOURCE_TYPE: documentation/repo/PDF/video/other] containing information about [TOPIC]. Use Skill Seekers to automatically detect the source type and build an AI skill that can [TASK: answer questions/extract insights/summarize/generate reports/etc.]. Include [SPECIFIC_OUTPUT_FORMAT] in the generated skill. Source: [PASTE_OR_LINK_SOURCE]
Based on the uploaded GitHub repository for 'Project Phoenix: AI-Powered Customer Support Automation,' Skill Seekers detected a Python-based documentation structure with YAML configs, Markdown READMEs, and code comments. The generated skill includes: 1. **Core Function**: A conversational agent that answers questions about the project's architecture and setup instructions. 2. **Key Components**: - **Source Analyzer**: Identifies Python files, requirements.txt, and config files to extract technical details. - **Intent Mapper**: Maps user queries to specific functions (e.g., 'How do I install dependencies?' → runs `pip install -r requirements.txt` simulation). - **Context Builder**: Pulls from README sections like 'Quick Start' and 'API Reference' to provide accurate responses. 3. **Output Example**: **User**: 'What are the prerequisites for running Project Phoenix?' **AI**: 'Project Phoenix requires Python 3.9+, Docker, and the following dependencies (verified from requirements.txt): - Flask==2.3.2 - Transformers==4.30.2 - LangChain==0.0.265 For setup, run: ```bash git clone https://github.com/org/phoenix.git cd phoenix pip install -r requirements.txt docker-compose up -d ``` Need help with a specific error? Share the traceback!'
skills-collection
Take a free 3-minute scan and get personalized AI skill recommendations.
Take free scan