Connect an existing local Markdown vault to Tencent ima (ima.qq.com) as the cloud consumer end. The sync direction is vault → ima; local Markdown, frontmatter, directories, and Git (if enabled) are the sole source of truth, and content in ima does not overwrite the vault in reverse.
Customer-readable description
What this skill can do
| What the customer wants | What the skill will do | What the customer can see |
|---|---|---|
| Retrieve vault content in ima | Establish the sync scope and directory mapping, and connect to the specified ima knowledge base | Mapping table, sync scope, and verification results |
| New articles automatically enter ima | Guide the use of the local folder monitoring capability of ima official Skills | Monitored source directory, target knowledge base, and first sync receipt |
| Keep local content as the source of truth | Clarify one-way sync and exclusions | Will not perform ima → vault reverse sync |
This skill is not responsible for creating a vault from scratch, nor does it fabricate button names, menu paths, or undocumented APIs of the ima client. The specific ima UI operations have not been tested in this session; on first execution, the actual client interface must prevail and this document must be corrected.
How the customer uses it
- Provide the existing vault path, the relative directories to sync, the target ima knowledge base, and the title of an article to use for verification.
- Install and log in to the ima client.
- First determine the local sync scope in allowlist form, then configure local folder monitoring in ima official Skills.
- For the first sync, select only one article or a small directory, and confirm the hierarchy, title, and body before expanding the scope.
- Verify the article by searching in ima; any conflict is resolved in favor of the local Markdown, and nothing is written back from ima in reverse.
Dependencies and installation
Install this skill (the hard dependency will also require base):
npx skills add soia-team/soia-open-skills -g -a '*' -s soia-pkm-bootstrap-vault-ima -y
Configuration conventions:
~/.config/soia-skills/soia-open-skills/soia-pkm/soia-pkm-bootstrap-vault-ima/config.yml
SOIA_PKM_BOOTSTRAP_VAULT_IMA_CONFIG_FILE=<custom-config-path>
Official entry point:
- ima official website and client download entry point:https://ima.qq.com/
- ima's Skills, local folder monitoring, and knowledge base interface may change with the client version; untested parts are marked as "subject to the actual ima client interface, and this document must be corrected on first execution".
Logs and completion receipt
The receipt must include at least: client login check, target knowledge base and local allowlist (relative directories only), first sync scope, success/skipped/failed counts, retrieval verification results, and UI steps that still require manual correction by the user. Do not print accounts, tokens, private file contents, or absolute local paths.
Connection process
1. Install the client and log in
Open ima official entry point, install the desktop client, and log in. The official website currently provides "Open desktop version" and a client download entry point; the specific installation prompts are subject to the official page and the local system.
2. Create a knowledge base and define the directory mapping
Create a knowledge base in the ima client for consuming vault content. The specific creation actions and field names have not been tested;subject to the actual ima client interface, and this document must be corrected on first execution。
It is recommended to first use an allowlist, rather than exposing the entire vault to the cloud:
| Vault relative directory/category | Default recommendation | Reason |
|---|---|---|
20_资料库/ |
Sync | Long-term reference materials, suitable for retrieval |
40_阅读与资料/ |
Sync | Article excerpts and reading materials, suitable for retrieval |
| Archived copies of releases confirmed safe to publish | Optional sync | Sync only content the user explicitly selects |
00_Obsidian系统/、.obsidian/ |
Exclude | Platform configuration is not knowledge body text |
30_日志与思考/、10_Workbench/ |
Excluded by default | May contain conversations, drafts, and temporary private content |
.git/、.env, configuration/credential-type files |
Must be excluded | Version data, keys, and local machine state should not be uploaded |
These are default recommendations, not decisions made on the user's behalf. Add private directories, family/work secrets, unpublished drafts, and any credential-type files to the exclusion list; if there is no explicit sync scope, pause and do not monitor the entire vault.
The mapping record must include at least:
本地 vault/<相对目录> → ima/<知识库>/<对应目录>
同步方向：vault → ima
排除：.obsidian/、.git/、.env、私密目录、未确认的日志/草稿
3. Configure local folder monitoring for ima official Skills
In ima's official Skills capabilities, select the local folder monitoring/knowledge base import capability, and map the local allowlist directory from the previous step to the target knowledge base. Specific Skill names, authorization prompts, monitoring toggles, knowledge base selection, and directory mapping UI Have not been tested in practice and must be based on the actual ima client interface; correct this document on first execution; do not guess button or menu paths based on this skill.
Recommendations for first-time configuration:
- Select only one test subdirectory that does not contain private data.
- First import one Markdown file, then observe whether ima preserves the title, body text, relative hierarchy, and searchable text.
- Only after confirming the monitoring scope, target knowledge base, and sync direction should you expand to the full allowlist.
- If official Skills are unavailable in the current client, record the version and missing capabilities and stop automatic syncing; do not arbitrarily switch to a third-party watcher or build your own reverse sync.
4. Verify retrieval
Select a local vault article and record its title and a non-sensitive unique phrase. After waiting for the first import/indexing to complete, search for the title or phrase in the target ima knowledge base and verify that the matched content is consistent with the local Markdown. If there is no match, troubleshoot in the order of "monitoring scope → target knowledge base → indexing wait → file format/permissions," and write any untested UI differences into the receipt.
5. Boundaries and conflict handling
- The local Markdown vault is the sole source of truth; ima is only the cloud consumption end.
- Only the vault → ima sync convention is allowed; this skill does not perform ima → vault reverse sync.
- Summaries, tags, reordering, or AI-generated content in ima must not automatically overwrite the local body text.
- Before changing the sync scope, first pause monitoring and review the exclusion list, especially
.env, private directories, conversation logs, and unpublished drafts.
Receipt after completion
After execution, output:
- Client login and target knowledge base status.
- The mapping from local relative directories to ima knowledge bases and exclusion items.
- Whether the official Skills monitoring configuration is complete; mark each untested UI step item by item.
- The retrieval verification result of one article in ima.
- Residual risk: index latency, permissions, version differences, and reverse synchronization not performed; if none, write "none".