IMA Notes and Knowledge Base Assistant

Problem

Agents can call external APIs, but integrating IMA still hits practical failure modes: Chinese text sent through PowerShell 5.1 becomes GBK-mangled; knowledge-base file uploads accidentally rename files; and a request such as “add this to a note” is hard to route between append_doc and add_knowledge.

How the Skill Works

The skill separates the notes and knowledge-base modules:

• Notes content: search, create, append, and read document content through the notes module.
• Knowledge-base entries: upload files, add links, attach notes, and retrieve source content through the knowledge-base module.
• Cross-module tasks: read both submodule guides first, then call APIs in order, for example “record knowledge-base content into a note.”

Before calling the API, it checks credentials and runtime environment. Text writes require UTF-8 validation; binary uploads preserve original bytes; unsupported inputs such as video, Bilibili/YouTube URLs, and file:// links are rejected with a pointer to the IMA desktop client. Errors are split into script-level -100/-200 results and backend business-level code and msg values.

Boundaries

This is useful for engineering agents that already have an IMA Client ID and API Key. It is not meant for downloading videos, transcoding binary attachments, or changing upload filenames. When user intent is ambiguous, the agent should first confirm whether to create a new note or append to an existing one.