How do I install the Github Ops Tree Router skill?

Run npx skillmds@latest add chf3198/github-ops-tree-router in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Github Ops Tree Router safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Github Ops Tree Router?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Github Ops Tree Router free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Github Ops Tree Router?

chf3198 (@chf3198) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Github Ops Tree Router by chf3198 — Agent Skill

Name: Github Ops Tree Router
Rating: 4.2 (5 reviews)
Author: chf3198

File contents

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

Owner Matrix
Invocation Map
Output Contracts
Phase 3 De-overlap Migration

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>

---name: github-ops-tree-routerdescription: Route GitHub workflow requests through a capability-first GitHub skill tree with explicit ownership boundaries and minimal overlap.--- # 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 - [Owner Matrix](references/OWNER-MATRIX.md) - [Invocation Map](references/INVOCATION-MAP.md) - [Output Contracts](references/OUTPUT-CONTRACTS.md) - [Phase 3 De-overlap Migration](references/PHASE-3-DEOVERLAP-MIGRATION.md) ## Output format ```text 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> ```

Frequently asked questions

Github Ops Tree Router