gg-actions
Use when authoring, reviewing, or operating GitHub Actions workflows, including triggers, permissions, secrets, pinning, artifacts, runners, concurrency, or OIDC.
- License 许可
- MIT
- 所属仓库
- xiaden/SkyScow
- 最近更新
- 2026-09-30
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- gg-actions
- description
- Use when authoring, reviewing, or operating GitHub Actions workflows, including triggers, permissions, secrets, pinning, artifacts, runners, concurrency, or OIDC.
02 资源文件 10
- 参考文档references/action-pinning.md1.8 KB
- 参考文档references/credentials-and-visibility.md7.2 KB
- 参考文档references/events-and-dispatch.md2.3 KB
- 参考文档references/oidc-trust.md2.3 KB
- 参考文档references/runners.md1.9 KB
- 参考文档references/workflow-authoring.md1.2 KB
- 参考文档references/workflow-lifecycle.md4.3 KB
- 参考文档references/workflow-operations.md2.0 KB
- 参考文档references/workflow-permissions.md1.5 KB
- 参考文档references/workflow-secrets.md1.8 KB
03 SKILL.md 正文
gg-actions
Purpose: Guide secure GitHub Actions workflow authoring and operation — how to write, trigger, secure, and operate workflows through the terminal with gh, including the full inspect/branch/push/run/watch/logs/artifact/cancel/cleanup/iterate lifecycle.
When to use
- Writing or revising a workflow file (
.github/workflows/*.yml) - Choosing workflow triggers and reviewing over-broad or privileged triggers
- Setting least-privilege permissions and minimal
GITHUB_TOKENscopes - Handling Actions and environment secrets safely
- Pinning and vetting third-party actions
- Tuning cache, artifacts, and concurrency
- Choosing between hosted and self-hosted runners
- Enabling cloud authentication through OpenID Connect (OIDC)
- Dispatching a workflow manually (
workflow_dispatch) with inputs and environment protection
Do NOT use for local history work — load gg-core. Do NOT use for collaboration, PRs, releases, or branch protection — load gg-repos. Do NOT use for credentials, secrets, permissions, or environment fact lookup — load gg-env.
First safe step
Review what the workflow can do before writing it: inspect its triggers, its permissions block, and every third-party action it references. Default to the least privilege that still lets the workflow complete. Never put a token, secret, or private key in plaintext.
Task index
- Author workflow syntax and structure -> references/workflow-authoring.md
- Choose events and triggers, and dispatch workflows manually -> references/events-and-dispatch.md
- Set least-privilege permissions and minimal token scopes -> references/workflow-permissions.md
- Store and use Actions and environment secrets -> references/workflow-secrets.md
- Pin and vet third-party actions -> references/action-pinning.md
- Control cache, artifacts, and concurrency -> references/workflow-operations.md
- Choose hosted or self-hosted runners -> references/runners.md
- Enable cloud auth with OpenID Connect -> references/oidc-trust.md
- Run and drive the full workflow lifecycle (branch + push a change, dispatch/run, watch, view status and logs, download artifacts, cancel, clean up, iterate) -> references/workflow-lifecycle.md
- Look up shared visibility, credential, and artifact-attestation facts -> references/credentials-and-visibility.md
Ownership
This skill owns the workflow authoring and lifecycle capability: inspecting/creating/modifying/removing workflow files, branching and pushing the change, dispatching or running via gh (gh workflow run/repository_dispatch), watching runs, viewing status and logs, downloading artifacts, cancelling failed/stale runs, cleaning up temporary branches/workflows/runs where supported, and iterating code from collected results until verification passes. Local branch/commit state is gg-core; push/remotes/PR collaboration is gg-repos; credentials/PAT hygiene is gg-env; hosted Docker/artifacts is gg-artifacts. Name those skills as pointers only; do not duplicate their reference files here.
Unmatched task
Consult the official GitHub Actions documentation: https://docs.github.com/actions.
04 同仓库更多 Skills
unquoted-colon
暂无简介
quoted-description
Use when a plain scalar contains a colon: like this one.
block-description
Use when a plain scalar contains a colon: like this one.
work-routing
Canonical authority for who owns the next unit of work — direct work versus delegation, task tiers, bounded localization, the Change DAG size threshold, R&D evaluation routing, progressive research escalation, researcher scope signals, and QA/support owner selection. Use before choosing execution, investigation, design, or QA ownership; do not use to construct dispatch prompts, handoff schemas, or Change DAG/DD tool operation.
update-docs
Update project documentation to match code changes — generate codemaps, refresh READMEs, detect doc/code drift using AST analysis. Use when updating documentation after code changes, generating codemaps, verifying doc accuracy, or detecting stale documentation. Do NOT use for writing API reference docs from scratch (use doc-coauthoring) or for creating new skill files (use making-editing-skills).
skill-loading-system
Explain or troubleshoot OpenCode skill discovery, loading, permissions, availability, or prompt injection.