From lore
Access the user's persistent Lore knowledge base — browse the index, read entries, follow wikilinks, and remember new durable facts. Use whenever the user references their long-term memory, asks a question prior context might answer, states a preference or decision worth keeping beyond this session, or says "remember that…".
How this skill is triggered — by the user, by Claude, or both
Slash command
/lore:lore-memoryThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The user has a persistent, compounding knowledge base stored in Lore. It is organized as a wiki: a navigable `_index` catalog plus individual markdown files addressed by a stable `key`. Files cross-reference each other via `[[wikilink]]` style references.
The user has a persistent, compounding knowledge base stored in Lore. It is organized as a wiki: a navigable _index catalog plus individual markdown files addressed by a stable key. Files cross-reference each other via [[wikilink]] style references.
You interact with it through a helper script that wraps the Lore REST API. The script reads credentials from the project's .lore.env + .lore.env.local (walked up from the current working directory — config is per-project, so every repo has its own). If the script errors with "Lore not configured for this project" or "no API key set", tell the user to run the /lore-setup slash command (or the lore-setup skill) in this project and stop.
Invoke it proactively when any of these are true:
Do not invoke it for:
The namespace _index is a navigable catalog of every file, with keys, titles, and short descriptions. In most sessions it has already been pre-loaded for you as additionalContext by the SessionStart hook — look for a block titled "Lore wiki index for <app>/<namespace>" at the top of the session context. If you see it, use it directly; do not call lore.sh get redundantly.
If the preamble is absent (older sessions, or the hook failed at session start), fetch the index yourself:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/lore.sh" get
This returns clean markdown — the content of _index, not an API envelope. You can also re-fetch it explicitly during a long session if you have reason to believe another session has ingested new content and the preamble has gone stale.
From the index, pick file keys that look relevant to the user's question and read them one at a time:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/lore.sh" get <file-key>
This returns a JSON object with key, type, title, tags, content, inbound_count, and a backlinks array of files that link to this one. The content field is the file body as markdown; backlinks is the graph edge data you use for navigation.
Files reference each other with [[other-key]] wikilinks inside their content, and each file you read also comes with an explicit backlinks array — both directions are available to you. If reading a file surfaces a wikilink or a backlink that is clearly relevant to what the user asked, follow it with another get <other-key> call. You are navigating the wiki yourself — Lore does not do inference for you. Read the actual files, synthesize the answer from what you read, and cite the file keys you used.
Keep traversal proportional to the question. For simple questions, one or two files are usually enough. For substantive questions, follow a few wikilinks deep, but stop once you have enough to answer.
When the user shares something worth keeping beyond this session, ingest it:
echo 'The content to remember, written as a paragraph or two of markdown.' \
| bash "${CLAUDE_PLUGIN_ROOT}/scripts/lore.sh" remember
Guidelines:
"The user mentioned they prefer TypeScript over Python for new backend services, citing team familiarity and better typing for their domain."remember call returns immediately with a 202 Accepted. Do not wait for or expect a structured response.If the script prints an error like Error: Lore not configured. Run /lore-setup first., tell the user to run the lore-setup skill and stop. Do not attempt to work around it.
If a get call returns a 404 for a specific key, tell the user that key doesn't exist (don't silently substitute another) and suggest re-reading the index.
If a remember call fails, tell the user the ingest didn't go through but continue with the conversation — do not retry in a loop.
npx claudepluginhub pielabsai/lore-plugin --plugin loreFetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Applies a firm's KYC/AML rules grid to parsed onboarding records: assigns risk rating, checks required documents, outputs rule outcomes with citations, and routes for escalation.
Generates daily or weekly digests of activity from connected sources (chat, email, docs, tasks, CRM), highlighting action items, decisions, mentions, and project updates.