Open WorkBuddy SkillHub
Go to Experts, Skills & Connectors, choose Skills, then open SkillHub.
Collect live status across four AI delivery dependencies with Lexmount WebFetch, verify key pages in a cloud browser, and return an auditable GO, CAUTION, HOLD, or UNKNOWN decision.
Before your first run, search for and install the required Skills inside the WorkBuddy app.
Go to Experts, Skills & Connectors, choose Skills, then open SkillHub.
Enter lexmount in the search field and confirm that both Lexmount Skills appear.
Click + on both cards. After the installed confirmation appears, verify that both Skills are enabled.
Skills load immediately after installation, so a restart is usually unnecessary. On first use, each Skill may download its Rust CLI and open a browser for Lexmount OAuth. Never paste an API key into the conversation. If the prompt returns SKILL_REQUIRED, confirm that both Skills are installed and enabled.
Mandatory prerequisite: Use the installed and enabled WorkBuddy Skills lexmount-webfetch and lexmount-browser. If either Skill is unavailable, stop with SKILL_REQUIRED, name the missing Skill, and tell the user to complete the WorkBuddy setup for this template. Follow each Skill's bundled instructions, run its doctor check, and authenticate only when required. Continue only when both Skills are ready.
Task: Create an evidence-backed release-readiness brief using these official public status pages:
- OpenAI: https://status.openai.com/
- GitHub: https://www.githubstatus.com/
- npm: https://status.npmjs.org/
- Cloudflare: https://www.cloudflarestatus.com/
Check each provider's overall status, release-critical components, active incidents, maintenance, and any material incident resolved within the previous 24 hours.
Flow:
1. Create artifacts/workbuddy-release-readiness in the working directory. If it already exists, append a UTC timestamp instead of overwriting it.
2. Use lexmount-webfetch first for all four URLs.
3. Record each provider's requested URL, final URL, access time, overall status, relevant component status, incidents, maintenance, and warnings in facts.json.
4. Use lexmount-browser only when WebFetch returns missing, conflicting, or non-operational information, or when capturing the required visual evidence.
5. Open the Cloudflare status page with lexmount-browser and save at least one screenshot in evidence/.
6. Apply these decision rules:
- HOLD: a release-critical component has a major outage or is unavailable.
- CAUTION: an active incident, degraded service, partial outage, relevant maintenance, or material incident resolved within the previous 24 hours could affect a release.
- GO: all four providers explicitly report normal operation for relevant components.
- UNKNOWN: required evidence is missing, contradictory, or insufficient.
7. Write brief.md, facts.json, and run-summary.json.
8. Close every temporary Browser Session created by this task.
Execution: Keep all browser activity read-only. Do not subscribe to updates, sign in, enter contact information, change settings, or submit forms. Never infer normal operation from an HTTP success response or missing status text. Every material conclusion in brief.md must reference a source_id from facts.json.
Acceptance: Every input URL must have an explicit result. All required files must exist and be non-empty, both JSON files must parse successfully, every material conclusion must have a source and access time, every declared screenshot must exist, and all temporary Browser Sessions must be closed.
Return SUCCESS only when all sources and cleanup succeed, PARTIAL_SUCCESS when any source or cleanup step fails, and FAILURE when fewer than two sources succeed. release_readiness must be UNKNOWN whenever required evidence is insufficient.
Cleanup: On success, failure, timeout, or cancellation, close only temporary Sessions created by this task. Do not close WorkBuddy, pre-existing Sessions, or persistent Contexts. Retain all generated evidence.
Return: Report only the status, release_readiness, successful and failed source counts, brief path, facts path, evidence path, run summary path, screenshot count, cleanup result, and sanitized error summary. Do not expose API keys, Project IDs, Session IDs, connection URLs, OAuth details, or credentials.