Github Workflows Query Agent Skill
List GitHub Actions workflows with per_page pagination support.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/github/gh-aw --skill github-workflows-queryWhat comes with it
2 453 bytes besides the instructionThe instruction itself
7 sections, as written by the authorGitHub Workflows Query Skill
List GitHub Actions workflows with efficient pagination using the --per-page flag.
Usage
Use this script to list workflows from any repository with controlled page sizes.
Basic Usage
./query-workflows.sh --owner github --repo gh-aw
# Returns 10 workflows (default per_page=10)
Pagination
# Get the first workflow only
./query-workflows.sh --owner github --repo gh-aw --per-page 1
# Get 50 workflows starting from page 2
./query-workflows.sh --owner github --repo gh-aw --per-page 50 --page 2
Parameters
| Parameter | Required | Default | Description |
|-----------|----------|---------|-------------|
| --owner | Yes | - | Repository owner (username or organization) |
| --repo | Yes | - | Repository name |
| --per-page | No | 10 | Results per page (1–100) |
| --page | No | 1 | Page number |
Output
Returns JSON with the following fields:
{
"total_count": 42,
"per_page": 10,
"page": 1,
"workflows": [
{
"id": 12345,
"node_id": "W_...",
"name": "CI",
"path": ".github/workflows/ci.yml",
"state": "active",
"created_at": "2024-01-01T00:00:00Z",
"updated_at": "2024-01-01T00:00:00Z",
"url": "https://api.github.com/repos/owner/repo/actions/workflows/12345",
"html_url": "https://github.com/owner/repo/actions/workflows/ci.yml",
"badge_url": "https://github.com/owner/repo/actions/workflows/ci.yml/badge.svg"
}
]
}
Source
Calls the GitHub REST API:
GET /repos/{owner}/{repo}/actions/workflows?per_page={n}&page={n}
Other skills for the same job
different authors, same section of the catalogue
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
Use when complex problems require systematic step-by-step reasoning with ability to revise thoughts, branch into alternative approaches, or dynamically adjust scope. Ideal for multi-stage analysis, design planning, problem decomposition, or tasks with initially unclear scope.
Multi-agent workflow examples to work together on the OpenServ Platform. Covers agent discovery, multi-agent workspaces, task dependencies, and workflow orchestration using the Platform Client. Read reference.md for the full API reference. Read openserv-agent-sdk and openserv-client for building and running agents.
> Compress natural language memory files (CLAUDE.md, todos, preferences) into caveman format to save input tokens. Preserves all technical substance, code, URLs, and structure. Compressed version overwrites the original file. Human-readable backup saved as FILE.original.md.
API design principles and decision-making. REST vs GraphQL vs tRPC selection, response formats, versioning, pagination.
Patterns for automating GitHub workflows with AI assistance, inspired by [Gemini CLI](https://github.com/google-gemini/gemini-cli) and modern DevOps practices.
Groups existing components into logical business domains to plan service-based architecture. Use when asking "which components belong together?", "group these into services", "organize by domain", "component-to-domain mapping", or planning service extraction from an existing codebase. Do NOT use for identifying new domains from scratch (use domain-analysis) or analyzing coupling (use coupling-analysis).
API design principles and decision-making. REST vs GraphQL vs tRPC selection, response formats, versioning, pagination.
How to use it
Take github/github-workflows-query from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.