Tools are Installed, but Knowledge is Still Scattered
If you use WPS, ima, Obsidian, WeChat Favorites, and local files all at once, how do you divide responsibilities to prevent duplication and ensure a single source of truth?
Define the Primary Platform First, then Connect Tools
A robust knowledge base can have multiple inputs, but must have a single primary catalog:
| Platform | Recommended Role | What NOT to Do |
|---|---|---|
| WPS / Kdocs | Shared docs, spreadsheets, collaborative wikis. | Store private raw research files as the sole backup. |
| ima | WeChat article collection, mobile search, RAG queries. | Save secondary conclusions lacking primary links. |
| Obsidian | Local markdown vault, bi-directional links, wikis. | Run automated batch renames without git backups. |
| WeChat Favorites | Low-friction ingestion point, temp inbox. | Use for permanent archiving and structured searches. |
| Lark / Tencent Docs | Team collaborations, feedback logs, publications. | Expose confidential private materials by default. |
Scenario 1: Capturing Raw Inspiration Instantly
Avoid two pitfalls when capturing ideas: either failing to note them down, or letting the AI instantly expand a single sentence into a long, generic article that drifts from the original idea.
- Use Inspiration Hunter to automatically categorize ideas and write them to a markdown inbox.
- Use ima to record notes on mobile and query private knowledge libraries.
- Use Obsidian local directories as the long-term primary database.
Record the following into "Inspiration Inbox". Keep my raw text without expanding or commenting: "AI tool benchmarks should validate outputs, not prompts."Scenario 2: WeChat Collections are Large, but Hard to Search
- Use WeChat Favorite Skill to export, catalog, and route files to ima, Obsidian, or Notion.
- Use URL to Obsidian to scrape web pages, generate summaries, and save them to your vault.
- Use WeChat Public Fetch to export official account articles into local markdown files.
Process this week's WeChat favorites. Read-only; do not delete originals.Scenario 3: ima as a Mobile Knowledge Query Point
ima excels at mobile content gathering, private RAG queries, and WeChat integration. Define target knowledge bases and writing rules when invoking it.
Upload the 3 selected files into the inbox of ima "WorkBuddy Case Library".Scenario 4: Maintaining Obsidian Wikis over Directories
- Use Obsidian Core Notes to manage core index entries, topic digests, and directory structures.
- Use Obsidian Long-term Memory to manage long-term project boundaries and memory logs.
Analyze this official account article using WorkBuddy and save it to my Obsidian assets folder.WorkBuddy will parse the text, extract authors, and output structured markdown entries.
References
Part of this series
WorkBuddy In Action
View all guides in this series →