grtninja/meta-harness-app-order-bootstrap
skill-candidates/meta-harness-app-order-bootstrap/SKILL.md
Orchestrate app-first, registry-aware bring-up and health validation for local multi-app meta-harness stacks. Use when startup order, runtime registry, launcher scripts, control-center bring-up, or cross-app health checks change together.
$ install --global
skillsauthnpx skillsauth add grtninja/skill-arbiter meta-harness-app-order-bootstrapInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 22, 2026, 8:21 PM54.9s2 files scanned
SKILL.md
- name:
- meta-harness-app-order-bootstrap
- description:
- Orchestrate app-first, registry-aware bring-up and health validation for local multi-app meta-harness stacks. Use when startup order, runtime registry, launcher scripts, control-center bring-up, or cross-app health checks change together.
Meta-Harness App-Order Bootstrap
Use this skill when recent work spans startup scripts, runtime registries, app-order sequencing, and cross-app health validation under the local meta-harness.
Trigger Conditions
Use this skill when all are true:
- Two or more local apps/services must launch or attach in a required order.
- The work touches launcher scripts, runtime registry state, or desktop bring-up flows.
- Validation depends on real endpoint health, not just process start.
Route elsewhere when:
- the task is only about desktop window polish or shortcut ownership: use
$desktop-startup-acceptance - the task is only about one repo's internal routing contract: use the most specific repo skill
- the task is only about model-lane authority drift: use
$shim-pc-control-brain-routing
Workflow
- Capture the intended app order and ownership:
- app-first entry surface
- attach/start sequence
- runtime registry updates
- health and readiness gates
- Read the active launcher and registry surfaces before editing.
- Confirm the authoritative local model lanes:
http://127.0.0.1:9000/v1http://127.0.0.1:2337/v1- treat
http://127.0.0.1:1234/v1only as a non-authoritative operator surface
- Patch sequencing, registry, or health contracts without introducing alternate public endpoints.
- Validate the real bring-up flow in order:
- launcher starts cleanly
- dependent app attach succeeds
- runtime registry reflects the active state
- health endpoints stay green
- Report the exact app-order contract and remaining degraded lanes.
Required Evidence
- launcher files touched
- runtime registry files or templates touched
- health endpoints checked with status results
- any startup-order dependency that remains manual or operator-confirmed
Guardrails
- Do not invent new public ports to work around sequencing bugs.
- Keep launch ownership explicit; one surface owns startup, dependent surfaces attach.
- Prefer shell-free public launch surfaces when desktop startup is involved.
- Fail closed when the registry says one thing and the live health surface says another.
Scope Boundary
Use this skill for meta-harness bring-up sequencing, registry-aware startup contracts, and cross-app readiness validation.
Do not use this skill for unrelated packaging, UI styling, or long-running host offload work.
References
$desktop-startup-acceptance$shim-pc-control-brain-routing$heterogeneous-stack-validation
Related Skills
grtninja/white-hat
tools
VerifiedTrustedCommunity
Run a defender-first security sweep on code, configs, prompts, model/tooling surfaces, or third-party contribution lanes. Use when a request involves safe bug, leak, zero-day-class, exploit, or hack hunting for protection, when contributing to outside repositories and you want a focused security pass, or when touching auth, secrets, permissions, network exposure, prompt/tool boundaries, data flow, or update/build surfaces. This skill is defensive only and must never be used for weaponization or unauthorized access.
2SKILL.mdUpdated Apr 22, 2026
grtninja/vrm-sandbox-startup-acceptance
development
VerifiedTrustedCommunity
Validate and repair VRM Sandbox startup acceptance with shim-first local model authority, frontend/backend bring-up, and avatar-runtime launch proof. Use when launch behavior, chat handoff, voice fallback, or runtime bridge acceptance must be verified end to end.
2SKILL.mdUpdated Apr 22, 2026
grtninja/voice-catalog-runtime-alignment
documentation
VerifiedTrustedCommunity
Align documented voice-command catalogs, endpoint action allowances, and live runtime handlers so operator-visible voice surfaces match what the stack can actually execute. Use when voice command docs, parser matrices, endpoint permissions, or runtime action routing drift apart.
2SKILL.mdUpdated Apr 22, 2026
grtninja/skillhub-trend-radar
development
VerifiedTrustedCommunity
Track SkillHub trend and topic drift, maintain a bounded rewrite watchlist, and surface emerging gaps worth turning into repo-owned skills. Use when the marketplace query set shows new families or when the current shortlist has gone stale.
2SKILL.mdUpdated Apr 22, 2026