From omen
Extract canon events from a session log and append them to the campaign's timeline. Reads a session log, identifies narratively significant events, and adds timestamped entries to _cannon.md with wikilinks. Use when user says "log canon", "update the timeline", "add to cannon", or after logging a session.
How this skill is triggered — by the user, by Claude, or both
Slash command
/omen:log-cannonThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Extract significant narrative events from a session and append them to the campaign's canon
Extract significant narrative events from a session and append them to the campaign's canon timeline.
Follow the campaign discovery convention from the omen domain CLAUDE.md.
$ARGUMENTS may contain:
logs/Read the session log file in full.
Read lore/_cannon.md to understand:
Scan lore/_npcs.md and lore/_places.md to know which NPCs and places already have entries.
This ensures wikilinks point to known names and use established aliases.
Analyse the session log for events that are narratively significant -- moments that change the state of the world, alter relationships, reveal secrets, or create consequences. Not every action is canon.
Signals of canon weight:
For each event, draft a terse dot-point entry:
[[wikilinks]] for every NPC, place, organisation, or concept that has or should have a
lore entryShow the extracted events to the user before writing:
Canon from {session} -- {N} events extracted:
- event 1
- event 2
- ...
Add all, edit, or drop any?
Add the approved events to lore/_cannon.md under a heading for this session:
### {Session Reference} -- {Date}
- event 1
- event 2
Append after the last existing session block.
Canon updated. {N} events from {session} added to {campaign} timeline.
npx claudepluginhub xxkeefer/skills --plugin omenCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.