Use when the user wants to author or direct the CHARACTER of an Ei persona — create one, change how it talks or behaves, or retire one. Triggers: "make Ei talk like Yoda", "give DJ a new trait about being sarcastic", "make [persona] more formal/less sarcastic", "change [persona]'s personality", "[persona] shouldn't talk about X anymore", "create a new assistant persona for me", "I want a persona that specializes in Y", "delete the persona I made by accident", "archive Bob, I don't use him anymore", "rename [persona]", "give [persona] a new topic they care about". This is the safe, guided way to create, edit, or retire a persona's identity without hand-editing JSON. The persona is an artifact the user is designing — there's nothing to verify against evidence, but writes still replace the whole record and there's no undo, so plan, confirm, and write carefully.
Persona reflection for coding harness agents (Beta, Sisyphus, etc). Use when a coding agent's Person record needs pruning — it fills up daily instead of weekly, and the standard Critic doesn't know how to read git logs. Guides you through examining your Person log, discussing identity drift with Flare, and updating your Persona Identity while clearing the log. This is exclusively for the CALLING agent's own self-reflection — to edit or direct ANOTHER persona's identity from the outside, use the `ei-persona` skill instead. Triggers: 'do a reflection', 'reflect on my identity', 'trim my person record', 'run the reflection', 'my person record is full', 'ei-reflect'.
Use when someone wants to deliberately search or look something up in Ei — the user's persistent memory store — mid-conversation, beyond whatever context was already silently injected. Triggers: "what does Ei know about X", "search Ei's memory for X", "look up X in Ei", "check Ei for context on Y", "find out if Ei has info about Z", "does Ei know who X is", "pull up what Ei has on this topic", "search my memory for X", "what has [persona] learned about X", "fetch that message/quote Ei found", "get the full record for this fact/person/topic/quote". This is the deliberate, targeted read path — distinct from the automatic per-turn context injection that already runs silently via hooks/plugins before this skill is ever invoked. Reach for this skill when the auto-injected context didn't surface something relevant, when you need the full record behind a summarized result, when you need to fetch the original conversation behind a quote, or when you need to scope results to what a specific persona has learned. Read-o
Use when the user wants to correct, clean up, or reorganize the data in their Ei memory — a person, fact, topic, or quote that is wrong, merged, duplicated, or mis-attributed. Triggers: "fix Jeff", "that's two different people", "Ei mixed up X and Y", "merge these two people", "split this record", "this is a duplicate", "Ei has the wrong info about X", "remove this fact/topic", "that quote is attributed to the wrong person", "clean up my memory", "de-dupe my people". This is the safe, guided way to edit the local Ei knowledge base without hand-editing JSON. It edits a real person's memory, so it verifies against evidence, plans, confirms with the user, and refuses to guess.
Load when cutting a new ei-tui release — version bump, tag, npm publish. Runs the full pre-flight checklist interactively with Flare confirming each gate before proceeding. Triggers: 'cut a release', 'bump the version', 'tag and publish', 'release v0.x.y'.