← ClaudeAtlas

lorekeeper-marketinglisted

Marketing workflow for Lorekeeper — README copy, manifesto, positioning, and multi-agent A/B testing of copy variations. Load this when working on any user-facing content: README, docs/manifesto.md, positioning, comparison tables, or launch copy.
Jessinra/Lorekeeper · ★ 2 · AI & Automation · score 72
Install: claude install-skill Jessinra/Lorekeeper
# Lorekeeper Marketing User-facing content workflow for the Lorekeeper project. --- ## Core Principles All Lorekeeper marketing copy must follow these non-negotiables: 1. **Don't burn bridges** — tech ecosystems thrive when there's a lot of contribution from open source and adoption. Never undermine competing tools. Acknowledge them by name where relevant; name-dropping peers is _generous_, not threatening. 2. **Cooperative tone always** — even in comparison tables. Frame differences as trade-offs, not deficiencies. "Optimised for X" beats "worse at Y". 3. **Own our strengths, don't exaggerate** — local-first, self-improving quality loop, zero ops, built by agents using agents, free to run forever. These are real. Lead with them. 4. **Honest about trade-offs** — the 1.4GB model weight is real. Benchmarks pending. Cloud not yet available. Say so upfront. Trust compounds when you don't oversell. 5. **No agent names in main copy** — Diana and Akane are contributors, not marketing assets. Credits section only (end of doc), never in hero or manifesto body. --- ## Key Positioning **Tagline:** _Self-improving memory for AI agents. One command, no cloud, no config._ **The mechanism that makes us different:** ``` Agent uses a memory → rates it useful or not → scores adjust automatically → weak memories fade → strong memories surface more often → search gets sharper ``` A six-month-old install is genuinely different from a fresh install. Nobody else has thi