القائمة
Use when CTOX handles a Business OS Support conversation and must summarize, classify, draft, or propose the next support action through typed Business OS writeback.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Create, edit, redline, review, and comment on .docx documents through the CTOX documents engine (Euro-Office port), with a strict render-and-verify workflow. Authoring and layout changes run as editor flows; deterministic OOXML batch operations run as native office-engine ops. Never assume a document is correct without rendering and visually inspecting every page.
Authorized deployment readiness and go-live security audit for software projects and running apps. Use as the final app go-live gate to assess release readiness, validate evidence, run scanner coverage, verify authorization boundaries, prove release blockers, and produce a deployment audit report. Provides one Rust CLI boundary for Pi/CTOX agents running in a sandbox.
Create, edit, analyze, and verify .xlsx workbooks through the CTOX spreadsheets engine (Euro-Office port). Formula-driven, auditable models with typed values, invariant number formats, and a mandatory visual verification pass. Authoring capabilities are gated on the engine's feature matrix; read/render/analyze paths are available first.
Use when tasks involve reading, reviewing, or verifying PDF files where rendering and layout matter. Prefer visual checks by rendering pages to PNGs (Poppler, same path as the CTOX report pipeline). PDF creation routes through the CTOX documents engine, not ad-hoc PDF generator libraries.
Use whenever CTOX, Business OS, App Creator, App Store, chat, CLI, or an inbound Business OS workflow asks an agent to build, modify, repair, review, or install a CTOX Business OS app/module. The agent builds the app itself as no-build vanilla HTML/CSS/browser ESM, persists through the shell-provided CTOX Sync Engine/RxDB handle, sends automation through commandBus, studies shipped Business OS app examples, and validates the result with CTOX app validation.
Use when an external agent should connect to CTOX Business OS through the Business OS MCP Channel to query modules, records, runs, artifacts, approvals, or delegate validated Business OS actions. Trigger when setting up or using CTOX from ChatGPT, Codex, another MCP-capable agent, or an agent runtime that can install GitHub-hosted skills.
| name | business-os-support-workflow |
| description | Use when CTOX handles a Business OS Support conversation and must summarize, classify, draft, or propose the next support action through typed Business OS writeback. |
Use this skill for CTOX work launched from the Business OS Support app.
Support work is durable Business OS work. Do not treat the prompt as a private chatbot request and do not send external replies directly.
Read the supplied record_snapshot, then produce any structured Support result
through the advertised writeback_contract:
support.agent.writeback
If a Business OS MCP Channel is available, use business_os.list_module_actions
for module support, then propose or execute support.agent.writeback only
within the server's policy. If MCP is not available, write the structured
result in the final response so CTOX can capture it through the normal Harness
review path.
Allowed suggestion_kind values:
summarydraft_replyclassificationnext_actioncustomer_updateticket_actionEvery writeback must include:
conversation_idsource_command_idtask_id when knownsuggestion_kindsummarypayloadconfidencerequired_human_actionUse required_human_action: "human_send_required" for reply drafts. Reply
drafts are never external sends.
Do not:
Prefer a small suggestion with clear evidence over a broad unsupported action.