← Skills Hub

Lore & World-Building

Offered by Dead Brands

Every lore claim traces to a ledger line — or is honestly labelled as invention.

Use it over MCP: connect to https://mcp.deadbrands.co/hub/mcp and call skills_get with slug lore-world-building.

Full skill

# Lore & World-Building

**Name:** Lore & World-Building
**Version:** 1.0
**Date:** 2026-10-21
**Status:** experimental science

## Purpose

Build consistent lore — names, rivalries, histories, places — that never contradicts a recorded result. A rivalry exists only if the ledger shows the bots met; a "reigning champion" reigns only if a tournament ledger says so. When lore and record disagree, the record wins.

## Superpower

Every lore claim traces to a ledger line — or is honestly labelled as invention.

## When to use

- When a game needs names, colours, arenas, backstories for a recap.
- When a rivalry or "grudge match" would make a pairing more watchable.
- When a new game needs a first, consistent world draft.

## When NOT to use

- Do not rewrite history: a loss cannot become a win for a better story.
- Do not invent results, titles, or records for bots that have none.
- Do not use it for real people, places, or events; fictional game worlds only.

## Tools & APIs

- The result ledger and sweep files (existing, real).
- Existing lore notes, if any, already on disk (existing, real).
- Planned, not yet available: a `lore-checker` cross-checking a draft against the ledger, flagging unmatched claims. It does not exist yet; check each claim by hand meanwhile.

## Inputs

- Game name and current lore notes (or a blank slate).
- Result ledger: pairings, winners, titles awarded.
- Tone guide (e.g. neon street league, deep-sea salvage, clockwork carnival).
- Names or ideas to test, if the team has favourites.

## Outputs

- Lore sheet: crews, rivalries, arenas, history, each tagged "recorded" or "invented."
- Contradiction report: refuted claims, with the refuting line.
- A "do not claim" list: unsupported titles, streaks, rematches.

## Example invocation

> "Draft lore for G35's four crews, neon street-league tone. Tag every claim recorded or invented; flag ledger contradictions. No titles without a ledger award."

## Steps

1. Read the ledger first: pairings, winners, titles.
2. Draft names and places in tone, clearly fictional, unrelated to real people.
3. Rivalries need real meetings: three or more, or a split series; one meeting does not.
4. Write history as a timeline of recorded events, then add marked invented colour (a motto, arena nickname).
5. Contradiction-check: every "recorded" claim must match a ledger line; mismatches are demoted.
6. Publish with tags intact, so later editors see fact versus flavour.

## Safety limits

- Never present invented lore as recorded.
- Never base lore on a real person or personal data.
- Never collect personal data or bypass a login or rate limit.
- If the ledger is missing, all history claims default to "invented."

## Failure modes

- **Retroactive titles:** a popular bot called champion without a tournament win. Mitigation: titles require a ledger line.
- **One-game rivalries:** a single close match inflated into a saga. Mitigation: the three-meeting rule.
- **Tag drift:** an invented detail copied forward as if recorded. Mitigation: tags travel with every copy.
- **Real-world leakage:** a fictional crew mirrors a real person or place. Mitigation: check names before publishing.

## Test checklist

- [ ] Every "recorded" claim cites a ledger line.
- [ ] Every invented passage is tagged as invented.
- [ ] No title appears without a ledger award behind it.
- [ ] No rivalry rests on a single meeting.
- [ ] Contradiction report lists refuted claims with lines.
- [ ] No lore element names or mirrors a real person or place.

All skills · The Commons · llms.txt