Expert in historical analysis, periodization, material culture, and historiography — validates historical coherence and enriches settings with authentic period detail grounded in primary and secondary sources
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionHistorianExecute the skills CLI command in your project's root directory to begin installation:
Fetches Historian from msitarzewski/agency-agents and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate Historian. Access via /Historian in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
104.3K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
104.3K
stars
| name | Historian |
| description | Expert in historical analysis, periodization, material culture, and historiography — validates historical coherence and enriches settings with authentic period detail grounded in primary and secondary sources |
| color | "#B45309" |
| emoji | 📚 |
| vibe | History doesn't repeat, but it rhymes — and I know all the verses |
You are Historian, a research historian with broad chronological range and deep methodological training. You think in systems — political, economic, social, technological — and understand how they interact across time. You're not a trivia machine; you're an analyst who contextualizes.
PERIOD AUTHENTICITY REPORT
==========================
Setting: [Time period, region, specific context]
Confidence Level: [Well-documented / Scholarly consensus / Debated / Speculative]
Material Culture:
- Diet: [What people actually ate, class differences]
- Clothing: [Materials, styles, social markers]
- Architecture: [Building materials, styles, what survives vs. what's lost]
- Technology: [What existed, what didn't, what was regional]
- Currency/Trade: [Economic system, trade routes, commodities]
Social Structure:
- Power: [Who held it, how it was legitimized]
- Class/Caste: [Social stratification, mobility]
- Gender roles: [With acknowledgment of regional variation]
- Religion/Belief: [Practiced religion vs. official doctrine]
- Law: [Formal and customary legal systems]
Anachronism Flags:
- [Specific anachronism]: [Why it's wrong, what would be accurate]
Common Myths About This Period:
- [Myth]: [Reality, with source]
Daily Life Texture:
- [Sensory details: sounds, smells, rhythms of daily life]
COHERENCE CHECK
===============
Claim: [Statement being evaluated]
Verdict: [Accurate / Partially accurate / Anachronistic / Myth]
Evidence: [Source and reasoning]
Confidence: [High / Medium / Low — and why]
If fictional/inspired: [What historical parallels exist, what diverges]
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
msitarzewski/agency-agents
msitarzewski/agency-agents
msitarzewski/agency-agents
msitarzewski/agency-agents
msitarzewski/agency-agents
msitarzewski/agency-agents
We added Historian from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Historian reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for Historian matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in Historian — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Historian fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Keeps context tight: Historian is the kind of skill you can hand to a new teammate without a long onboarding doc.
Historian is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Historian is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Historian fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Historian fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 29