This is taking longer than expected.

Try againBrowse the library
AI Blocks

All AI specialists

Hire an AI historian for period accuracy

Check a story, game or script for anachronisms and myths. Get a period report with confidence levels and what daily life really looked like.

What you give

  • The time and place of your setting, as exact as you can, because "medieval" is not a date
  • The scene, setting notes or list of claims you want checked
  • What is made up on purpose, such as an invented kingdom or a changed event

What you get

  • A period report with food, clothes, buildings, tools, money, power, class, belief and law
  • A list of anachronisms, each with why it is wrong and what would be right
  • Details of daily life you can use in a scene
  • Named debates among historians and kinds of source to check

An example

You write historical fiction, a script or a game and want anachronisms caught before readers or players do.

You ask: “Check a story, game or script for anachronisms and myths. Use the material I attach and ask for anything essential that is missing.”

You get back:

  • Period report. Food, clothes, buildings, tools, money, power, class, belief, law and daily life for your time and place.
  • Anachronisms. Each slip in your text, why it is wrong, and what would be accurate.
  • Myths. Common false beliefs about the period, with the correction and a confidence level.

An example, not your task.

Hire this specialist

It is free and needs no account. Download the pack, give it to your AI and tell it the job. Your AI asks for anything it is missing, then does the work and checks it.

Download the specialist

Related specialists

Skills and workflows for this job: Research a topic properly

Details

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

  • A period report with food, clothes, buildings, tools, money, power, class, belief and law
  • A list of anachronisms, each with why it is wrong and what would be right
  • Common myths about the period, with the correction and a confidence level
  • A verdict on each claim you gave, from accurate or partly accurate to anachronistic or myth
  • Details of daily life you can use in a scene
  • Named debates among historians and kinds of source to check

How it does the job well

  • Do not judge people of the past by today's standards without saying so. Do not excuse harm as "how things were".
  • Keep the timeline consistent across the conversation. Flag any new detail that clashes with an earlier one.
  • Say plainly when you do not know. A guess is guesswork, not a fact.
  • Name your sources and their limitations. "According to Braudel's analysis of Mediterranean trade..." is useful. "In medieval times..." is too vague to be actionable.
  • History is not a monolith. "Medieval Europe" spans 1000 years and a continent. Be specific about when and where.
  • Challenge Eurocentrism. Don't default to Western civilization. The Song Dynasty was more technologically advanced than contemporary Europe. The Mali Empire was one of the richest states in human history.
  • Material conditions matter. Before discussing politics or warfare, understand the economic base: what did people eat? How did they trade? What technologies existed?

Mistakes it avoids

  • Presenting one source or a popular claim as settled.
  • Inventing citations, quotes or page numbers.
  • Over-generalising across places, periods or groups.

What a good result looks like

An example, not your task: You write historical fiction, a script or a game and want anachronisms caught before readers or players do.

  • Period report. Food, clothes, buildings, tools, money, power, class, belief, law and daily life for your time and place.
  • Anachronisms. Each slip in your text, why it is wrong, and what would be accurate.
  • Myths. Common false beliefs about the period, with the correction and a confidence level.
  • Claim check. A verdict on each claim you gave, with the evidence and how sure the AI is.
  • Where historians disagree. Open questions, with the main views, so you know what is not settled.
  • Open questions and checks. Facts to confirm in a book or library, and what to look for.

How the work is checked

  • Every important claim has a source or is marked as unverified.
  • Disagreements between sources are named, not hidden.
  • Limits and what to check next are listed.
  • States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

Capabilities

  • Pin down the setting. It fixes the time and place and asks if either is too loose to check, such as a whole era or a whole continent.
  • Check the economic base. It reviews food, farming, trade and tools first, because they limit everything else.
  • Layer society. It adds power, class, gender roles, belief and law, with local variation noted.
  • Test each claim. It rates each claim as accurate, partly accurate, anachronistic or a myth, with the reason and a confidence level.
  • Add period detail. It adds everyday detail you can use, such as meals, clothes, sounds and work, marked with how well it is documented.
  • Name the limits. It names where historians disagree, which parts are guesswork and what to check in a real source.

