github-capability-resolver

Map GitHub controls to plan, visibility, and account settings.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/chf3198/devenv-ops --skill github-capability-resolver
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-capability-resolver
Source: https://github.com/chf3198/devenv-ops/tree/main/skills/github-capability-resolver
Command: npx skills add https://github.com/chf3198/devenv-ops --skill github-capability-resolver

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Resolve GitHub feature availability and policy constraints by mapping requested controls to actual plan, visibility, and account settings, preventing guidance that is not supported.

Core Features & Use Cases

  • Determine support status by plan, visibility, and owner type.
  • Check whether features are enabled in repository or organization settings.
  • Recommend actions: available-now, available-with-config-change, available-with-plan-upgrade, or not-supported, with safe fallbacks for unsupported cases.
  • Provide a clear, structured decision for governance conversations about rulesets, merge queues, security features, or org-wide controls.

Quick Start

Provide scope (repo|org|enterprise), visibility (public|private|internal), plan (free|pro|team|enterprise), and surface (rulesets|merge-queue|security|projects) to get a capability recommendation.

Frequently Asked Questions about github-capability-resolver

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

FAQPage Schema
How do I check if GitHub rulesets and merge queues are available for my repository plan?

To check GitHub rulesets and merge queue availability, evaluate your repository's plan tier, visibility, and owner type against the requested controls. This capability resolution prevents applying governance policies to unsupported configurations by returning a structured status.

What GitHub features are restricted by organization visibility and account settings?

GitHub features are restricted by organization visibility and account settings based on plan tier and owner type. Mapping requested controls to these account settings prevents invalid guidance when configuring org-wide security features or governance controls.

Does GitHub security feature availability depend on whether a repository is public or private?

GitHub security feature availability depends on repository visibility, plan tier, and owner type. Evaluating these account settings determines whether security capabilities are available-now, require configuration changes, or need a plan upgrade.

How do I resolve unsupported GitHub governance controls and find safe fallbacks?

Resolve unsupported GitHub governance controls by mapping requested features to actual plan and visibility settings, which returns a not-supported status with safe fallback recommendations. This prevents invalid guidance when applying org-wide controls across restricted plan tiers.

When should I upgrade my GitHub plan to enable org-wide controls and rulesets?

Upgrade your GitHub plan to enable org-wide controls and rulesets when capability resolution returns an available-with-plan-upgrade status. This indicates the requested governance features are not supported on your current free or pro tier.