openskills-dev-orchestrator
Route OpenSkills development tasks to the right project skill or subagent, including sequencing rules for debugging, feature work, regression checks, and release readiness.
git clone --depth 1 https://github.com/Geeksfino/openskills /tmp/openskills-dev-orchestrator && cp -r /tmp/openskills-dev-orchestrator/.cursor/skills/openskills-dev-orchestrator ~/.claude/skills/openskills-dev-orchestratorSKILL.md
# OpenSkills Dev Orchestrator Use this skill to decide which OpenSkills project skill or subagent to invoke first, and in what order, for the fastest safe outcome. ## Routing Rules ### 1) Runtime failures or sandbox regressions 1. Start with `openskills-runtime-debug`. 2. If issue spans multiple execution paths or platforms, use `runtime-sandbox-auditor` subagent. 3. Re-run runtime tests before concluding. ### 2) Plugin/build feature changes 1. Start with `openskills-plugin-separation`. 2. If dependency topology is unclear, use `wasm-plugin-build-specialist` subagent. 3. Validate runtime default-feature behavior and binding impact. ### 3) Binding breakages (TS/Python) 1. Start with `openskills-bindings-maintainer`. 2. If both bindings are affected or unclear, use `bindings-compatibility-agent` subagent. 3. Return a compatibility matrix and migration notes if needed. ### 4) Skill package authoring or updates 1. Start with `openskills-skill-authoring`. 2. Use `skill-spec-conformance-agent` subagent when multiple skills or ambiguous triggers are involved. 3. Validate discovery and activation behavior. ### 5) End-to-end confidence checks 1. Start with `openskills-e2e-test-runbook`. 2. Use `examples-e2e-agent` subagent for scenario-heavy or flaky behavior investigations. 3. Capture scenario-by-scenario pass/fail and tool-call evidence. ### 6) Release preparation 1. Start with `openskills-release-ops`. 2. Use `release-gatekeeper-agent` subagent for final GO/NO-GO judgment. 3. Output blockers, risks, and rollback notes explicitly. ## Escalation Heuristics - Use a skill first when the workflow is deterministic and repeatable. - Escalate to a subagent when the task needs deep cross-file reasoning, ambiguity handling, or parallel analysis. - If a task is unresolved after one full skill pass, escalate to the corresponding subagent. ## Output Contract Always return: 1. Selected path (skill and/or subagent) 2. Why this path was chosen 3. Ordered execution plan 4. Success criteria
Maintain compatibility between openskills-runtime and language bindings (TypeScript, Python), including feature flags, build configuration, and smoke verification.
Run deterministic OpenSkills end-to-end validation across runtime tests and example agents, then report tool calls, activation behavior, and regressions.
Enforce clean separation between core openskills-runtime and optional WASM build plugins so plugin compilation does not break runtime consumers or language bindings.
Prepare and validate OpenSkills release readiness across runtime, bindings, examples, and regression gates with a deterministic checklist and go/no-go outcome.
Diagnose openskills-runtime execution failures in sandboxed paths (Landlock, seatbelt, native script execution, wasm execution) and produce root-cause-first findings with minimal-risk remediation steps.
Create and refine OpenSkills-compatible skills (SKILL.md + optional resources) with strong metadata, clear activation triggers, and reliable execution guidance.
Reviews code for quality, best practices, and potential issues. Use when asked to review, audit, or check code for problems.
Explains code clearly and thoroughly. Use when asked to explain, clarify, or teach about code snippets, functions, or concepts.