OpenDemi Office Suite

What problem it solves

Office workflows often fragment across tools: files need manual classification, data needs ad hoc scripts, reports copy templates, and knowledge lookups jump between platforms. OpenDemi Office Suite gives those tasks a single routing entry point. It prefers existing local skills such as file-organizer, doc-forge, and weknora-connector; when none are present, it falls back to embedded capabilities. The point is not one more universal button, but clearer delegation, confirmation, and fallback.

How the skill works

• File organization: it confirms the target directory, scans files, proposes classification by type, date, or project, detects duplicates, and suggests names like [Category]_[Description]_[Date]_v[Version]. Destructive actions require explicit confirmation.
• Planning and documents: it builds six-column task plans and, when useful, a CSS timeline. Reports, summaries, and notices use fixed structures to reduce formatting overhead.
• Data analysis: it supports descriptive statistics, anomaly detection, trend analysis, and price/quantity/mix variance decomposition. Conclusions must have a computational basis or source reference.
• Office formats: with python-docx and openpyxl, it can work with Word and Excel; without those dependencies, it degrades to structured Markdown with manual import guidance.
• Knowledge routing: retrieval is layered by trust: attachments, local knowledge bases, conversation history, and web search. External results are marked for independent verification; missing items are stated honestly rather than fabricated.

Boundaries and cautions

It fits local environments where directory permissions are clear and data sovereignty matters. Without Python dependencies, document and table output leans Markdown; without WeKnora or IMA, structured navigation and knowledge-base citation are limited. The skill may record preferences such as anomaly thresholds, formatting habits, and corrections, but it does not self-modify core logic and new capabilities require consent. For sensitive files, grant only the needed directory access and keep manual review for deletion, renaming, and format conversion.