Skip to content
TrustedSkillsbeta
Back to all skills

History Analyzer

Checked
lis186·vlatest·writing·MIT

Analyzes historical texts to identify key events, figures, and trends, offering valuable insights for research and understanding past contexts.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add lis186/sourceatlas --skill history-analyzer -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

lis186

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned lis186/sourceatlas at b176ae0f1c.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
1 file, 44 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The history-analyzer skill analyzes historical text and provides insights. It can extract key events, identify figures involved, and summarize periods of time based on provided documents or passages. This allows users to quickly understand complex historical narratives without extensive reading.

When to use it

  • Researching a specific historical event for a school project.
  • Summarizing lengthy historical documents for quicker comprehension.
  • Understanding the context surrounding a particular figure in history.
  • Gaining an overview of a specific time period based on available text sources.

Key capabilities

  • Event extraction from historical texts
  • Identification of key figures mentioned
  • Summary generation of historical periods
  • Analysis of provided documents or passages

Example prompts

  • "Analyze this document about the French Revolution and tell me the main events."
  • "Who were the important people involved in the American Civil War, according to this text?"
  • "Summarize the key characteristics of the Victorian era based on these articles."

Tips & gotchas

The skill's accuracy depends heavily on the quality and clarity of the provided historical texts. Very dense or poorly written sources may yield less reliable results.