using-ixf-toolboxlisted

# Using ixf Toolbox Use this as a lightweight routing skill for ixf Toolbox workflows. Users do not need to name this skill or any domain skill explicitly. Use background routing for natural user requests, then hand off to the correct domain skill. This skill does not replace the domain skills and does not perform direct writes. ## Runtime Boundary Go `ixf` only. Do not call `ixfdoc` or `ixfwrite`. Do not use Python fallback, Python-compatible readers, or Python-compatible writers. ## Routing - Use `docs/agent-routing.md`, `AGENTS.md`, and current `skills/*/*/SKILL.md` files as authoritative current guidance. - Do not route from historical implementation notes, old changelog entries, or `docs/superpowers/` plans. - Use `ixf-docs-reader` for authorized document, wiki, docx, cloud-doc, direct sheets link, embedded sheet, mindnote, image artifact, or local Markdown reading. - Use `ixf-docs-writer` for approved Markdown publishing as a new docx document or existing-docx update. - Use `ixf-okr-reader` for authorized OKR reading, summary, ownership, mention, or alignment analysis. - Use `ixf-okr-writer` for approved Objective and Key Result creation or modification. - Use `ixf-messenger-reader` for authorized i讯飞 Messenger readiness checks and read-only message inspection workflows. - Use `ixf-messenger-writer` for approved Messenger sends after dry-run planning and explicit apply confirmation. ## Decision Rules 1. Classify the request as docs, OKR, or messenger. 2. Classify