Skip to content
TrustedSkillsbeta
Back to all skills

Github Actions

Checked
bagelhole·vlatest·devops·MIT

Automates GitHub Actions workflows with custom logic and error handling using Bagelhole's intelligent automation engine.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add bagelhole/devops-security-agent-skills --skill github-actions -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

bagelhole

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Only contacts known or declared hosts: github.com.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

    Hosts contacted

    github.comsource host

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned bagelhole/devops-security-agent-skills at 0365f57a07.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
0365f57a07
Manifest
devops/ci-cd/github-actions/SKILL.md
Scanned
2 files, 417 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The bagelhole-github-actions skill enables AI agents to interact with and manage GitHub Actions workflows. It allows for triggering workflow runs, retrieving workflow run details (status, logs), and potentially modifying or creating workflows based on user instructions. This facilitates automation of CI/CD processes and enhances DevOps security practices within a GitHub environment.

When to use it

  • Automated Testing: Triggering test workflows in response to code commits or pull requests.
  • Security Audits: Running security scanning workflows on demand to identify vulnerabilities.
  • Deployment Pipelines: Automating deployment steps by triggering release workflows based on specific events.
  • Workflow Troubleshooting: Retrieving logs and status information for failed workflow runs to aid in debugging.

Key capabilities

  • Triggering GitHub Actions workflows
  • Retrieving workflow run details (status, logs)

Example prompts

  • "Run the 'security-scan' workflow on the main branch."
  • "What is the status of the last deployment workflow?"
  • "Show me the logs for the failed test workflow."

Tips & gotchas

  • The agent will require appropriate GitHub API access tokens with sufficient permissions to interact with workflows. Ensure these are securely managed and scoped appropriately.