Namishsaxena Lore
- 3 repo stars
- Updated January 16, 2026
- namishsaxena/lore
namishsaxena-lore is a Claude Code plugin that gives agents scoped, queryable project knowledge instead of oversized static context files.
About
namishsaxena-lore is a Claude Code plugin that implements Lore as a knowledge memory layer for AI agents. developers drowning in AGENTS.md, copied architecture notes, and oversized CLAUDE.md files can store facts in scoped entries and let the agent query what matches the open files and active task. The bundle advertises MCP support, native tooling, and selective retrieval so integration work stays in the build phase rather than becoming a manual paste ritual each session. It targets developers who run Claude Code daily on real repos and need durable, structured memory without maintaining a second wiki. Install it when context rot slows you down or when multiple features share overlapping but not identical background. It is not a full vector database product; it is an opinionated memory plugin meant to replace bloated static context with something the agent can pull on demand. Expect setup around database or storage configuration per the upstream repo, then query-driven use as you iterate features.
- Scoped knowledge entries tied to files and tasks instead of monolithic context dumps
- Queryable retrieval returns only relevant lore for the current work
- MCP and native Claude integration for agent-side memory access
- Selective context loading to cut noise and token bloat
- Documentation and integration hooks packaged as a single Claude Code plugin
Namishsaxena Lore by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin install namishsaxena-lore@namishsaxena/loreAdd your badge
Show developers this plugin is listed on Skillselion. Paste this into your README.
| repo stars | ★ 3 |
|---|---|
| Last updated | January 16, 2026 |
| Repository | namishsaxena/lore ↗ |
What it does
Give Claude Code scoped, queryable project knowledge instead of dumping entire context files into every session.
Who is it for?
Best when you're running Claude Code on a long-lived codebase and want MCP-backed memory without hand-curating prompts each time.
Skip if: Skip if you already run a dedicated RAG platform with firm compliance requirements and no appetite for another memory store.
What you get
After you register Lore, the agent pulls only task-relevant knowledge entries so sessions stay focused and context stays maintainable.
- Installed Lore plugin wired into your Claude Code workspace
- Scoped knowledge entries the agent can query by file and task
- Reduced reliance on monolithic context paste-ins
By the numbers
- Plugin bundle count: 1
- Source repository: namishsaxena/lore
- Advertised integrations: MCP, native Claude tools, selective retrieval
Recommended Plugins
0pg Cc MarketplacePersonal Claude Code plugins collection
1shot Labs Squadron Comms PluginVoice communication system with ElevenLabs TTS for multi-agent coordination in Claude Code3
23blocks Os Ai MaestroAI Agent Orchestrator with Skills System - Give AI Agents superpowers: memory search, code graph queries, agent-to-agent messaging.733
3commas Io Commas ClaudeThis is a repo with shared agents and skills used company-wide4
884js Agent Plugins1 plugin
A5c Ai BabysitterBabysitter enforces obedience to agentic workforces and enables them to manage extremely complex tasks and workflows through deterministic, hallucination-free self-orchestration1.6kHow it compares
Agent knowledge-memory plugin with MCP retrieval, not a generic documentation skill or skills.sh marketplace bundle.
FAQ
Who is Namishsaxena Lore for?
Developers using Claude Code who need structured, queryable repo knowledge instead of pasting large context files into every chat.
When should I use Namishsaxena Lore?
Use it during Build when you are standardizing agent tooling, especially once static CLAUDE.md or AGENTS.md files grow unwieldy across modules and tasks.
How do I add Namishsaxena Lore to my agent?
Add the namishsaxena/lore Claude Code plugin from the repo marketplace entry, complete any Lore database or MCP setup in the upstream docs, then query lore from Claude during coding tasks.