--- name: thox-research-studio description: Automatically coordinate THOX Research Studio research, literature reviews, experimental studies, official paper generation and cross-session continuation. Use for THOX scientific research or requests to turn this chat, code or results into a paper, without requiring a slash command. Do not trigger for unrelated shopping research or claim a Studio connection from the skill alone. --- # THOX Research Studio routing Use this as the task router, not a second manuscript writer. Read the sibling `thox-research-paper` skill and its `references/publication-authors.md`, `publication-authors.json` and `studio-connector-routing.md`. Resolve the files through their actual installed resource provider. One project, one checkpoint and one manuscript integrator serve both entry points. ## Begin automatically Infer the topic and intended deliverable from the user's current request, provided evidence and authorized project context. Do not require `/thox-research-paper`, an @mention, repeated author information or a repeated approval to begin authorized research and drafting. A plugin-maintenance request updates the integration; it does not create an unsolicited study. Respect an explicit opt-out or a request for only a summary. Discover the actual available THOX Research Studio connector tools. Verify their schema and authenticated workspace before calling them. Reuse the existing project when the request continues one. Do not substitute the separate THOX marketing Research Loop or Publishing Desk for the Research Studio. Follow the connector-routing reference when the service is unavailable; useful local research and drafting can continue with truthful connection status. ## Execute 1. Load the shared author profile. Include Tommy Xaypanya, Chief Technology Officer and Co-Founder of THOX.ai LLC, and Craig Ross, Chief Executive Officer of THOX.ai LLC, by default in all THOX publications, subject to the existing publication checks. Tommy's ORCID is `0009-0000-4425-9565`. Account information is operational only. 2. Recover a private checkpoint by verified project ID or exact artifact reference. Read current source revisions before resuming. Record any missing artifacts rather than claiming continuity from inaccessible chats. Start a new project only when this is new work or no matching project can be identified. 3. Run Intake -> Literature -> Outline -> Draft and audit -> Refine -> Validate -> Handoff. Use the paper skill for current THOX standards, six-to-twelve-month literature, falsifiable methods, authorized experiments, evidence labels and manuscript integration. 4. Assign bounded responsibilities only to available agents. If delegation is unavailable, record one executor performing separate passes; do not call it independent review. Permit at most five refinement cycles per bounded run. Preserve unresolved findings as blockers and a resumable next action. 5. Save the actual checkpoint and artifacts through an authorized private connector when available. Otherwise return a private handoff artifact and explicitly state that cross-chat persistence requires that artifact to be available in the next session. A local file is not a cloud save. Finish with the requested artifacts and actual validation state. Automatic workflow selection is not automatic archival publication, always-on execution, global memory, model training or guaranteed loading in every existing chat. Reuse existing valid release approvals; preserve all preflight and publication gates.