/ Directory / Playground / Skill_Seekers
← All servers ↗ GitHub
● Community yusufkaraaslan ⚡ Instant

Skill_Seekers

by yusufkaraaslan · yusufkaraaslan/Skill_Seekers

Turns docs sites, GitHub repos, PDFs, and videos into ready-to-use SKILL.md bundles — a factory for making new Claude skills.

Skill Seekers is a meta-skill: you point it at a documentation source and it produces a production-grade SKILL.md (500+ lines with examples) plus a references folder. It detects conflicts between documented APIs and real code, supports 18 source types, and exports to Claude Code, Cursor, Windsurf, LangChain, and vector DBs.

▶ Watch demo 📦 Install 💡 Use Cases

Why use it

Key features

Live Demo

What it looks like in practice

skill-seekers-skill.replay ▶ ready
0/0

Install

Author repository · Claude Skills documentation

Use Cases

Real-world ways to use Skill_Seekers

Turn a library's documentation site into a Claude skill in 10 minutes

👤 Developers who rely on a library Claude doesn't know well ⏱ ~15 min intermediate

When to use: Claude keeps inventing function signatures for your favorite library because its training data is stale.

Prerequisites
  • URL of the library's docs site — The canonical ReadTheDocs, Docusaurus, or mintlify URL
Flow
  1. Review the generated SKILL.md
    Show me the frontmatter and the first 50 lines of the generated SKILL.md.✓ Copied
    → Valid YAML frontmatter, clear sections
  2. Test with a real prompt
    Now use the new example skill to do <representative task>.✓ Copied
    → Claude uses real API names, not hallucinated ones

Outcome: A new skill in your ~/.claude/skills/ folder that Claude picks up automatically.

Pitfalls
  • Docs-vs-code drift sneaks into the output — Let the conflict detector flag mismatches; skim the conflicts.md report it produces
Combine with: firecrawl · filesystem

Generate a skill directly from a GitHub repo's code and README

👤 Anyone onboarding Claude onto an internal or obscure OSS codebase ⏱ ~20 min intermediate

When to use: No hosted docs exist — the README and the source are the only truth.

Flow
  1. Run on the repo URL
    Run skill-seekers on github.com/acme/internal-sdk, include code examples from tests/.✓ Copied
    → Extracts public API surface + example usage
  2. Iterate on the skill
    The first draft misses the auth flow — add a section on token setup.✓ Copied
    → SKILL.md expanded with that section

Outcome: A targeted skill Claude can invoke when working in that codebase.

Pitfalls
  • Repo is huge and scraping stalls — Use excludePaths to skip vendored directories and test fixtures
Combine with: github

Combinations

Pair with other MCPs for X10 leverage

skill-seekers-skill + firecrawl

Firecrawl does the heavy JS-rendered scraping; Skill Seekers does the structuring

Use firecrawl to crawl the docs site, then skill-seekers to turn the output into a SKILL.md.✓ Copied
skill-seekers-skill + github

Pull repo contents via GitHub MCP, enhance into a skill

Fetch the acme/sdk repo's README, examples/, and types, then build a skill from them.✓ Copied

Tools

What this MCP exposes

ToolInputsWhen to callCost
Ingest source URL / repo / PDF path First phase — gather source material Free (plus any scraper API if used)
Enhance ingested content, target platform Second phase — AI-write the skill LLM tokens for enhancement
Conflict-detect docs + code sources Whenever you ingest both docs and source 0
Export target platform (Claude, Cursor, LangChain, etc.) Third phase — package for destination 0

Cost & Limits

What this costs to run

API quota
None for the skill itself; depends on which scraper you pair with
Tokens per call
Generation phase can use 10-50k tokens for a large library
Monetary
Free — the skill itself. Pairing scrapers (Firecrawl) may cost credits.
Tip
Cache ingested content; re-run enhance/export without re-scraping.

Security

Permissions, secrets, blast radius

Credential storage: No credentials in the skill. Paired scrapers may need their own API keys.
Data egress: Only to the sources you point it at

Troubleshooting

Common errors and fixes

Generated SKILL.md has placeholder sections

Source was too thin — re-run with more inputs (add the GitHub repo alongside the docs site).

Checkpoint resume starts over

Make sure you're running from the same working directory where the .skillseekers/ cache was created.

Verify: ls .skillseekers/

Alternatives

Skill_Seekers vs others

AlternativeWhen to use it insteadTradeoff
skillforgeYou want an interactive skill router that also creates skills on demandLighter generator; Skill Seekers is more thorough on heavy doc sources
Manual SKILL.md writingThe skill is small and you know the library coldFaster for trivial skills; tedious at scale

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills

Continue exploring

Related tools and workflows

Choose another guide for your workflow, or explore a collection.

Browse all topic collections → · See 29 new official additions →