Github workflow

Skill yuelenghan/orbit/skills/github-workflow

Use when the user needs GitHub Actions workflow, run, log, queue, or configuration operations through the packaged launcher and local CLI runtime.From its SKILL.md

Install

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

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.8 KB, 354 tokens by cl100k_base, as published. Nobody here has run it

GitHub Workflow Skill

Use this skill to operate GitHub Actions workflows and workflow runs through the packaged launcher and local CLI runtime.

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

Runtime and execution

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

macOS/Linux: ${GITHUB_WORKFLOW_SKILL_DIR}/bin/github-workflow
Windows: ${GITHUB_WORKFLOW_SKILL_DIR}\bin\github-workflow.cmd

${GITHUB_WORKFLOW_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 Actions workflows and workflow runs only.
CLI-mediated operations only.
Do not call GitHub REST endpoints directly from skill content.
Workflow runs map to the shared ci.job.*, ci.build.*, and ci.queue.* contract.

Capability Domain

Domain:

ci

Provides:

ci.config.get
ci.config.set
ci.job.get
ci.job.trigger
ci.build.get
ci.build.console
ci.queue.get
provider-specific workflow helpers

Config check:

github-workflow config get

Config check

Run github-workflow 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.4 KB alongside SKILL.md, 2 of them executable

Gives 0 of the 12 instructions most automation workflows skills give in 354 tokens

Counted across 745 of the 1,008 authors here whose files we hold, read 2026-08-07

Write conventional commit messagesin 36 of 745, across 35 files
Delete branches after mergein 30 of 745, across 21 files
Make atomic commitsin 25 of 745, across 15 files
Write minimal code to pass testsin 22 of 745, across 10 files
Re-snapshot after navigation or DOM changesin 21 of 745, across 13 files
Use try-catch for error handlingin 20 of 745, across 8 files
Run tests before committingin 20 of 745, across 12 files
Write tests before implementationin 20 of 745, across 8 files
Configure branch protection rulesin 19 of 745, across 5 files
Explain the why in commit messagesin 19 of 745, across 9 files
Refactor code while tests remain greenin 19 of 745, across 6 files
Interact with elements using refsin 19 of 745, across 11 files

Said here and by no other author read

operate GitHub Actions workflows and workflow runs
run the packaged launcher binary
resolve the launcher path before the first CLI call
read the usage reference file
map workflow runs to the shared CI contract
run config get when configuration state is unknown

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.