GitHub Actions Linter for Openclaw

A specialized linter for GitHub Actions YAML files to detect security risks, deprecated actions, and syntax errors.

charlie-morrison
v1.0.1
May 1, 2026
0
840
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install github-actions-linter

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install github-actions-linter using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is GitHub Actions Linter?

This skill provides a comprehensive suite of tools for validating GitHub Actions workflow files. By utilizing the provided Python script, developers can perform deep audits on their CI/CD pipelines to ensure adherence to best practices and security standards. It is an essential component for teams using Openclaw Skills to automate their development lifecycle, offering detection for shell injection, hardcoded secrets, and outdated action versions.

GitHub Actions Linter Use Cases

  • Auditing existing GitHub Actions workflows for security vulnerabilities like shell injection or hardcoded secrets.
  • Validating the syntax and structure of new .github/workflows/*.yml files during development.
  • Identifying and upgrading deprecated action versions or runner labels to maintain pipeline health.
  • Automating workflow linting within a CI/CD process to enforce consistent standards across a repository using Openclaw Skills.

How GitHub Actions Linter Works

  1. The user provides a workflow file or directory to the Python-based linter script.
  2. The linter parses the YAML structure and evaluates it against 28 distinct rules across syntax, security, and best practices.
  3. A security audit scans for specific risks like untrusted event contexts and permissive permissions.
  4. A deprecation check compares used actions against known outdated versions.
  5. Results are generated in the requested format (Text, JSON, or Markdown) for review or automated consumption.

GitHub Actions Linter Setup

To install and use this skill within Openclaw Skills, ensure you have Python 3 installed. You can execute the linter directly from your terminal using the following commands:

# Run general linting on a directory
python3 scripts/gha_linter.py lint .github/workflows/ --strict

# Run a security audit on a specific file
python3 scripts/gha_linter.py security .github/workflows/main.yml

# Check for deprecated actions
python3 scripts/gha_linter.py deprecated .github/workflows/main.yml

GitHub Actions Linter Data Schema & Taxonomy

The skill produces structured feedback regarding workflow health. It categorizes issues based on a set of 28 predefined rules:

Category Rules Covered
Syntax & Structure Missing triggers, empty jobs, circular dependencies, and missing runs-on labels.
Security Shell injection detection, hardcoded secrets, permissive permissions, and untrusted contexts.
Deprecated Outdated action versions, deprecated runner labels, and legacy command usage.
Best Practices Timeout settings, step naming, concurrency management, and runner optimization.

GitHub Actions Linter Advanced Features

  • Multi-format output support (JSON, Text, Markdown) for seamless integration with other tools in the Openclaw Skills ecosystem.
  • Strict mode configuration via the --strict flag to treat all warnings as build-failing errors.
  • Recursive directory scanning for bulk auditing of large enterprise repositories.
  • Specialized security module for detecting complex attack vectors like pull_request_target exploitation.
  • Automated CI/CD integration examples provided for self-linting workflows.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*