Results for “run-order”

Use when a researcher asks where to start, which project skill fits the current stage of a study, or in what order literature scoping, source access, vault upkeep, drafting, citation verification, disclosure, and review response should run.

Run a full pipeline for a task. Orchestrates roles through stages (standalone or HOTL-integrated).

Provides a sandboxed execution environment for running code, scripts, and automated workflows with resource capping and network isolation.

Provides a sandboxed execution environment for running code snippets, automating tasks, and deploying logic across multiple languages with resource capping and network isolation.

Orchestrates a strict four-stage shipping pipeline: session critique, validation, commit, and pull request, halting on failure. Supports a critique-only mode for mid-session quality checks.

Execute the full AgentHub competition lifecycle in a single command: initialize, capture baseline, spawn agents, evaluate results, and merge the winner.

Turn raw MATLAB code into a published .mltbx toolbox — full pipeline from scope definition through packaging and release. Drives 8 phases with human checkpoints, enforcing ordering and dependencies. Use when asked to package, create a toolbox, or run the files-to-package pipeline.

Orchestrate the complete post-first-draft polishing pipeline for an academic LaTeX paper by invoking five existing skills in fixed order: (1) paper-polish, (2) paper-self-revise, (3) paper-style, (4) paper-polish again, (5) reference-verify. Trigger when user says "paper pipeline" / "paper-pipeline" / "论文流水线" / "全流程打磨" / "一条龙打磨" / "初稿打磨" / "full polish pipeline" / "run the whole pipeline", or wants the entire post-draft polishing sequence run on a paper folder. Use this skill whenever the user asks for several paper-finishing steps (polish + revise + style + reference check) on one manuscript in one go, even if they don't name every individual skill.