USO

##Functional characteristics - Unified script library: Centrally register Python, Shell, and JavaScript scripts, and save descriptions, parameter definitions, versions, and tags. It is suitable for unifying scattered operation and maintenance scripts and data processing scripts. - Real-time execution and log playback: Support manual execution of scripts, and view stdout/stderr in real time within the page through WebSocket to facilitate quick diagnosis of the execution process. - Workflow chain orchestration: Multiple scripts can be organized into workflows with node configurations and edges for multi-step automated tasks such as serial export, processing, verification, and reporting. - Timing task scheduling: Built-in APScheduler, which can schedule scripts according to three trigger methods: interval, cron, and date. It is suitable for periodic inspections and scheduled reports. - Indicators and operation history: Provide statistical information such as scripts, workflows, scheduling, success rate, and time consumption to facilitate continuous observation of platform operation. - Confidential parameter injection: Enter the parameter marked as secret in the form of a password box and inject it as an environment variable into the target script during execution; the instance master key `USO_MASTER_KEY` is automatically injected by the lazy cat `stable_secret`. - Dependency graph and relationship visualization: The built-in graph page displays the relationship between scripts and workflows, which is suitable for sorting out multi-step automation links. ###Daily usage 1. Maintain script inventory on the Scripts page. The current interface supports filling in the name, runtime, description, content and tags for scripts, and executing them directly on the details page. 2. After the script is executed, first check the output, exit code, execution time and history in the 'Execute','History','Logs', and 'Metrics' tabs on the script details page. 3. Create a DAG on the Workflows page, add script nodes to the workflow, and then trigger the entire link through Execute Chain. 4. View the current script diagram on the Graph page. When there is no current connection,`No connections yet` will be displayed on the right side. 5. Create a Cron, Interval or Date schedule for a single script on the Schedules page, and you can directly 'Pause '/'Resume'. 6. View instance-level operation statistics on the Metrics page, such as total execution times, successes, failures, and recent runs list. 7. Maintain five sets of configurations, General, Logging, Execution, Persistence, and Scheduler on the Config page. 8. On the Modules page, check the directory of available modules for the three types of runtimes: Python, Shell, and JavaScript. 9. If other Agents in the platform need to call USO, they can read the MCP Provider exported by this application and discover tools such as list_scripts, get_script, run_script, get_run and other tools through `/mcp/`; this is a platform side integrated verification.