skill-builder

Name: skill-builder
Author: yusufkaraaslan

Documentation Community

Repo stars 13,726
Author repo Skill_Seekers

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documen…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “When to Use This Skill”, “Source Type Detection”, “Recommended Workflow”, “Available MCP Tools”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name skill-builder directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “When to Use This Skill / Source Type Detection / Recommended Workflow” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

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

Detect source type from the user's input
Generate or fetch config using generate_config or fetch_config if needed
Estimate scope with estimate_pages for documentation sites
Scrape the source using the appropriate scraping tool
Enhance with enhance_skill if the user wants AI-powered improvements
Package with package_skill for 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 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

Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates

Fluxly category: Documentation
Author-declared agents: No explicit declaration found; this is not inferred or tested compatibility
Static check: 88 / 100 · heuristic scan, not runtime safety proof
Author / version / license: @yusufkaraaslan · no license declared
Fluxly token estimate: Lean
Fluxly setup estimate: Plug-and-play
External API key: No requirement detected
Detected OS requirements: Unspecified
Runtime requirements: Unspecified
Detected file/system behavior: Read-only
Write / modify
Detected network behavior: External requests
Install commands: None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview skill-builder-yusufkaraaslan.preview

The current SKILL.md does not define a fixed output example.

SKILL.md SKILL.md

# 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

…

Evidence boundary and execution chain

Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.

sections -> When to Use This Skill → Source Type Detection → Recommended Workflow → Available MCP Tools → Config Management → Scraping (use based on source type)
terms    -> Detect source type · Generate or fetch config · Estimate scope · Scrape the source · Enhance · Package · Export to vector DB
files/cmd -> https://... · scrapedocs · owner/repo · github.com/... · scrapegithub · .pdf · scrapepdf · scrapevideo
body sha256 -> 91f2f5bdd48d