How do I install the Gh Readiness skill?

Run npx skillmds@latest add garyld1962/gh-readiness-3 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 Gh Readiness safe to use?

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

Which AI agents work with Gh Readiness?

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 Gh Readiness free to use?

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

Who published Gh Readiness?

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

Gh Readiness by garyld1962 — Agent Skill

Name: Gh Readiness
Author: garyld1962

Gh Readiness

Check GitHub access, target repository and required capabilities before creating issues, PRs, releases or other GitHub changes. Use when access is unknown or changed; avoid repeated probes once this session established the needed capability.

garyld1962 Updated Sep 17, 2026

File contents

GitHub readiness

This is a read-only capability check; do not create a test issue or PR.

Checks

Identify the intended host and owner/repository from the request and local remote configuration. Report a sanitized repository URL, not credentials embedded in a remote. Do not assume github.com when an enterprise host is configured.
Prefer an available GitHub connection. Read the target repository and relevant resource to verify access; inspect callable capabilities and repository permissions for the upcoming operation. Missing CLI is not failure when the connection suffices.
When CLI is required, use command -v gh, gh auth status --hostname , and a read-only API call to the intended repository. Do not use auth token, --show-token, dump environment variables, or start login/refresh as a side effect of this check.
Report the identity/host when available, repository match, read access and write permission evidence. Classic OAuth scopes are only one credential model: a fine-grained or GitHub App token cannot be judged from a missing "repo" scope. A readable repository alone does not prove permission to create a release or PR.
Reuse the successful check during this session unless account, host, repository, operation or an authentication failure changes the evidence.

Result

PASS: the selected path supports the requested operation, with evidence.
PARTIAL: reading works but required write capability or repository selection is unverified; name the uncertainty and the narrow next check.
FAIL: no usable path reaches the intended resource; report the actual failure and recovery step. Do not claim access was restored until a subsequent read succeeds.

Example

"File a bug using our GitHub connection" → check that repository and issue creation capability; do not require installing gh when the connection already supports it.

Closed decisions and open decisions

The target repository/host is a closed decision when specified. Resolve conflicting remotes or missing operation permissions before a write.

Do not

Do not print tokens, request broader access speculatively, mutate authentication, or conflate a missing tool with a missing GitHub capability.

Copilot integration

This skill is the durable entrypoint for Copilot hosts that load agent skills. The matching prompt file is an optional VS Code shortcut. Read repository instructions before edits; use the tools actually exposed by the host, including connected GitHub access when available. A prompt or skill does not itself grant additional permissions.

---name: gh-readiness-3description: Check GitHub access, target repository and required capabilities before creating issues, PRs, releases or other GitHub changes. Use when access is unknown or changed; avoid repeated probes once this session established the needed capability.---# GitHub readinessThis is a read-only capability check; do not create a test issue or PR.## Checks1. Identify the intended host and owner/repository from the request and local remote configuration. Report a sanitized repository URL, not credentials embedded in a remote. Do not assume github.com when an enterprise host is configured.2. Prefer an available GitHub connection. Read the target repository and relevant resource to verify access; inspect callable capabilities and repository permissions for the upcoming operation. Missing CLI is not failure when the connection suffices.3. When CLI is required, use command -v gh, gh auth status --hostname <host>, and a read-only API call to the intended repository. Do not use auth token, --show-token, dump environment variables, or start login/refresh as a side effect of this check.4. Report the identity/host when available, repository match, read access and write permission evidence. Classic OAuth scopes are only one credential model: a fine-grained or GitHub App token cannot be judged from a missing "repo" scope. A readable repository alone does not prove permission to create a release or PR.5. Reuse the successful check during this session unless account, host, repository, operation or an authentication failure changes the evidence.## Result- PASS: the selected path supports the requested operation, with evidence.- PARTIAL: reading works but required write capability or repository selection is unverified; name the uncertainty and the narrow next check.- FAIL: no usable path reaches the intended resource; report the actual failure and recovery step. Do not claim access was restored until a subsequent read succeeds.## Example"File a bug using our GitHub connection" → check that repository and issue creationcapability; do not require installing gh when the connection already supports it.## Closed decisions and open decisionsThe target repository/host is a closed decision when specified. Resolve conflictingremotes or missing operation permissions before a write.## Do notDo not print tokens, request broader access speculatively, mutate authentication,or conflate a missing tool with a missing GitHub capability.## Copilot integrationThis skill is the durable entrypoint for Copilot hosts that load agent skills.The matching prompt file is an optional VS Code shortcut. Read repository instructionsbefore edits; use the tools actually exposed by the host, including connected GitHubaccess when available. A prompt or skill does not itself grant additional permissions.

Frequently asked questions