Run any Skill in Manus with one click

github-workflows

Stars941

Forks83

UpdatedMay 22, 2026 at 16:58

Work with GitHub Actions CI/CD workflows - read live syntax, monitor runs, and debug failures. Use when writing, running, or debugging GitHub Actions workflows.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

open-gsd

open-gsd/gsd-pi

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

10 files

SKILL.md

readonly

name	github-workflows
description	Work with GitHub Actions CI/CD workflows - read live syntax, monitor runs, and debug failures. Use when writing, running, or debugging GitHub Actions workflows.

GitHub Workflows

Mission: Work with GitHub Actions without using stale training data. All syntax, versions, and parameters come from live sources.

Structural Principle

All CI operations go through ci_monitor.cjs. Never reach for gh CLI directly — the script wraps it with observable output.

Primary Tool: ci_monitor.cjs

Path: scripts/ci_monitor.cjs

node scripts/ci_monitor.cjs <command>

Before using any command:

Run --help to discover available arguments

Routing Table:

When You Need	Command
List recent runs	`runs [--branch <name>]`
Monitor running workflow	`watch <run-id>`
Fail fast in scripts	`fail-fast <run-id>`
See why run failed	`log-failed <run-id>`
Test pass/fail counts	`test-summary <run-id>`
Check action versions	`check-actions [file]`
Search logs	`grep <run-id> --pattern <regex>`
Wait for deployment	`wait-for <run-id> <job> --keyword <text>`

Documentation Routing

Base URL: https://docs.github.com/en/actions/reference/workflows-and-actions/

Before writing any workflow syntax:

Fetch the relevant .md file from the URL above
Read only the section you need

Task	File	Section
Create workflow	workflow-syntax.md	`name`, `on`, `jobs`
Set triggers	workflow-syntax.md	`on`
Set permissions	workflow-syntax.md	`permissions`
Concurrency	workflow-syntax.md	`concurrency`
Reusable workflow	workflow-syntax.md	`on.workflow_call`
Annotations	workflow-commands.md	"Setting an error/warning/notice message"
Output variables	workflow-commands.md	"Environment files"
Conditionals	expressions.md	"Operators", "Functions"
Contexts	contexts.md	" context"
Events	events-that-trigger-workflows.md	Event tables

Version Verification

What	Where
Action versions	`node ci_monitor.cjs check-actions <file>`
Node.js LTS	`curl -s https://nodejs.org/dist/index.json \| jq '.[0].version'`

Validation Constraint

"No errors" is not validation. Prove observable change:

BEFORE: [specific state]
AFTER:  [different state]
EVIDENCE: [output from ci_monitor.cjs]

References

references/gh/SKILL.md — gh CLI reference

More from this repository

same repository

gsd-headless

open-gsd/gsd-pi

Orchestrate GSD (Git Ship Done) projects programmatically via headless CLI. Use when an agent needs to create milestones from specs, execute dev workflows, monitor progress, check status, or control execution (pause/stop/skip/steer). Triggers on "run gsd", "create milestone", "execute project", "check gsd status", "orchestrate development", "run headless workflow", or building orchestrators that coordinate multiple GSD workers.

2026-07-12941

gsd-orchestrator

open-gsd/gsd-pi

Build software products autonomously via GSD headless mode. Handles the full lifecycle: write a spec, launch a build, poll for completion, handle blockers, track costs, and verify the result. Use when asked to "build something", "create a project", "run gsd", "check build status", or any task that requires autonomous software development via subprocess.

2026-06-21941

create-skill

open-gsd/gsd-pi

Expert guidance for creating, writing, building, and refining GSD skills. Use when working with SKILL.md files, authoring new skills, improving existing skills, or understanding skill structure and best practices.

2026-06-15941

spike-wrap-up

open-gsd/gsd-pi

Package findings from a completed spike into a durable project-local skill that auto-loads on future similar work. Reads the latest `.gsd/workflows/spikes/` dir, interviews the user on what's reusable, then writes `.agents/skills/<name>/SKILL.md`. Use when asked to "wrap up the spike", "package this as a skill", "make this reusable", "turn findings into a skill", or at the synthesize phase of `/gsd start spike`.

2026-06-11941

debug-like-expert

open-gsd/gsd-pi

Deep analysis debugging mode for complex issues. Activates methodical investigation protocol with evidence gathering, hypothesis testing, and rigorous verification. Use when standard troubleshooting fails or when issues require systematic root cause analysis.

2026-05-31941

decompose-into-slices

open-gsd/gsd-pi

Break a plan or milestone brief into independently-grabbable vertical slices (tracer bullets), written to `M###-ROADMAP.md` by default (GitHub issues only on explicit confirmation). Prefers many thin slices over few thick ones and marks dependency order. Use when asked to "break this into slices", "decompose the plan", "vertical slices", "break into issues", or when a plan needs task-level decomposition.

2026-05-31941

name	github-workflows
description	Work with GitHub Actions CI/CD workflows - read live syntax, monitor runs, and debug failures. Use when writing, running, or debugging GitHub Actions workflows.

GitHub Workflows

Mission: Work with GitHub Actions without using stale training data. All syntax, versions, and parameters come from live sources.

Structural Principle

All CI operations go through ci_monitor.cjs. Never reach for gh CLI directly — the script wraps it with observable output.

Primary Tool: ci_monitor.cjs

Path: scripts/ci_monitor.cjs

node scripts/ci_monitor.cjs <command>

Before using any command:

Run --help to discover available arguments

Routing Table:

When You Need	Command
List recent runs	`runs [--branch <name>]`
Monitor running workflow	`watch <run-id>`
Fail fast in scripts	`fail-fast <run-id>`
See why run failed	`log-failed <run-id>`
Test pass/fail counts	`test-summary <run-id>`
Check action versions	`check-actions [file]`
Search logs	`grep <run-id> --pattern <regex>`
Wait for deployment	`wait-for <run-id> <job> --keyword <text>`

Documentation Routing

Base URL: https://docs.github.com/en/actions/reference/workflows-and-actions/

Before writing any workflow syntax:

Fetch the relevant .md file from the URL above
Read only the section you need

Task	File	Section
Create workflow	workflow-syntax.md	`name`, `on`, `jobs`
Set triggers	workflow-syntax.md	`on`
Set permissions	workflow-syntax.md	`permissions`
Concurrency	workflow-syntax.md	`concurrency`
Reusable workflow	workflow-syntax.md	`on.workflow_call`
Annotations	workflow-commands.md	"Setting an error/warning/notice message"
Output variables	workflow-commands.md	"Environment files"
Conditionals	expressions.md	"Operators", "Functions"
Contexts	contexts.md	" context"
Events	events-that-trigger-workflows.md	Event tables

Version Verification

What	Where
Action versions	`node ci_monitor.cjs check-actions <file>`
Node.js LTS	`curl -s https://nodejs.org/dist/index.json \| jq '.[0].version'`

Validation Constraint

"No errors" is not validation. Prove observable change:

BEFORE: [specific state]
AFTER:  [different state]
EVIDENCE: [output from ci_monitor.cjs]

References

references/gh/SKILL.md — gh CLI reference