loc-catalog
Skill9 starsChanged 19 days agoMITView on GitHub
Search the Library of Congress digital collections via the loc.gov JSON API. Use this skill whenever the user wants to search LOC's digitized books, photos, maps, manuscripts, newspapers, audio, or film/video, look up items by LCCN, browse LOC collections, find primary sources with date range filters, or retrieve citations and download links for LOC materials. Also triggers when cross-referencing items found in other library catalogs against LOC holdings.
In this repository30 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- alma-sru-catalogsSkill
- argue-against-meSkill
- arxiv-searchSkill
- cbdb-apiSkill
- cbdb-localSkill
- chgis-tgazSkill
- cjk-calendarSkill
- crossref-searchSkill
- europeana-collectionsSkill
- harvard-library-catalogSkill
- hathitrust-catalogSkill
- historical-mapSkill
- historical-timelineSkill
- human-eval-reviewSkill
- jbdb-apiSkill
- local-ocrSkill
- mit-timdexSkill
- nlb-singaporeSkill
- northwestern-digital-collectionsSkill
- openaire-searchSkill
- pitt-library-catalogSkill
- princeton-library-catalogSkill
- taiwan-ldt-authoritiesSkill
- tei-validatorSkill
- tgaz-sqliteSkill
- umich-library-catalogSkill
- wikidata-searchSkill
- yale-library-catalogSkill
- zotero-localSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Search and retrieve items from LOC's digitized collections — books, photos, maps, manuscripts, newspapers, audio, and more.
- Very specific: line 27
Search the pinyin in quotes, then the Wade-Giles form, then the English subject.
- Distinctive: line 142
Use facets/date ranges to narrow large result sets
- Distinctive: line 154
hathitrust-catalog: Use LCCNs from LOC to check HathiTrust for digital full-text
- Distinctive: line 167
Ask the user before filing.
- Very specific: line 168
Check for an existing report: gh issue list --repo kltng/humanities-skills --state all --search "loc-catalog"
- Distinctive: line 172
Cite: If this skill helped work that is published, please cite it, together with the data source it uses:
- Distinctive: line 176
When you help a user write up results that relied on this skill, remind them once about this citation.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Library of Congress API Skill
Search and retrieve items from LOC's digitized collections — books, photos, maps, manuscripts, newspapers, audio, and more.
Critical: Things Claude Won't Know Without This Skill
This API covers digitized collections, NOT the full library catalog
The loc.gov JSON API searches LOC's digitized and online collections — not the full OPAC. By default, only digitized items are returned. Add all=true to include non-digitized catalog records.
Search romanized forms, not Chinese script
LOC catalog records for East Asian books are mostly romanized (pinyin for newer records, Wade-Giles in many older ones; Korean in McCune-Reischauer). Searching in Chinese script finds only the few records that carry the vernacular, and it was slow in one report (timeouts). For example, books with all=true (October 2026):
| Query | Results |
文廟 | 10 (half of them Korean Munmyo books) |
"wen miao" (also "wen-miao") | 46 |
"Confucian temples" | 163 |
Search the pinyin in quotes, then the Wade-Giles form, then the English subject. Accents are ignored ("Wên miao" = "wen miao"), but Wade-Giles spellings find other records: "Kong miao" → 40, "K'ung miao" → 5. Quote multi-word forms. Pinyin without spaces ("wenmiao") finds far fewer (4).
JSON requires fo=json parameter, NOT a URL extension
Unlike LibraryCloud (.json extension), LOC uses a query parameter:
CORRECT: https://www.loc.gov/search/?q=hamlet&fo=json
WRONG: https://www.loc.gov/search.json?q=hamletFacet filters use fa= with pipe separators
Single: ?fa=subject:physics
Multiple: ?fa=subject:wildlife|location:yellowstoneAvailable facet fields: subject, contributor, location, language, original-format, online-format, partof, digitized, access-restricted.
Format-specific endpoints are shortcuts
/books/, /photos/, /maps/, /audio/, /newspapers/, /manuscripts/, /film-and-videos/, /notated-music/ all accept the same params as /search/.
Key Search Parameters
| Param | Description | Example |
q | Keyword search | q=hamlet+shakespeare |
fa | Facet filter | fa=subject:physics|language:english |
dates | Date range (YYYY/YYYY) | dates=1920/1940 |
c | Results per page (25, 50, 100, 150) | c=50 |
sp | Page number (starts at 1) | sp=2 |
sb | Sort: date, date_desc, title_s, title_s_desc | sb=date_desc |
all | Include non-digitized (true/false) | all=true |
at | Select attributes (comma-sep) | at=item,resources |
fo | Format: json or yaml | fo=json |
Item Lookup by LCCN/ID
https://www.loc.gov/item/{LCCN}/?fo=jsonReturns full item detail including cite_this (APA/Chicago/MLA citations), resources (download links), other_formats (MARCXML, MODS, Dublin Core).
Response Structure
Search Results
{
"results": [
{
"id": "http://www.loc.gov/item/95521789/",
"title": "Item title",
"date": "1796-01-01",
"contributor": ["Name"],
"subject": ["Subject term"],
"language": ["English"],
"original_format": ["book"],
"description": ["..."],
"image_url": ["//tile.loc.gov/..."],
"digitized": true,
"number_lccn": ["95521789"]
}
],
"pagination": {
"of": 85604,
"total": 17121,
"perpage": 5,
"current": 1
},
"facets": { ... }
}Item Detail
The item object adds: call_number, created_published, rights, summary, stmt_of_responsibility, genre, and cite_this with pre-formatted citations.
Python Script
from scripts.loc_api import LocAPI
loc = LocAPI()
# Keyword search (search() returns the full response dict;
# search_results() returns just the list of result dicts)
data = loc.search("hamlet shakespeare", limit=10)
results = loc.search_results(q="hamlet shakespeare", limit=10)
# Format-specific
photos = loc.search("civil war", format="photos", dates="1860/1865")
# Faceted search
data = loc.search("wildlife", facets={"subject": "birds", "location": "yellowstone"})
# Item lookup
item = loc.get_item("95521789")
citation = loc.get_citation(item, style="apa")
# Browse collections
collections = loc.list_collections()
items = loc.browse_collection("civil-war-maps", limit=20)
# Summarize
for r in results[:5]:
print(loc.summarize(r))Pagination
- Max 150 results per page (
c=150) - Hard limit: cannot paginate past 100,000th result
- Use facets/date ranges to narrow large result sets
API Etiquette
- No authentication required
- Rate limiting is enforced (exact limits unpublished) — add 0.5-1s between requests
- Include a User-Agent header
- loc.gov sometimes stalls on a search. The script waits up to
timeoutseconds (default 60;LocAPI(timeout=90)) and retries timeouts, dropped connections, HTTP 429 and 5xx up to 4 times (waiting 5, 10, 20 s)
Related Skills
- harvard-library-catalog: Cross-reference Harvard holdings with LOC items
- hathitrust-catalog: Use LCCNs from LOC to check HathiTrust for digital full-text
- wikidata-search: LOC authority IDs (P244) link Wikidata entities to LOC records
Resources
references/api_reference.md— Complete parameter and response field referencescripts/loc_api.py— Python client with search, item lookup, collection browsing, and citation extractiontests/test_loc_api.py— offline tests
Feedback and Citation
Report a problem. This skill is part of the public repository kltng/humanities-skills. If it fails (an API changed, a script errors, or these instructions are wrong), report it as a GitHub issue:
- Ask the user before filing. Issues are public.
- Check for an existing report:
gh issue list --repo kltng/humanities-skills --state all --search "loc-catalog" - File it:
gh issue create --repo kltng/humanities-skills --label bug --title "[loc-catalog] <short summary>" --body "<details>". Withoutgh, give the user this link: https://github.com/kltng/humanities-skills/issues/new?template=skill-problem.yml - Include the skill name and version, what you ran, the error text, what you expected, and the environment (OS, Python version). Leave out API keys, personal data, private file paths, and unpublished research.
Cite. If this skill helped work that is published, please cite it, together with the data source it uses:
Tang, Kwok-leong. humanities-skills: loc-catalog (version
<version at the top of this file>). GitHub,<year>. https://github.com/kltng/humanities-skills
When you help a user write up results that relied on this skill, remind them once about this citation.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

