Github issue

Skill yuelenghan/orbit/skills/github-issue

Use when the user needs GitHub issue and milestone-backed tracker operations through the packaged launcher and local CLI runtime.From its SKILL.md

Install

npx -y skills add yuelenghan/orbit --skill github-issue

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

One thing to look at

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.

SKILL.md

1.9 KB, 360 tokens by cl100k_base, as published. Nobody here has run it

GitHub Issue Skill

Use this skill to operate GitHub Issues and milestone-backed planning data through the packaged launcher and local CLI runtime.

Within Orbit's shared provider framework, this skill is one implementation of the tracker capability.

Runtime and execution

Always run the packaged launcher through ${GITHUB_ISSUE_SKILL_DIR} so it works from the user's current working directory:

macOS/Linux: ${GITHUB_ISSUE_SKILL_DIR}/bin/github-issue
Windows: ${GITHUB_ISSUE_SKILL_DIR}\bin\github-issue.cmd

${GITHUB_ISSUE_SKILL_DIR} is a documentation placeholder, not a guaranteed shell environment variable. Resolve BIN to a real launcher path once before the first CLI call. Do not call node app/dist/cli.js directly.

Scope and boundaries

GitHub Issues and milestones only.
CLI-mediated operations only.
Do not call GitHub REST endpoints directly from skill content.
Sprint semantics map to milestones so scenarios can keep using the shared tracker.sprint.* contract.

Capability Domain

Domain:

tracker

Provides:

tracker.config.get
tracker.config.set
tracker.issue.get
tracker.issue.search
tracker.issue.create
tracker.issue.update
tracker.issue.assign
tracker.sprint.get
tracker.sprint.issues
provider-specific workflow helpers

Config check:

github-issue config get

Config check

Run github-issue config get when configuration state is unknown or before the first provider-scoped task in a new session.

Supporting files

Read references/commands.md for the packaged command surface.
Read references/usage.md for execution policy and read/write behavior.

What ships with it: 9 files

3.7 KB alongside SKILL.md, 2 of them executable

Gives 0 of the 12 instructions most bug reports skills give in 360 tokens

Counted across 130 of the 155 authors here whose files we hold, read 2026-09-06

Reproduce the bug as a new failing regression test firstin 11 of 130, across 4 files
Add security-reviewer for security-sensitive defectsin 10 of 130, across 3 files
Skip the research phase by defaultin 10 of 130, across 3 files
Escalate build breaks to build-error-resolverin 10 of 130, across 3 files
Stop at Gate 1 and Gate 2in 10 of 130, across 3 files
Fix until that test goes greenin 10 of 130, across 3 files
Run the orch-pipeline engine with the settings abovein 10 of 130, across 3 files
Scope unclear root causes with code-explorer before writing the red testin 10 of 130, across 3 files
Replace sensitive data with placeholdersin 6 of 130, across 3 files
Match severity rating to actual impactin 6 of 130, across 3 files
Reference screenshots and attachments inlinein 6 of 130, across 3 files
Create issues as markdown filesin 5 of 130, across 2 files

Said here and by no other author read

Always run the packaged launcher through the skill directory
Resolve the launcher path once before the first CLI call
Run github-issue config get when configuration state is unknown
Run the config check before the first provider-scoped task each session
Read references/commands.md for the command surface
Read references/usage.md for execution policy

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.