Find a skill for your task
Two ways to browse the same skills: by jurisdiction and by practice area,
both read from each first-party skill’s own lq_ai.jurisdiction and
lq_ai.tags. Each jurisdiction or practice-area page lists the skills that
cover it today, plus — where one exists — a scope note explaining what
“covered” actually means for that entry. A tag having skills against it
isn’t automatically a clean bill of coverage; read the note before assuming
it is.
Litigation is the clearest example why. The case-law-research skill
carries the litigation tag, but
PRD §1.6 excludes “e-discovery or
litigation-specific workflows” outright, and the skill’s own “What this
skill does not do” section bounds it further — it won’t research non-U.S.
jurisdictions, search statutory or regulatory text, apply retrieved
authority to your facts, or say whether a case is still good law. A page
that showed the tag alone would answer “can it do litigation?” wrongly, by
omission; the scope note exists so it doesn’t.
An empty category on this index means no first-party skill was listed
against it — not that nobody has ever written a related skill. Most
jurisdiction- and practice-area-specific work lives in the community
lq-skills repository rather
than this one; where this page shows a gap, read
Where skills live for the contribution
route. Scope notes and their sources are maintained in
docs/site/_data/coverage-notes.yaml; where a note is missing, the entry
reflects frontmatter only and should be read as unverified against the
wider canon.
Built from 17 first-party skills in skills/, faceted two ways. A count in the Skills column is a count of frontmatter declarations, not a coverage claim — the scope note is what tells you what “covered” means for that row.
By jurisdiction
Section titled “By jurisdiction”| Jurisdiction | Skills | Scope note |
|---|---|---|
| Jurisdiction-agnostic | 7 | yes |
| United States | 4 | yes |
| Regime-aware (input-selected) | 3 | yes |
| global | 1 | no scope notes yet |
| European Union | none | yes |
By practice area
Section titled “By practice area”2 practice areas named in docs/site/_data/coverage-notes.yaml have no first-party skill against them: Employment, Intellectual property. Each page says whether the area is an open gap or a deliberate scope exclusion.
1 jurisdiction is named with no skill declaring it: European Union.
39 tags in skill frontmatter are not grouped into a practice area by docs/site/_data/coverage-notes.yaml, so they have no page of its own: alerts, case-law, citations, commercial, communications, compliance, confidentiality, courtlistener, deadlines, demonstration, dpa, drafting, due-diligence, extraction, goods, internal, meta, msa, nda, orchestration, plain-language, playbooks, procurement, productivity, prompt-engineering, purchase, qa, question-answering, regulatory, research, review, saas, snapshot, subscription, supply, tabular, transformation, triage, vendor. A tag is a discovery aid; a practice area is an editorial claim about coverage, and only the second one gets a page.
1 facet has no scope note in docs/site/_data/coverage-notes.yaml and reflects frontmatter only: global.
Contributing coverage
Section titled “Contributing coverage”A jurisdiction- or practice-area-specific skill contribution routes to the community LegalQuants/lq-skills repository (ADR 0024’s skills route), not to this repository’s own skills/ directory — this repository’s skills/ holds the fifteen first-party built-in skills (the ten M1 starter skills plus case-law-research and four table-mode/ internal skills), per README.md §“Starter skills”. Claim the jurisdiction or practice area on a tracking issue first, per skills/CONTRIBUTING.md’s contribution process, so two contributors don’t duplicate the same coverage. ADR 0024 commits to a standing coverage ledger at docs/contribute/coverage-map.md; that file is not present in the repository as of the checked commit, so this generated index is the closest thing to it today. A practice area PRD §1.6 excludes outright (litigation chief among them) is a different route entirely — it needs a mini-PRD and a committee-decided PRD amendment before any skill work starts, per ADR 0024’s fourth route.
docs/adr/0024-jurisdiction-and-practice-area-expansion.md · README.md