A
licenseA
qualityC
maintenanceTurn any YouTube video, article, PDF, or image into a reusable Claude Code skill — without leaving your editor.
6
35
MIT
Skill Seekers
Related Servers
Alternatives to Skill Seekers
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables Claude to intelligently analyze and query codebases using knowledge graphs, supporting natural language code search, relationship discovery, and incremental updates.11-
- AlicenseAqualityFmaintenanceProvides access to a library of 18 specialized skills, project templates, and prompt patterns for Claude Code. It enables automated workflows for feature development, security audits, and system maintenance through multi-agent collaboration.62 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables Claude Code to index and semantically search through PDFs, code, and documents with exact citations and zero hallucinations.MIT
- AlicenseCqualityCmaintenanceEnables AI-powered automated testing, security scanning, code review, and maintenance tasks directly within Claude Code or desktop.124MIT
- FlicenseNot gradedqualityCmaintenanceTransforms code repositories and development documentation into a queryable Neo4j knowledge graph, enabling AI assistants to perform intelligent code analysis, dependency mapping, impact assessment, and automated documentation generation across 15+ programming languages.7-
TDQS
B3.1/5.0
Scored across 40 tools
Disambiguation4/5
Most tools have a distinct verb+resource target, so concepts like configs, config sources, workflows, marketplaces, and vector exports remain separable. The main mild ambiguities are scrape_docs vs scrape_generic (both can touch HTML content) and the four parallel export_to_* tools, though their target names and descriptions mostly resolve confusion.
Naming Consistency5/5
The entire surface uses consistent snake_case, verb-first naming: list_configs, create_workflow, scrape_docs, validate_config, export_to_chroma, and so on. Even the preposition-style names like publish_to_marketplace and export_to_weaviate follow the same predictable verb+target pattern.
Tool Count2/5
40 tools is well beyond the 16-25 heavy range and creates a sprawling MCP surface. Several groups, such as the four export_to_* tools and the parallel config-source vs marketplace lifecycles, could plausibly be consolidated without reducing the server's actual functionality.
Completeness4/5
The surface covers a nearly complete skill-building lifecycle: configs, scraping, enrichment, packaging, installing, publishing, marketplace management, and vector database exports. Minor gaps exist around managing already-published or already-installed skills, but the core workflows are not dead-ended.
Maintenance
ActivityActive
ResponsivenessResponsive