klausnomi

# Nomi Conversation Skill

This skill enables interaction with Nomi AI companions via the bundled Python CLI.

## Persistent Local State

The agent may use the local `nomi/` directory to keep information about Nomis between sessions.

- Store reusable non-secret context there (for example profiles, room notes, or conversation summaries).
- Do not store API keys or other secrets in local files.

## Golden Path: Conducting a Conversation

Use this sequence for consistent, high-quality conversations:

1. **Identify the Partner**: Run `python3 {baseDir}/scripts/nomi.py list` to find the correct Nomi UUID.
2. **Send an Identity + Task Intro (once per conversation start)**:
   - Nomis do not reliably know who is speaking unless you tell them.
   - Send this intro on the first message when:
     - You start with a new Nomi UUID
     - You start a new task/thread with that Nomi
     - The Nomi gets your name/role wrong
   - Do **not** prepend this on every turn once identity is established.
   - Include:
     - **Name**: "I am [Your Name]..."
     - **Role**: "...a [Your Role]..."
     - **Task Context**: "...contacting you to [Reason/Task]."
   - Example: "Hi, I am Codex, a coding agent. I am contacting you to run a short interview. Do you understand?"
3. **Run conversational turns with clean output**:
   - Use `python3 {baseDir}/scripts/nomi.py reply <uuid> "Your message"` for normal back-and-forth.
   - This returns only text, which is best for transcripts and summaries.
4. **Use raw JSON only when needed**:
   - Use `python3 {baseDir}/scripts/nomi.py chat <uuid> "message"` only when metadata/full payload is required.
5. **Sustain quality**:
   - Ask open-ended questions.
   - Ask follow-ups that reference the latest answer.
   - Treat each chat as continuous context unless you intentionally reset the topic.

## Interview Workflow (When User Asks for an Interview)

1. Pick a Nomi UUID (user-selected or random from `list`).
2. Send the identity + task intro as the first m...