# Keep Fictional Lore Consistent with De Lore Is

Fiction projects accumulate conflicting facts, unresolved alternatives, and revisions that are difficult to track. This skill guides local De Lore Is workflows for structured lore, continuity checks, and author-approved rulings.

## Install

```bash
npx skillstore add jeffreykentjr/deloreis
```

## Metadata

- Status: approved
- Slug: jeffreykentjr-deloreis
- Skillstore revision: r1
- Version status: missing
- Tree hash: 16379d91b6f3367f3cd3b3743091cd91fc101d785487202bdab01b39b01cf6c2
- Author: jeffreykentjr
- GitHub username: jeffreykentjr
- License: MIT
- Repository: https://github.com/jeffreykentjr/deloreis/tree/40d230a79c0f4063f57ada0a2d10c41754948a3a/skills/deloreis
- Ref: 5dbcf287869d7ca5fd8e7c9b64a5640d44649b36
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network
- Quality score: 75
- Public page: https://skillstore.pages.dev/skills/jeffreykentjr-deloreis
- Manifest: https://skillstore.pages.dev/api/skills/jeffreykentjr-deloreis/manifest

## Capabilities

- Guide local runtime setup and project-scoped MCP registration using the included first-session walkthrough.
- Record entities, facts, relationships, events, and event-anchored states through typed authoring tools.
- Check structured claims against declared rules and explain findings through supporting claims and decisions.
- Keep proposed alternatives and hypothetical accounts distinct from established lore.
- Guide author-approved retcons while retaining earlier claim identifiers and decision history.
- Guide rendered lore export and linked Markdown wiki generation using specialist tools and the CLI.

## Use Cases

- Maintain a Novel Series Bible: Query established character and setting facts before drafting, then check proposed additions against recorded lore.
- Track Campaign History: Record campaign events, ordering, and changing allegiances without confusing story changes with retcons.
- Review Competing Story Accounts: Compare proposed alternatives, inspect their consequences, and record the selected ruling while preserving earlier support.

## Prompt Templates

### Start a Small Lore Project

```
Help me set up De Lore Is for a small sample of my notes. Confirm runtime availability and ask which details are established.
```

### Check a Chapter Addition

```
Query established lore relevant to this scene: [scene]. Propose its new factual claims, check continuity, and show conflicts before accepting changes.
```

### Compare Story Alternatives

```
Compare these accounts: [alternatives]. Keep them proposed or hypothetical, explain their consequences, and ask for my ruling before changing established lore.
```

### Plan a Traceable Retcon

```
Review this revision: [revision]. Inspect support and differences, retain old claim IDs, and request approval before recording decisions or defeating earlier support.
```

## Limitations

- The skill does not install or bundle the De Lore Is runtime; a separate installation and client configuration are required.
- Checks cover structured claims and recorded rules, not manuscript prose or every possible continuity error.
- The host application must enforce approval, access control, and concurrent-write policy; some operations update the store directly.
- World facts do not establish character knowledge, and De Lore Is is not general-purpose agent memory.

## Best Practices

- Start with a small sample, distinguish established facts from ideas, and agree on constraints with the author.
- Inspect findings and differences before acceptance; follow host review policy before operations that update the store directly.
- Track source decisions and claim IDs, refresh workspace digests after changes, and open a fresh workspace after another session commits.

## Anti Patterns

- Do not change lore merely to silence findings or declare every predicate single-valued.
- Do not treat chat recollection, edited wiki pages, or direct agent edits to rendered files as the project store.
- Do not assume every mutation is staged or that discarding a workspace reverses recorded decisions.

## Security Audit

- Audited at: 2026-11-05T14:09:36.482\+00:00
- Summary: All 59 static findings are false positives involving Markdown formatting, quoted local setup commands, descriptive text, or documentation links. No evidence found of prompt injection, credential theft, or data exfiltration in the reviewed skill files. The external runtime was not reviewed, and the documented local workflow delegates authorization and review policy to the host.

## Stats

- Views: 0
- Downloads: 0
- Favorites: 0
- Popularity score: 0