AugmentClaude

Skill Builder

Convert documentation, repos, PDFs, and videos into AI-ready skills automatically.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.

    This copies the whole skill folder into ~/.claude/skills/skill-builder-yusufkaraaslan/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

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.

What this skill does

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 PatternSource TypeTool to Use
https://... (not GitHub/YouTube)Documentationscrape_docs
owner/repo or github.com/...GitHubscrape_github
*.pdfPDFscrape_pdf
YouTube/Vimeo URL or video fileVideoscrape_video
Local directory pathCodebasescrape_codebase
*.ipynb, *.html, *.yaml (OpenAPI), *.adoc, *.pptx, *.rss, *.1-.8Variousscrape_generic
JSON config fileUnifiedUse 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

Related skills