skills.rest
Ryokuman
RyokumanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

shared-runtime-health-check

Validates project runtime sets and shared server health before lifecycle execution.

1|Updated Jul 3, 2026
Search Tags:#devops#e2e testing#server validation#runtime set#lifecycle gate#task silo#runtime health check
One-click install
npx skills add https://github.com/Ryokuman/new_human_ochestrator --skill shared-runtime-health-check-ryokuman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: shared-runtime-health-check
Source: https://github.com/Ryokuman/new_human_ochestrator/tree/main/system/20-skills/shared-runtime-health-check
Command: npx skills add https://github.com/Ryokuman/new_human_ochestrator --skill shared-runtime-health-check-ryokuman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often start page-lifecycle, run, or E2E verification without confirming that the project's runtime set exists and that shared server runtimes are actually healthy, causing wasted runs and confusing failures. This Skill gates execution by checking runtime_set definitions and server health first. ## Core Features & Use Cases - Runtime Set Resolution: Resolves the correct runtime_set using a defined priority order (run_set, task, qa_or_runbook, project common) and stops execution when none is defined. - Server Runtime Detection: Identifies server-type runtimes via runtime_kind, ports, or health check commands and skips non-server runtimes with a recorded reason. - Health Gate Reporting: Produces standardized pass/fail summaries for goal.md, handoffs, and PR bodies without ever reading or recording secret values. - Use Case: Before running an E2E suite for a task silo, confirm the project's frontend dev server and backend API runtime respond on their registered ports, then record the health summary in the PR body. ## Quick Start Check whether my project's runtime set is defined and verify the health of its shared server runtimes before I start the page-lifecycle run.

Frequently Asked Questions about shared-runtime-health-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check shared runtime health before running E2E tests?▼

Resolve the project's runtime_set using the priority order run_set, task, qa_or_runbook, then project common. For each server-type runtime, run its registered health command or URL and record the pass/fail summary before starting E2E.

What is a runtime_set and how is it resolved?▼

A runtime_set defines the runtimes a project needs, including workspace path, branch, commit, port, and env policy. It is resolved in priority order: run_set.required_runtime_set, task.runtime_set, qa_or_runbook.runtime_set, then project.common_runtime_set.

When can the runtime health check be skipped?▼

The health check can be skipped when the runtime_set contains no server-type runtimes, such as source checkouts or static reference repos. The skip reason must still be recorded in goal.md or the execution report.

What happens if a runtime health check fails?▼

Lifecycle, run, and E2E execution are stopped immediately. The failure report includes the failed runtime, the command or URL checked, the reason, and a next action such as defining the runtime_set or starting the server.

Does the health check read env files or secrets?▼

No. It only records env file paths, injection policies, or secret provider names. Secret values, tokens, and credentials are never read or written.

Related Skills

Explore More Software Engineering Skills→
fallguyconsultingfallguyconsulting
1

open

Creates an isolated git worktree workspace with its own branch and namespaced runtime for one job.

Official
Intermediate
bybren-llcbybren-llc
395

orchestration-patterns

Orchestrate long-running multi-step tasks across subagents with evidence checkpoints.

Official
Advanced
mDevsLabsmDevsLabs
1

builtin-tool

Create and wire LobeHub builtin tool packages with manifests, runtimes, and executors.

Community
Advanced
Rational-PartnersRational-Partners
4

local-debugging

Inspect logs and verify processes to diagnose local development errors.

Official
Intermediate