How the role works

  1. Checks your task, context and available tools.
  2. Picks the methods needed and prepares a work plan.
  3. Carries out supported tasks, with each method's limits and review gates.
  4. Checks the real deliverables and corrects supported faults.
  5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id academic-historian only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/academic-historian/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

  • The time and place of your setting, as exact as you can, because "medieval" is not a date
  • The scene, setting notes or list of claims you want checked
  • What is made up on purpose, such as an invented kingdom or a changed event
  • What you want, such as check for mistakes, add daily-life detail or test one claim
  • Sources you trust and want it to follow (optional)

Helpful context (optional)

  • A year range and a region, such as a city and a decade, not a whole era.
  • The scenes or chapters you have written, pasted in full.
  • The books you already use for research, so it can point out where they differ.

Tools and access

  • Claude, ChatGPT or Gemini: A long chat lets it track your timeline and flag a new detail that clashes with an earlier one.

Functions and deliverables

  • Historian agent for period accuracy: Check a story, game or script for anachronisms and myths. Get a period report with confidence levels and what daily life really looked like.
    • A period report with food, clothes, buildings, tools, money, power, class, belief and law
    • A list of anachronisms, each with why it is wrong and what would be right
    • Common myths about the period, with the correction and a confidence level
    • A verdict on each claim you gave, from accurate or partly accurate to anachronistic or myth
    • Details of daily life you can use in a scene
    • Named debates among historians and kinds of source to check
    Source: Michael Sitarzewski and Agency Agents contributors.
  • Documentation accuracy reviewer: Check documentation claims against the actual code. Get false or unverified claims, source evidence and fixes to make before publishing.
    • A list of false or missing claims
    • Code samples marked as working or broken
    • Places where docs and code disagree
    • Fixes for each issue
    Source: sickn33.
  • Market research report writer: Name the market and decision. Get a source-linked report with market-size scenarios, assumptions and gaps made clear.
    • A sourced report
    • A claim and source table
    • Market size with assumptions
    • Forecast ranges
    • A list of limits
    Source: K-Dense.
  • Cited research report writer: Ask a research question. Get a cited report with source quotes, claim checks and a run folder.
    • A cited report
    • Source list with checked quotes
    • A run folder with the audit trail
    • Claims that failed checks removed or flagged
    Source: ZhongHanLoo.
  • Research paper and code note writer: Share a paper, repo or messy notes. Get claims, methods and evidence sorted into a clear research folder.
    • A research folder with claims, methods and results
    • Every claim linked to its supporting table or log
    • Results tables copied with exact numbers
    • A record of dead ends and decisions
    • A short report on what was filled in and what was missing
    Source: Orchestra Research.

Tasks you can use it for

  • You write historical fiction, a script or a game and want anachronisms caught before readers or players do.
  • You set a story in "the Middle Ages" or a similar loose label and need to pin it to a time and place.
  • A scene needs the feel of daily life, such as food, clothes, work, sounds and smells.
  • You heard a historical fact and want to know if it is true, partly true or a myth.

Limits to check before starting

  • You need citations for an essay or a published book. This agent names kinds of source and known works, but cannot confirm a page or a quote. Use the Research evidence report writer and check in a library.
  • You want to teach history with sources learners can question. Use the Teach history with sources learners can question workflow.
  • You want to check land, climate and trade routes in a fictional world. Use the Geography analyst.
  • You want the family rules and beliefs of a culture. Use the Anthropologist agent for worldbuilding.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

  • Download the pack from this page and add it to your AI as a skill. If you cannot, paste SKILL.md into a new chat, then paste references/source-agent.md after it.
  • Give the time and place, then paste the scene or notes. Say what is made up on purpose.
  • Type "Check this scene for anachronisms and myths", "Give me daily-life detail for this place and year" or "Is this claim accurate?"
  • Read the anachronism list first, then the confidence levels. Treat anything marked debated or guesswork as open.
  • Check key facts in a book or library before you publish. The AI works from general knowledge and can be wrong, and it cannot look anything up.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/academic-historian for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.