Repository inventory

skogai/lore

Skills indexed from this repository, with install-style signals scoped to the repo.
2 skills2 GitHub stars0 weekly installsShellGitHubOwner profile

Overview

This skill turns technical work—commits, bug fixes, design decisions—into narrative lore entries that act as persistent agent memory. It teaches a simple data model (Entry, Book, Persona) and patterns for compressing technical meaning into memorable mythological stories for long-term retrieval.

How this skill works

You create or select a persona that will narrate the story, transform the technical artifact into a mythic narrative, and store the result as an Entry linked into a Book that the persona reads. The workflow supports manual creation and LLM-assisted generation, and enforces linkage so entries are never orphaned.

When to use it

  • Recording a commit, PR, or deployment as an agent memory
  • Documenting bug fixes or incident retrospectives in narrative form
  • Capturing design decisions or architecture changes as memorable lore
  • Building a persona-aligned knowledge base for an agent team
  • Onboarding agents with chronicle books that summarize system history

Best practices

  • Always pick or create a persona first and match voice and tone
  • Write non-empty content using mythic metaphors, not raw technical jargon
  • Assign a category (event, character, place, object, concept) that fits the content
  • Link each entry to a book and ensure the book lists the persona as a reader
  • Tag entries with searchable keywords to aid discovery and retrieval

Example use cases

  • Transforming a critical authentication bug fix into a battle tale narrated by a cautious guardian persona
  • Converting a major refactor into a story about reshaping the realm’s foundations for future builders
  • Logging a release as an event chronicle so agents remember the conditions and consequences
  • Creating persona profiles that capture mode-of-operation and heuristics as character entries
  • Generating a concept entry that encodes architectural principles as a teaching parable

FAQ

An Entry needs id, title, content (non-empty narrative), category, tags, and a book_id linking it to a Book.

How do I avoid orphaned entries?

Always add the entry to a Book with add-to-book and confirm the Book lists a persona in its readers array.

2 skills

More from this maintainer
Other repositories and skills published under the same GitHub owner.
Skills library
Jump back to the full directory or explore grouped topics.
Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational