IMA Knowledge Base and Notes API

Problem

Working with IMA notes and knowledge bases often requires choosing between several APIs: appending to an existing note, creating a note, uploading a file, adding a web link, or searching and browsing items. The skill standardizes that routing and keeps credential handling out of the conversation.

How it works

The skill starts from ima-skill, reads SETUP_TOKEN.md, and fetches credentials inline for each command through get-token.sh or get-token.ps1. All calls are sent as HTTP POST + JSON to https://ima.qq.com. It routes user intent into two modules: notes for searching, browsing, reading, creating, and appending notes, and knowledge-base for uploading files, adding web links, searching, and browsing knowledge base entries. For ambiguous requests such as “save this to a note” versus “add this file to the knowledge base,” it first determines whether the target is note content or a knowledge base item, then selects the matching operation.

Boundaries

It does not persist credentials across sessions and will not display real Client ID or API Key values. Writes to notes require valid UTF-8 text; file uploads should preserve the original binary content. In PowerShell 5.1, the request body must be explicitly converted to UTF-8 bytes to avoid silent Chinese encoding issues.