osworld-status_skill

Overview

This skill reports the current status of an OSWorld server so you can quickly check environment readiness and runtime details. It returns human-friendly text plus raw metadata including readiness, uptime, step counter, provider, headless flag, and screen configuration. Use it to verify the server is ready before running observations or automated interactions.

How this skill works

The skill queries the configured OSWorld endpoint (OSWORLD_URL or osworld_config.osworld_url) and reads a JSON status payload. It formats a short status message and exposes the full raw metadata as the note output for downstream steps. No input parameters are required and any provided value parameter is ignored.

When to use it

• Before running automated observations or actions to confirm environment readiness
• As a health check in orchestration scripts or CI pipelines
• To log server uptime and step counter for debugging or metrics
• When switching providers or deployment targets to validate configuration
• To detect headless vs. headed mode and screen resolution before UI interactions

Best practices

• Configure OSWORLD_URL or set osworld_config.osworld_url to point to the correct environment
• Run this skill at the start of every workflow and after any environment changes
• Treat the raw metadata as authoritative for automation branching (ready, headless, screen)
• Record the formatted text and metadata into logs for traceability
• Combine with osworld-observe and osworld-execute steps to build robust interaction flows

Example use cases

• Pre-flight check in a test runner to skip actions if the server is not ready
• CI health probe that aborts deployment if uptime or provider mismatches expected values
• Automation flow that adapts clicks based on reported screen width/height
• Debugging session that records step_counter to correlate actions with server state
• Monitoring script that polls status and triggers alerts on unexpected provider or headless changes