GitHub `yeet` skill incorrectly requires `gh` despite connector-first workflow

What issue are you seeing?

The GitHub plugin's yeet skill describes a connector-first workflow, but its prerequisites unconditionally require GitHub CLI (gh) and stop if it is unavailable.

Source:

https://github.com/openai/plugins/blob/main/plugins/github/skills/yeet/SKILL.md

The skill says:

• Prefer the GitHub app for pull request creation.
• Use gh only as a fallback when connector coverage is insufficient.

But the Prerequisites section then says:

• Require gh and run gh --version.
• Stop and ask the user to install it if it is missing.
• Require an authenticated gh session before continuing.

These instructions contradict each other. In a ChatGPT-login Codex session where the GitHub connector is available and exposes pull-request creation, the skill still stops immediately when gh is not installed. The connector path is never attempted.

What steps can reproduce the bug?

1. Use a Codex environment with the GitHub plugin and an authenticated GitHub connector.
2. Ensure the connector can create pull requests.
3. Use a local Git repository where ordinary git is available, but GitHub CLI gh is not installed.
4. Ask Codex to commit, push, and open a draft pull request.
5. The yeet skill runs gh --version, receives command not found, asks the user to install gh, and stops.

What is the expected behavior?

The skill should:

1. Use local git for branch creation, staging, commit, and push.
2. Use the GitHub connector by default to create the pull request.
3. Check for gh only if connector coverage is actually insufficient.
4. Treat missing or unauthenticated gh as a blocker only for that fallback path.

Suggested change

Replace the unconditional CLI prerequisites with connector-first prerequisites, for example:

## Prerequisites

- Require a local Git repository and a clear understanding of which changes belong in the pull request.
- Use the GitHub connector by default for pull request creation.
- Do not require or check GitHub CLI (`gh`) when the connector can inspect the repository and create the pull request.
- Check `gh --version` and `gh auth status` only when connector coverage is insufficient and the CLI fallback is required.
- Missing or unauthenticated `gh` blocks only the fallback path.

This would make the prerequisites consistent with the skill description and the connector-first workflow already documented in the same file.

Additional information

Observed with the curated GitHub plugin skill cached as version 0.1.8-2841cf9749ae. The same contradictory prerequisites are present in the current public main version of the source file.