IMA Note ID Auto Registration

Problem

When multiple agents write IMA notes, note_id often remains only in execution logs, temporary scripts, or conversation records. Later, if you need to determine which agent created a note, when it was created, how it was tagged, or whether it should be added to a shared knowledge base, you have to search through scattered context. Without a shared entry point for this metadata, retrieval and ownership tracking become harder.

How It Works

• Registry entry: Calling register_note(title, note_id, agent_id, tags?) writes the title, note_id, agent_id, and optional tags into a shared registry.json, creating a queryable local registry.
• Knowledge-base sync: After successful registration, the skill automatically uses kb_id to call IMA OpenAPI import_doc, writes the note into the configured knowledge base, and records sync status in registry.log, reducing manual re-import work.
• Query helpers: get_all_notes() returns all records sorted by created_at descending; find_notes(keyword) performs case-insensitive fuzzy matching on titles or tags; get_notes_by_agent(agent_id) retrieves notes by agent.

Boundaries

The skill requires an IMA OpenAPI clientId and API Key, provided via environment variables or local credential files; IMA_REGISTRY_DISABLED=1 temporarily disables registration. Knowledge-base sync depends on IMA API responses; if the API fails, local registration may still succeed. This makes it suitable for persisting note_id into the shared registry first, then debugging sync issues from registry.log.