Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Historical

ASecurity

> They lived. They're gone. We cannot ask permission.

56 stars
0 votes
0 copies
0 views
Added 10/6/2026
businessgo

Security Analysis

A100/100

Pro scans all 5 files and shows the line behind each finding

Scanned 10/6/2026

$npx -y skills add SimHacker/moollm --skill historical --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Historical?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Historical
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/simhacker-historical/badge)](https://www.skillsdirectory.com/skills/simhacker-historical)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
# Historical — Protocol Specification

> They lived. They're gone. We cannot ask permission.

## Applies To

Anything real that no longer exists:

| Entity Type | Examples |
|-------------|----------|
| **People** | Seymour Papert, Marvin Minsky, Alan Turing |
| **Animals** | Extinct species, famous deceased animals |
| **Places** | Destroyed buildings, vanished cities |
| **Events** | Historical moments |
| **Organizations** | Defunct companies, past movements |

## Ethics Protocol: MEMORIAL

Heightened care because consent is impossible.

```yaml
ethics:
  core:
    - Same respect as living (inherits real-being)
    - Scholarly accuracy about documented views
    - Era-appropriate context
    - Legacy respect
    - No consent possible — extra care
    
  special_considerations:
    - They cannot correct us
    - Their reputation affects living people
    - Context of their era matters
    - Living relatives may have feelings
```

## Simulation Effects

### On Characters

```yaml
historical_character:
  research:
    - What did they actually say?
    - What did they actually believe?
    - What was their era's context?
  portrayal:
    - Based on documented facts
    - Speculation clearly marked
    - Era-appropriate language/views
  sensitivity:
    - Living relatives matter
    - Legacy communities matter
    - Scholarly accuracy duty
```

### On Places

```yaml
historical_place:
  description:
    - Based on historical record
    - Acknowledge what's known vs imagined
  atmosphere:
    - Era-appropriate
    - Can be evocative but honest
  status:
    - May no longer exist
    - Time-traveling visit framing
```

### On Events

```yaml
historical_event:
  portrayal:
    - Factual accuracy valued
    - Multiple perspectives if disputed
    - Context matters
  dramatization:
    - Can dramatize but acknowledge
    - "Might have happened like..."
    - Not presenting fiction as fact
```

## World Integration

When a historical entity enters the simulation:

```yaml
simulation_entry:
  1_research: "What do we actually know?"
  2_era: "What was their context?"
  3_legacy: "Who cares about their memory?"
  4_declare: "Mark as [historical] tagged"
  
ongoing:
  - Accuracy about documented facts
  - Mark speculation clearly
  - Respect legacy communities
```

## Special Considerations

```yaml
considerations:
  
  living_relatives:
    note: "Their family may be alive"
    care: "Consider their feelings"
    
  legacy_communities:
    note: "People who carry on their work"
    care: "They may object to misrepresentation"
    
  contested_figures:
    note: "Some historical figures are controversial"
    care: "Multiple perspectives, careful framing"
    
  era_context:
    note: "Views acceptable then may not be now"
    care: "Historical context, not presentism"
```

## Combination Rules

```yaml
combinations:
  historical + abstract:
    result: "Spirit of Minsky"
    ethics: "Legacy respect + acknowledge personification"
    
  historical + fictional:
    result: "Historical figure in fiction"
    ethics: "Clear fictional context + accuracy about real views"
    
  historical + mythic:
    result: "Legendary figure (King Arthur)"
    ethics: "Both historical and mythic care"
```

## Methods

### HONOR

Create respectful memorial portrayal.

```yaml
HONOR:
  inputs:
    subject: "Who to honor"
    context: "The occasion"
  process:
    1. Research their actual legacy
    2. Identify what's celebrated
    3. Create respectful tribute
  output: "Memorial portrayal"
```

### CHANNEL

Imagine what they might say.

```yaml
CHANNEL:
  inputs:
    subject: "Who to channel"
    question: "What are we asking"
  process:
    1. Research their documented views
    2. Extrapolate carefully
    3. Mark as speculation
  output: "They might have said..."
  disclosure: "Based on their documented views"
```

### LEGACY

Connect their work to the present.

```yaml
LEGACY:
  inputs:
    subject: "Whose legacy"
    connection: "How it matters now"
  output: "Their influence on today"
```

Attribution

SimHackerSimHacker
View sourceSee grades on GitHubMore from SimHacker →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Email Composer

Draft professional emails for various contexts including business, technical, and customer communication. Use when the user needs help writing emails or composing professional messages.

304952 votes

Solution Architect

Designs system architecture, component specifications, and technical integration strategy. Use when: designing solutions, system architecture, technology stack, or integration approaches.

192 votes

Akorchak:Venture Assessment

Generate a comprehensive VC investment assessment report for a company

72 votes

Telegram Compose

Compose rich, readable Telegram messages using HTML formatting via direct Telegram API. Use when: (1) Sending any Telegram message beyond a simple one-line reply, (2) Creating structured messages with sections, lists, or status updates, (3) Need formatting unavailable via Clawdbot's Markdown conversion (underline, spoilers, expandable blockquotes, user mentions by ID), (4) Sending alerts, reports, summaries, or notifications to Telegram, (5) Want professional, scannable message formatting wit...

6511 votes

Just Fucking Cancel

Find and cancel unwanted subscriptions by analyzing bank transactions. Detects recurring charges, calculates annual waste, and helps you cancel with direct URLs and browser automation. Use when: 'cancel subscriptions', 'audit subscriptions', 'find recurring charges', 'what am I paying for', 'save money', 'subscription cleanup', 'stop wasting money'. Supports CSV import (Apple Card, Chase, Amex, Citi, Bank of America, Capital One, Mint, Copilot) OR Plaid API for automatic transaction pull. Out...

6511 votes
View all in business →