Skip to content
FunCoding

Search

Search docs, Skills and MCP

skill-builder

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.

浏览器自动化15kdistribution/claude-plugin/skills/skill-builder/SKILL.md

Install

Send this to Claude Code, Codex or Cursor. The agent checks the Skill for safety first and installs it only after you confirm.

读取 https://funcoding.ai/skills/yusufkaraaslan/skill_seekers/skill-builder/install.md ,按里面的步骤帮我安装这个 Skill。

SKILL.md

Skill Builder

This skill uses the Skill Seekers MCP server, which provides 40 tools for converting knowledge sources into AI-ready skills. If the MCP tools are not available, use the CLI fallback at the bottom of this file instead — do not stop.

Prerequisites

The MCP tools below only work when the Skill Seekers MCP server is connected:

  1. Install the package: pip install "skill-seekers[mcp]"
  2. Connect the server:
    • Installed as the Skill Seekers plugin? Nothing to do — the plugin's bundled .mcp.json starts the server automatically (it still needs step 1).
    • Installed standalone (e.g. copied into ~/.claude/skills/)? Register the server once: claude mcp add skill-seekers -- python -m skill_seekers.mcp.server_fastmcp

If tools like scrape_docs or package_skill are not in your tool list, the server is not connected. Tell the user about the two steps above, and use the CLI fallback in the meantime.

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
  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

CLI Fallback (MCP server not connected)

The same pipeline is available from the command line (requires pip install skill-seekers). Run it with the Bash tool:

skill-seekers create <source>                      # auto-detects: URL, owner/repo, ./path, file.pdf, video URL, ...
skill-seekers package <skill_dir> --target claude  # or gemini/openai/langchain/chroma/...

create covers detection, scraping, and building in one step; add --enhance-level 0 to skip AI enhancement. After it finishes, read the generated SKILL.md and summarize what was created.

Similar Skills

webapp-testing
anthropics/skills180k

webapp-testing

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

Browser automation

browser-testing-with-devtools
addyosmani/agent-skills103k

browser-testing-with-devtools

Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be configured.

Browser automation

webapp-testing
ComposioHQ/awesome-claude-skills77k

webapp-testing

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

Browser automation

browser
code-yeongyu/oh-my-openagent70k

browser

Drives a real browser through the omowright library from the js eval kernel: sites the user is already signed into, forms and clicks, JS-rendered pages, screenshots, web QA, extension popups, a human handoff for login, CAPTCHA or OTP, and a browser you own for scraping, bot-scored targets, network capture and QA traces. Use for any interactive browser task; not for a plain search or an unblocked static fetch.

Browser automation

agent-browser
shanraisshan/claude-code-best-practice67k

agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

Browser automation

cherry-tool-guide
CherryHQ/cherry-studio52k

cherry-tool-guide

Cherry Studio first-party tool and bundled-shell routing for general agents. For straightforward local work in shell-capable sessions, run JS/TS with `bun <file>` and one-off JS tools with `bun x`; run Python with `uv run [--with <pkg>] python` and one-off Python CLIs with `uvx`; search with `rg`. Load this guide before changing project dependencies, deciding whether a tool should be ephemeral or reusable, reading or converting local Office/PDF files, coordinating or delegating across Agent Sessions, or using Cherry-owned web/browser, knowledge, persistent memory, schedules/notifications, IM channels, image generation, artifact reporting, managed CLI, skill, or MCP-server-registration capabilities—even if the user names no tool. Consult it before shell/file workarounds; live tool schemas are authoritative.

Browser automation