Skill Builder Agent Skill
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.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/yusufkaraaslan/Skill_Seekers --skill skill-builderThe instruction itself
9 sections, as written by the authorSkill 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
- Detect source type from the user's input
- Generate or fetch config using
generate_configorfetch_configif needed - Estimate scope with
estimate_pagesfor documentation sites - Scrape the source using the appropriate scraping tool
- Enhance with
enhance_skillif the user wants AI-powered improvements - Package with
package_skillfor the target platform - Export to vector DB if requested using
export_to_*tools
Available MCP Tools
Config Management
generate_config— Generate a scraping config from a URLlist_configs— List available preset configsvalidate_config— Validate a config file
Scraping (use based on source type)
scrape_docs— Documentation sitesscrape_github— GitHub repositoriesscrape_pdf— PDF filesscrape_video— Video transcriptsscrape_codebase— Local code analysisscrape_generic— Jupyter, HTML, OpenAPI, AsciiDoc, PPTX, RSS, manpage, Confluence, Notion, chat
Post-processing
enhance_skill— AI-powered skill enhancementpackage_skill— Package for target platformupload_skill— Upload to platform APIinstall_skill— End-to-end install workflow
Advanced
detect_patterns— Design pattern detection in codeextract_test_examples— Extract usage examples from testsbuild_how_to_guides— Generate how-to guides from testssplit_config— Split large configs into focused skillsexport_to_weaviate,export_to_chroma,export_to_faiss,export_to_qdrant— Vector DB export
Other skills for the same job
different authors, same section of the catalogue
This skill should be used when the user asks about "plugin settings", "store plugin configuration", "user-configurable plugin", ".local.md files", "plugin state files", "read YAML frontmatter", "per-project plugin settings", or wants to make plugin behavior configurable. Documents the .claude/plugin-name.local.md pattern for storing plugin-specific configuration with YAML frontmatter and markdown content.
-Automatically convert documentation websites, GitHub repositories, and PDFs into Claude AI skills in minutes.
This skill should be used when the user asks about "plugin settings", "store plugin configuration", "user-configurable plugin", ".local.md files", "plugin state files", "read YAML frontmatter", "per-project plugin settings", or wants to make plugin behavior configurable. Documents the .claude/plugin-name.local.md pattern for storing plugin-specific configuration with YAML frontmatter and markdown content.
Standardize how an AI-collaboration project turns work into reusable knowledge. Use when initializing or retrofitting Project Cairn in a project, recording progress after meaningful work, maintaining AGENTS/CLAUDE/cairn docs, auditing project knowledge for drift or missing records, pulling and citing external knowledge, or graduating validated project experience into a reusable knowledge base.
Persistent memory and context management for AI agents using OpenContext. Keep context across sessions/repos/dates, store conclusions, and provide document search workflows.
> PARA method knowledge management for Obsidian vaults. Use this skill whenever the user wants to organize notes using PARA (Projects, Areas, Resources, Archive), classify a note into a PARA category, route a note to the right vault folder, normalize frontmatter fields, run a PARA hygiene review, suggest archiving, audit vault structure, or process new knowledge inputs into an existing PARA-based vault. Also trigger when the user mentions inbox processing, vault cleanup, note classification, PARA review, or asks "where does this note belong?". Works with existing Obsidian skills (obsidian-markdown, obsidian-cli) — never replaces them.
Keeps implementation and specs in sync. Use when working on a feature that has a spec in .agents/specs/, when the user says /spec, or when starting implementation of a documented feature. Also use when the user asks to verify implementation against a spec or update a spec after changes.
Build and query AI-powered knowledge bases from claude-mem observations. Use when users want to create focused "brains" from their observation history, ask questions about past work patterns, or compile expertise on specific topics.
How to use it
Take yusufkaraaslan/skill_seekers-skill-builder from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.