agentsclimarketplace

Github ops tree router

Skill chf3198/megingjord-harness/skills/github-ops-tree-router

AI agent governance harness: baton workflow, fleet LLM routing (Ollama/Claude/OpenRouter), and CI gates for Copilot, Claude Code, and Codex.

Install
npx -y skills add chf3198/megingjord-harness --skill github-ops-tree-router

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Route GitHub workflow requests through a capability-first GitHub skill tree with explicit ownership boundaries and minimal overlap.

SKILL.md

2.8 KB, as published. Nobody here has run it

GitHub Ops Tree Router

Purpose

Select the correct specialized GitHub operations path with minimal overlap and valid feature support.

Capability-first protocol

For goals involving rulesets, merge queue, Actions security, or plan-sensitive controls, run github-capability-resolver first.

If capability status is not-supported or evidence is incomplete, return NO_CHANGE.

Ownership model

  • Primary router owner: github-ops-tree-router
  • Policy catalog owner: github-ops-excellence
  • Delegates:
    • github-capability-resolver
    • github-ticket-lifecycle-orchestrator
    • github-projects-agile-linkage
    • github-review-merge-admin
    • github-release-incident-flow
    • github-ruleset-architecture
    • github-actions-security-hardening
    • repo-profile-governance
    • workflow-self-anneal

Routing table

  • goal=ticket-lifecycle -> github-ticket-lifecycle-orchestrator (+ github-ops-excellence for policy profile)
  • goal=agile-projects -> github-projects-agile-linkage
  • goal=review-merge -> github-capability-resolver + github-review-merge-admin
  • goal=release-incident -> github-release-incident-flow (+ github-ops-excellence for policy profile)
  • goal=repo-governance -> repo-profile-governance
  • goal=actions-security -> github-capability-resolver + github-actions-security-hardening
  • goal=ruleset-architecture -> github-capability-resolver + github-ruleset-architecture
  • goal=process-hardening -> workflow-self-anneal

Required references

Output format

GITHUB_OPS_ROUTER_REPORT
goal: <ticket-lifecycle|agile-projects|review-merge|release-incident|repo-governance|actions-security|ruleset-architecture|process-hardening>
policy_profile: <strict|standard|light>
capability_resolution:
- required: <yes|no>
- status: <available-now|available-with-config-change|available-with-plan-upgrade|not-supported|not-run>
selected_skill_path:
- <ordered skills>
ownership:
- router: github-ops-tree-router
- policy_catalog: github-ops-excellence
- delegates: <skills>
checks:
- <required verifications>
decision:
- <apply|defer|NO_CHANGE>
missing_evidence:
- <none or artifacts>

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.