Agent skill
ead-kaufman-benson
Specialized skill for editing and refining EAD2002 finding aids for the Terrence Kaufman Papers at the Archive of Indigenous Languages of Latin America (AILLA), Lillas Benson Latin American Studies and Collections, University of Texas at Austin. Use when working with KaufmanEAD.xml, implementing staff feedback, validating against EAD2002 standards, or referencing institutional finding aid examples.
Install this agent skill to your Project
npx add-skill https://github.com/JankMajesty/KaufmanEAD/tree/main/my-ead-skill/ead-kaufman-benson
SKILL.md
EAD Finding Aid Editor - Kaufman Papers (AILLA/Benson)
This skill provides specialized guidance for creating and editing the preliminary EAD2002 finding aid for the Terrence Kaufman Papers collection at AILLA/Lillas Benson, UT Austin.
Project Context
Collection: Terrence Kaufman Papers
Institution: Archive of Indigenous Languages of Latin America (AILLA), Lillas Benson Latin American Studies and Collections, University of Texas at Austin
Status: Pre-processed materials, preliminary finding aid in progress
Standard: EAD2002
Primary File: KaufmanEAD.xml
Workflow
When working on the Kaufman finding aid:
- Review Current State: Load and analyze KaufmanEAD.xml to understand the current structure
- Implement Feedback: Apply staff feedback from Benson archivists systematically
- Validate Structure: Check against EAD2002 schema (schema2.xsl) and institutional standards
- Reference Examples: Consult institutional EAD examples in references/ for consistency
- Preserve Context: Maintain AILLA-specific metadata and indigenous language documentation standards
Key EAD2002 Elements for Archival Collections
Critical Structural Elements
<ead>- Root element<eadheader>- Header with metadata about the finding aid itself<archdesc>- Main archival description (level="collection" or "fonds")<did>- Descriptive identification (required in archdesc and component levels)<dsc>- Description of subordinate components (series, subseries, files, items)
Common Components in
<unittitle>- Title of the unit<unitid>- Unique identifier<unitdate>- Date(s) of materials<physdesc>- Physical description including<extent><repository>- Holding institution<langmaterial>- Language of materials (important for AILLA multilingual collections)<origination>- Creator information
Important Descriptive Elements
<bioghist>- Biographical/historical note<scopecontent>- Scope and content note<arrangement>- Organization of materials<accessrestrict>- Access restrictions<userestrict>- Use restrictions<prefercite>- Preferred citation<controlaccess>- Controlled access terms (subjects, names, etc.)
Component Structure ( or -)
For series/subseries/file organization:
- Use
<c>elements or numbered<c01>,<c02>, etc. - Each component has
levelattribute: "series", "subseries", "file", "item" - Each component typically contains its own
<did>and may have additional descriptive elements
AILLA-Specific Considerations
- Indigenous Language Materials: Ensure proper language codes in
<langmaterial> - Cultural Sensitivity: Review access restrictions for culturally sensitive materials
- Documentation Standards: Follow AILLA metadata standards for linguistic materials
- Researcher Context: Include sufficient detail for linguists and indigenous language researchers
Reference Files
The skill includes institutional EAD examples demonstrating Benson standards:
- references/carlosmorton.xml - Carlos Morton Papers EAD example
- references/ailla.xml - AILLA collection EAD example
- references/pirapirana.xml - Pirapirana collection EAD example
- references/ead2002-elements.md - Quick reference for EAD2002 element usage
Consult these files when questions arise about:
- Proper element nesting and hierarchy
- Institutional description conventions
- Container notation standards
- Subject heading formatting
Validation
Use schema2.xsl to validate the finding aid structure. Common validation steps:
- Check XML well-formedness
- Validate against EAD2002 DTD/schema
- Verify required elements are present
- Ensure proper nesting and hierarchy
- Check controlled vocabulary terms
Best Practices for This Project
- Consistency: Match formatting and description style from reference EADs
- Completeness: Ensure all required EAD2002 elements are present
- Clarity: Write descriptions for researchers unfamiliar with the collection
- Accuracy: Verify dates, extent, and other factual information
- Standards Compliance: Follow both EAD2002 and Benson institutional guidelines
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
handoff
Compact the current conversation into a handoff document for another agent to pick up.
obsidian-vault
Search, create, and manage notes in the Obsidian vault with wikilinks and index notes. Use when user wants to find, create, or organize notes in Obsidian.
setup-pre-commit
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.
migrate-to-shoehorn
Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.
edit-article
Edit and improve articles by restructuring sections, improving clarity, and tightening prose. Use when user wants to edit, revise, or improve an article draft.
scaffold-exercises
Create exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold exercises, create exercise stubs, or set up a new course section.
Didn't find tool you were looking for?