Nushell
ccusage/ccusage
Guides ccusage Nushell scripts. An agent skill from ccusage/ccusage.
OpenTeams skill for manually starting a GitHub Actions workflow, watching its execution, diagnosing failures, rerunning transient failed jobs, repairing code or configuration errors, and dispatching…
Install GitHub Actions Run And Fix
$ npx skills add openteams-lab/openteams --skill github-actions-run-and-fix -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install openteams-lab/openteams github-actions-run-and-fix --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/openteams-lab/openteams.git skills-src && mkdir -p .claude/skills && cp -r skills-src/assets/skills/github-actions-run-and-fix .claude/skills/github-actions-run-and-fix && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "github-actions-run-and-fix" agent skill from https://github.com/openteams-lab/openteams/tree/main/assets/skills/github-actions-run-and-fix into .claude/skills/github-actions-run-and-fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-actions-run-and-fix", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/openteams-lab/openteams/tree/main/assets/skills/github-actions-run-and-fixType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add openteams-lab/openteams --skill github-actions-run-and-fix -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install openteams-lab/openteams github-actions-run-and-fix --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openteams-lab/openteams.git skills-src && mkdir -p .agents/skills && cp -r skills-src/assets/skills/github-actions-run-and-fix .agents/skills/github-actions-run-and-fix && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "github-actions-run-and-fix" agent skill from https://github.com/openteams-lab/openteams/tree/main/assets/skills/github-actions-run-and-fix into .agents/skills/github-actions-run-and-fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-actions-run-and-fix", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add openteams-lab/openteams --skill github-actions-run-and-fix -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install openteams-lab/openteams github-actions-run-and-fix --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openteams-lab/openteams.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/assets/skills/github-actions-run-and-fix .cursor/skills/github-actions-run-and-fix && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "github-actions-run-and-fix" agent skill from https://github.com/openteams-lab/openteams/tree/main/assets/skills/github-actions-run-and-fix into .cursor/skills/github-actions-run-and-fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-actions-run-and-fix", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/openteams-lab/openteams.git --path assets/skills/github-actions-run-and-fix--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add openteams-lab/openteams --skill github-actions-run-and-fix -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install openteams-lab/openteams github-actions-run-and-fix --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openteams-lab/openteams.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/assets/skills/github-actions-run-and-fix .gemini/skills/github-actions-run-and-fix && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "github-actions-run-and-fix" agent skill from https://github.com/openteams-lab/openteams/tree/main/assets/skills/github-actions-run-and-fix into .gemini/skills/github-actions-run-and-fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-actions-run-and-fix", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install openteams-lab/openteams github-actions-run-and-fixInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add openteams-lab/openteams --skill github-actions-run-and-fix -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/openteams-lab/openteams.git skills-src && mkdir -p .github/skills && cp -r skills-src/assets/skills/github-actions-run-and-fix .github/skills/github-actions-run-and-fix && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "github-actions-run-and-fix" agent skill from https://github.com/openteams-lab/openteams/tree/main/assets/skills/github-actions-run-and-fix into .github/skills/github-actions-run-and-fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-actions-run-and-fix", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add openteams-lab/openteams --skill github-actions-run-and-fix -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install openteams-lab/openteams github-actions-run-and-fix --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openteams-lab/openteams.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/assets/skills/github-actions-run-and-fix .opencode/skills/github-actions-run-and-fix && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "github-actions-run-and-fix" agent skill from https://github.com/openteams-lab/openteams/tree/main/assets/skills/github-actions-run-and-fix into .opencode/skills/github-actions-run-and-fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-actions-run-and-fix", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
github-actions-run-and-fix- GitHub stars
- 629
- Token cost
- ~923 tokens
- SKILL.md length
- 437 words
- Files
- 2 (incl. scripts)
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
OpenTeams skill for manually starting a GitHub Actions workflow, watching its execution, diagnosing failures, rerunning transient failed jobs, repairing code or configuration errors, and dispatching…
- Works in 8 steps: Confirm the repository, workflow name or… → Start and watch a workflow with the… → To inspect an existing run, use bash… → …
- Tasks that involve CI/CD
- SKILL.md covers OpenTeams context, Required tool, Workflow and Safety boundaries
- Runs Shell scripts from its folder; calls gh, bash and brew; reaches github.com
What it does
GitHub Actions Run And Fix is an agent skill from openteams-lab/openteams. OpenTeams skill for manually starting a GitHub Actions workflow, watching its execution, diagnosing failures, rerunning transient failed jobs, repairing code or configuration errors, and dispatching the workflow again until it passes or the retry limit is reached.
Its SKILL.md is about 920 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/workflow-run.sh`).
It sits in DevOps & Cloud, covering CI/CD. It works with GitHub Actions and GitHub. The repository describes itself as: Plan, Build, and Ship — with a team of AI agents instead of one. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve CI/CD
Example prompts
- “Use the github-actions-run-and-fix skill to openteam skill for manually starting a GitHub Actions workflow, watching its execution, diagnosing…”
- “/github-actions-run-and-fix”
Requirements
- A Bash shell
Workflow steps
8 steps, taken from the first numbered list in SKILL.md.
- Confirm the repository, workflow name or file, git ref, workflow inputs, and target environment. If any deployment target or input is…
- Start and watch a workflow with the bundled script from this skill directory
- To inspect an existing run, use bash scripts/workflow-run.sh --run-id . For a clearly transient failure, use --run-id --rerun-failed once.
- When a run fails, read the summary and failed-step logs emitted by the script. Inspect the relevant workflow and reproduce the failing…
- Classify the failure
- Review the diff, commit only related files, and push normally. Never force-push. Dispatch again only when a push does not already trigger…
- Repeat for at most three repair iterations, including at most one no-change rerun for the same failure signature.
- Report the workflow, run URLs, root cause, reruns, files changed, local verification, pushed commit, and final conclusion.
What it can do on your machine
Read from SKILL.md and the folder at commit ebee9de. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Shell), which the agent can run.
Shell commands in SKILL.md call:
ghbashbrewwinget
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
GitHub Actions Run And Fix loads about 923 tokens when it runs. Until then it costs about 73 tokens; SKILL.md has 437 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from openteams-lab/openteams at commit ebee9de, republished under its Apache-2.0 licence (© openteams-lab). 437 words, ~923 tokens.
Download SKILL.mdSave it as
.claude/skills/github-actions-run-and-fix/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- github-actions-run-and-fix
- description
- OpenTeams skill for manually starting a GitHub Actions workflow, watching its execution, diagnosing failures, rerunning transient failed jobs, repairing code or configuration errors, and dispatching the workflow again until it passes or the retry limit is reached.
Run and Fix a GitHub Actions Workflow
Use this skill for workflows that support workflow_dispatch, or for inspecting and rerunning a known Actions run.
OpenTeams context
This skill is designed specifically for use by OpenTeams members. OpenTeams input prompts should include this marker to make the message source explicit:
[OPENTEAMS_SOURCE=openteams]Treat the marker as a source hint, not a security boundary. Its absence does not block the workflow; continue when the surrounding session context clearly comes from OpenTeams.
Required tool
At the start, check whether GitHub CLI is installed and authenticated:
command -v gh >/dev/null 2>&1 && gh auth statusIf gh is missing, stop and tell the user to install GitHub CLI. Offer the relevant command without installing it automatically:
- macOS:
brew install gh - Windows:
winget install --id GitHub.cli - Linux: follow
https://github.com/cli/cli/blob/trunk/docs/install_linux.md
Then ask the user to run gh auth login. Never request, print, or persist their token.
Workflow
Confirm the repository, workflow name or file, git ref, workflow inputs, and target environment. If any deployment target or input is ambiguous, ask before dispatching.
Start and watch a workflow with the bundled script from this skill directory:
bash bash scripts/workflow-run.sh \ --workflow <workflow-file-or-name> \ --ref <branch-or-tag> \ --field key=valueRepeat
--fieldfor multiple inputs. Add--repo OWNER/REPOwhen the repository cannot be inferred.To inspect an existing run, use
bash scripts/workflow-run.sh --run-id <id>. For a clearly transient failure, use--run-id <id> --rerun-failedonce.When a run fails, read the summary and failed-step logs emitted by the script. Inspect the relevant workflow and reproduce the failing command locally when practical.
Classify the failure:
- Runner, network, rate-limit, cache-service, or temporary external outage: rerun failed jobs once without editing code.
- Code, test, lint, type, build, dependency, or deterministic configuration failure: make the smallest relevant fix and validate it locally.
- Missing permission, secret, approval, protected environment, billing, or unavailable production resource: stop and report the required human action.
Review the diff, commit only related files, and push normally. Never force-push. Dispatch again only when a push does not already trigger the required workflow.
Repeat for at most three repair iterations, including at most one no-change rerun for the same failure signature.
Report the workflow, run URLs, root cause, reruns, files changed, local verification, pushed commit, and final conclusion.
Show full SKILL.md (76 more words)Show less
Safety boundaries
- Ask before starting a production deployment, destructive workflow, rollback, database migration, infrastructure mutation, or workflow with unclear inputs.
- Ask before changing
.github/workflows/**, authentication, permissions, secrets, deployment configuration, or infrastructure. - Do not invent workflow inputs. List available workflows with
gh workflow listand inspect the selected YAML when necessary. - Do not claim success until the target GitHub Actions run finishes successfully. If blocked, return the run URL and exact failed job or required user action.
© openteams-lab, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (scripts) in assets/skills/github-actions-run-and-fix of openteams-lab/openteams.
- SKILL.md
- scripts/workflow-run.sh
Open the folder on GitHubat commit ebee9de
Compare with similar skills
GitHub Actions Run And Fix next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| GitHub Actions Run And Fix this skillopenteams-lab/openteams | 629 | — | ~923 | Automated safety check: Pass | Apache-2.0 | |
| Nushellccusage/ccusage | 19k | — | ~938 | Automated safety check: Pass | Custom licence | |
| Make GitHub Actions Workflowdotnet/efcore | 15k | — | ~2.1k | Automated safety check: Pass | MIT | |
| AI News RadarLearnPrompt/ai-news-radar | 1.8k | — | ~2.5k | Automated safety check: Notes | MIT | |
| Clawsweeperopenclaw/openclaw | 392k | — | ~3k | Automated safety check: Pass | MIT | |
| ONNX Runtime CI Managementmicrosoft/onnxruntime | 22k | — | ~4.1k | Automated safety check: Pass | MIT |
Similar skills
- Official
Make GitHub Actions Workflow
dotnet/efcore
Create GitHub Actions workflows for CI, automation, or PR management.
AI News Radar
LearnPrompt/ai-news-radar
A skill your agent uses when working on AI News Radar, 24 小时 AI 更新雷达, AI 更新雷达, 伯乐Skill, or Scout Skill: finding high-signal AI/tech sources, adding RSS/OPML/GitHub feeds, checking source health…
Clawsweeper
openclaw/openclaw
A skill your agent uses for all ClawSweeper work: OpenClaw issue/PR sweep reports, repair jobs, cloud fix PRs, @clawsweeper maintainer mention commands, trusted ClawSweeper-reviewed…
- Official
ONNX Runtime CI Management
microsoft/onnxruntime
Triggers, re-runs and unblocks the CI checks on an ONNX Runtime pull request, after diagnosing whether a failure is transient or needs a code change.
CI Watchdog
latitude-dev/latitude-llm
Continuously monitor GitHub PR CI checks and automatically fix failures until all checks pass.
More from openteams-lab/openteams
Brainstorming
openteams-lab/openteams
OpenTeams-only workflow skill. An agent skill from openteams-lab/openteams.
Code Guidelines
openteams-lab/openteams
OpenTeams-only workflow skill. An agent skill from openteams-lab/openteams.
GitHub PR Actions Fix
openteams-lab/openteams
OpenTeams skill for watching GitHub Actions checks after a pull request is submitted or updated, inspecting failures, making the smallest safe code fix, validating locally, pushing to the PR branch…
Planning Mode
openteams-lab/openteams
A skill your agent uses when the user asks to break down a goal into a clear, executable, reviewable task plan using WBS, dependencies, milestones, RACI, risk register, and plan review.
Using Git Worktrees
openteams-lab/openteams
A skill your agent uses when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools, git…
Writing Plans
openteams-lab/openteams
OpenTeams-only workflow skill. An agent skill from openteams-lab/openteams.
Related
Works with
Categories
Questions about GitHub Actions Run And Fix
What does GitHub Actions Run And Fix do?
OpenTeams skill for manually starting a GitHub Actions workflow, watching its execution, diagnosing failures, rerunning transient failed jobs, repairing code or configuration errors, and dispatching…. GitHub Actions Run And Fix is an agent skill from openteams-lab/openteams. OpenTeams skill for manually starting a GitHub Actions workflow, watching its execution, diagnosing failures, rerunning transient failed jobs, repairing code or configuration errors, and dispatching the workflow again until it passes or the retry limit is reached.
When should I use GitHub Actions Run And Fix?
GitHub Actions Run And Fix fits situations like: tasks that involve CI/CD.
How do I install GitHub Actions Run And Fix in Claude Code?
Run `npx skills add openteams-lab/openteams --skill github-actions-run-and-fix -a claude-code`. Or copy the skill folder (assets/skills/github-actions-run-and-fix in openteams-lab/openteams) into .claude/skills/github-actions-run-and-fix in your project. Claude Code loads it when a task matches its description.
How do I install GitHub Actions Run And Fix in Codex?
Run `npx skills add openteams-lab/openteams --skill github-actions-run-and-fix -a codex`. Or copy the skill folder (assets/skills/github-actions-run-and-fix in openteams-lab/openteams) into .agents/skills/github-actions-run-and-fix in your project. Codex loads it when a task matches its description.
Can I use GitHub Actions Run And Fix in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add openteams-lab/openteams --skill github-actions-run-and-fix -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/github-actions-run-and-fix, .gemini/skills/github-actions-run-and-fix, .github/skills/github-actions-run-and-fix and .opencode/skills/github-actions-run-and-fix in your project.
What does GitHub Actions Run And Fix need to run?
Going by SKILL.md and its folder, GitHub Actions Run And Fix needs a shell for the scripts in its folder and the command-line tools its instructions call (gh, bash, brew and winget). Our summary lists: A Bash shell.
Does GitHub Actions Run And Fix access the network?
SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is GitHub Actions Run And Fix safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does GitHub Actions Run And Fix use?
GitHub Actions Run And Fix is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does GitHub Actions Run And Fix use?
About 923 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to GitHub Actions Run And Fix?
Skills that share tags, products or a category with GitHub Actions Run And Fix: Nushell (ccusage/ccusage, 19k stars), Make GitHub Actions Workflow (dotnet/efcore, 15k stars), AI News Radar (LearnPrompt/ai-news-radar, 1.8k stars) and Clawsweeper (openclaw/openclaw, 392k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains GitHub Actions Run And Fix?
openteams-lab (a GitHub organization) maintains it in openteams-lab/openteams, which has 629 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 4, 2026.
Source: openteams-lab/openteams on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.