lore

Connect agents to Lore backends for governed reads, mutations, and schema proposals.

1|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/pengelbrecht/skills --skill lore-pengelbrecht
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lore
Source: https://github.com/pengelbrecht/skills/tree/main/skills/lore
Command: npx skills add https://github.com/pengelbrecht/skills --skill lore-pengelbrecht

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables autonomous agents to securely connect to a Lore backend to read, mutate with governance, and propose schema changes.

Core Features & Use Cases

  • Context-first data access: fetch schema, knowledge, and governance rules before acting.
  • Governance-driven mutations: route all changes through Lore's governance pipeline with audits.
  • Schema proposals and learning: propose changes, learn from results, refine knowledge, and improve agent effectiveness.

Quick Start

Authenticate to Lore and run a basic query to verify access.

Frequently Asked Questions about lore

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

FAQPage Schema
How do I connect an autonomous agent to a Lore backend for secure API access?

Secure Lore backend access is enabled by authenticating the agent and running a basic query through the /v1/query endpoint to verify connectivity and apply governance rules.

How do I execute raw SQL mutations with governance and audit trails?

Raw SQL mutations are routed through the /v1/mutate endpoint, ensuring all changes pass through Lore's governance pipeline to generate audit trails before execution.

What is context-first data access for governance-aware agents?

Context-first data access requires fetching schema, knowledge, and governance rules before acting, ensuring autonomous agents understand operational boundaries before querying or mutating data.

Can I propose schema changes dynamically through the Lore API?

Schema changes are proposed dynamically via the /v1/schema/propose endpoint, allowing agents to submit modifications, learn from results, and refine knowledge for future tasks.

Does Lore backend access enforce access policies for autonomous agents?

Lore backend access enforces access policies and safe API usage by requiring governance-driven mutations and audit trails across all CRUD operations and knowledge learning tasks.

What are the limitations of using raw SQL mutations with governance pipelines?

Raw SQL mutations cannot bypass Lore's governance pipeline; all changes must route through /v1/mutate to ensure audit trails and access policies are applied before execution.