gh-aw
Skill4 starsChanged 6 months agoMITView on GitHub
GitHub Agentic Workflows (`gh aw`) operations for repository automation, creating workflows, running coding agents, and auditing workflow runs. You MUST load this skill when working with the `gh aw` command.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- prowler-cloud/prowlertheir own version, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- prowler-cloud/prowler★ 15ksame name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository124 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/AGENTS.mdAGENTS.md
- .github/workflows/AGENTS.mdAGENTS.md
- .vscode/AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- agent-log-analysisSkill
- agent-mdSkill
- agent-md-writerSkill
- agent-skill-md-writerSkill
- agentskillsSkill
- agents-md-writerSkill
- ai-prompt-writerSkill
- ansibleSkill
- apache-airflow-apiSkill
- apache-airflow-dagsSkill
- astro-cliSkill
- astronomer-docsSkill
- awesome-copilotSkill
- brainstorm-agent-runsSkill
- brainstorm-github-prSkill
- brainstormSkill
- catSkill
- chrome-devtoolsSkill
- claude-docsSkill
- codeqlSkill
- code-reviewSkill
- code-tourSkill
- coding-standard-writerSkill
- context-aware-opsSkill
- copilot-cliSkill
- copilot-docsSkill
- critical-thinkingSkill
- datadog-agentSkill
- datadog-apiSkill
- datadog-mcpSkill
- datadog-monitorsSkill
- datadog-pulumiSkill
- devcontainerSkill
- dictationSkill
- direnvSkill
- dockerfileSkill
- dockerSkill
- docs-reviewSkill
- docs-writerSkill
- dot-claudeSkill
- dotfilesSkill
- dot-githubSkill
- editorconfigSkill
- fact-writerSkill
- gdpr-compliantSkill
- gh-agent-taskSkill
- gh-apiSkill
- gh-aw-compileSkill
- gh-aw-firewall-debugSkill
- gh-aw-firewallSkill
- gh-aw-newSkill
- gh-aw-troubleshootingSkill
- gh-codespaceSkill
- gh-issueSkill
- gh-modelsSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 2 are distinctive, and 9 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Very specific: line 12
Use gh aw to orchestrate GitHub Agentic Workflows for repository automation.
- Very specific: line 17
When compiling .md agent definitions into executable .lock.yml GitHub Actions.
- Distinctive: line 23
When writing application code that simply uses the OpenAI or Anthropic API directly.
- Very specific: line 40
If gh extension install is unavailable or fails (e.g., in environments without GitHub CLI extension support), you can download and run the …
- Very specific: line 122
Setup: Use gh aw init to initialize a repository, followed by gh aw new <workflow-name> or gh aw add-wizard.
- Very specific: line 124
Execution: Use gh aw run <workflow-name> to execute a workflow or gh aw trial for simulated runs.
- Very specific: line 125
Analysis: If a run fails, load the gh-aw-troubleshooting skill to diagnose the root cause using gh aw audit and gh aw logs.
- Very specific: line 126
Updating: Run gh aw upgrade to get the latest agent files and apply codemods.
- Distinctive: line 130
Always review the changes made by the AI agent, especially considering security and context.
- Very specific: line 131
Do not manually edit the generated .lock.yml files.
- Very specific: line 142
When asked to create, update, debug, or upgrade GitHub Agentic Workflows, use webfetch to retrieve and read the appropriate instruction …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- markdownlint-disable MD013 MD023 MD031 MD032 -->gh-aw Skill
Use gh aw to orchestrate GitHub Agentic Workflows for repository automation.
When to Use
- To initialize, create, update, or run GitHub Agentic Workflows.
- When compiling
.mdagent definitions into executable.lock.ymlGitHub Actions. - To manage MCP (Model Context Protocol) servers and toolsets within a repository's agent configuration.
When Not to Use
- For standard GitHub CLI operations that don't involve the Agentic Workflows extension (e.g., just listing issues or PRs).
- When writing application code that simply uses the OpenAI or Anthropic API directly.
- For troubleshooting a failed workflow run (use
gh-aw-troubleshootinginstead).
Common Pitfalls
- Manual Lockfile Edits: Directly editing the
.lock.ymlfile, which will be silently overwritten the next timegh aw compileis run. - Skipping Compilation: Changing an agent's
.mddefinition but forgetting to rungh aw compile, causing the CI pipeline to run the outdated version. - Missing Extension: Attempting to run
gh awcommands on a fresh runner without first executinggh extension install github/gh-aw.
How to Install the Extension
To install the GitHub Agentic Workflows extension for the GitHub CLI, run:
gh extension install github/gh-awIf gh extension install is unavailable or fails (e.g., in environments
without GitHub CLI extension support), you can download and run the
installation script:
curl -sL https://raw.githubusercontent.com/github/gh-aw/v0.74.3/install-gh-aw.sh -o install-gh-aw.sh
head -n 50 install-gh-aw.sh # Review the script before executing
bash install-gh-aw.shMindmap of Commands
mindmap
root((gh aw))
Setup Commands
add
Add workflows
add-wizard
Interactively add workflows
init
Initialize repository
new
Create new workflow
remove
Remove workflow files
secrets
Manage secrets
update
Update workflows
upgrade
Upgrade repository
Development Commands
compile
Compile workflows into YAML
domains
List network domains
fix
Apply automatic fixes
lint
Lint workflows
mcp
Manage MCP servers
validate
Validate workflows
Execution Commands
disable
Disable workflows
enable
Enable workflows
run
Run workflows on GitHub Actions
trial
Run in trial mode
Analysis Commands
list
List workflows
audit
Audit workflow runs
checks
Classify CI check state
health
Show health overview
logs
Analyze workflow logs
status
Show workflow status
Utilities
completion
Generate shell completion
hash-frontmatter
Compute frontmatter hash
mcp-server
Run MCP server
pr
Pull request utilities
project
Create Projects V2 boardsCore Process
- Setup: Use
gh aw initto initialize a repository, followed bygh aw new <workflow-name>orgh aw add-wizard. - Development: Workflows are markdown files compiled via
gh aw compileinto GitHub Actions YAML (.lock.yml). - Execution: Use
gh aw run <workflow-name>to execute a workflow orgh aw trialfor simulated runs. - Analysis: If a run fails, load the
gh-aw-troubleshootingskill to diagnose the root cause usinggh aw auditandgh aw logs. - Updating: Run
gh aw upgradeto get the latest agent files and apply codemods.
What to Avoid
- Always review the changes made by the AI agent, especially considering security and context.
- Do not manually edit the generated
.lock.ymlfiles; they are intended to be compiled from the markdown workflows.
References
Agentic Workflow Prompts
When asked to create, update, debug, or upgrade GitHub Agentic Workflows,
use webfetch to retrieve and read the appropriate instruction prompt from the official repository before proceeding:
Setup docs
Related Skills
- gh-aw-compile: You MUST load this skill when recompiling Agentic Workflows.
- gh-aw-troubleshooting: You MUST load this skill to diagnose and fix failing Agentic Workflows.
- gh-run: You MUST load this skill when working with GitHub Actions workflow runs.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

