lore

Slot external knowledge from local directories, URLs, or Git repositories into Rune constructs.

2|Updated Jan 2, 2026
One-click install
npx skills add https://github.com/0xHoneyJar/rune --skill lore
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lore
Source: https://github.com/0xHoneyJar/rune/tree/main/.claude/skills/lore
Command: npx skills add https://github.com/0xHoneyJar/rune --skill lore

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Lore enables you to slot curated external knowledge into Rune constructs, enriching components with trusted references and improving learning and adaptation without altering runtime behavior.

Core Features & Use Cases

  • Knowledge slotting: Attach external references to specific constructs (Glyph, Sigil, Rigor, Wyrd) to augment behavior and learning.
  • Reference management: Organize sources under .claude/references and wire them to relevant rules.
  • Quick Slot: Use simple commands to slot and wire new sources to desired constructs, enabling rapid knowledge integration.

Quick Start

Use the lore command to slot external knowledge for a target construct and install it under .claude/references.

Frequently Asked Questions about lore

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I import external knowledge into local development constructs?

You slot external knowledge by sourcing references from local directories, URLs, or Git repositories and mapping them to target constructs, which installs them under .claude/references for immediate use.

What is the best way to attach reference documentation to specific system components?

You slot external knowledge by sourcing references from local directories, URLs, or Git repositories and mapping them to target constructs, which installs them under .claude/references for immediate use.

Can I use Bash commands to wire external Git repository sources into my project?

Bash-based commands with standard tools support wiring external Git repository sources into project constructs, installing the fetched knowledge directly into the .claude/references directory structure.

Does integrating external references change how my components run at runtime?

Integrating external references enriches components with trusted sources for learning and adaptation, but it explicitly does not alter runtime behavior, keeping execution stable while augmenting knowledge.

How do I organize and manage external knowledge sources for my development environment?

Reference management organizes external knowledge sources by installing them under .claude/references and wiring them to relevant rules, ensuring curated references map correctly to their target constructs.