legal-skills
Related Servers
Alternatives to legal-skills
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables LLM agents to discover and search a catalog of skills, then fetch skill instructions and supporting references, scripts, and assets on demand.10MIT

decimalai-mcpofficial
AlicenseAqualityBmaintenanceEnables MCP clients to search the DecimalAI skills registry, retrieve detailed skill records, and access effectiveness-ranked leaderboards, with optional org-specific enrichment via an API key.3193 PyPI1MIT- AlicenseAqualityDmaintenanceProvides access to 462+ production-grade skills for AI-powered product building, enabling search, retrieval, and validation of skills across categories.51Apache 2.0
- -licenseNot gradedqualityNot gradedmaintenanceEnables intelligent discovery and management of Claude Skills through semantic search, ratings, favorites, and community curation. Provides tools to search, upload, rate, and organize skills with natural language queries and comprehensive metadata.-
- AlicenseNot gradedqualityBmaintenanceEnables Claude Code and other agents to search versioned skills, fetch skill contents, and browse folders through MCP, backed by hybrid full-text and semantic search.25 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables searching and browsing a library of Agent Skills and prompts, then loading full SKILL.md instructions and supporting files for a chosen skill.-
TDQS
Scored across 3 tools
Each tool maps to a distinct operation: search_legal_skills for discovery, list_legal_facets for browsing aggregates, get_legal_skill for retrieval by name. There is no overlap in purpose, and the descriptions reinforce the intended ordering/workflow.
All three tools follow a strict verb_noun snake_case pattern with a shared 'legal_skill(s)' entity suffix: get_legal_skill, search_legal_skills, list_legal_facets. The convention is fully predictable.
Three tools is slightly thin but well-matched to a read-only reference library, since the domain only requires discover, browse, and fetch. No redundant or trivial tools are present.
The surface covers discovery (search), browsing (facets), and retrieval (get), which is the natural lifecycle for a knowledge library. Minor gaps like pagination or listing all skills in a facet without search are workable around but not explicitly provided.