Agent skill

GitHub Actions Pipeline Builder

by curiositech in curiositech/some_claude_skills

Build production CI/CD pipelines with GitHub Actions. An agent skill from curiositech/some_claude_skills.

MITAuto-check: notesDevOps & Cloud

Install GitHub Actions Pipeline Builder

skills CLI
$ npx skills add curiositech/some_claude_skills --skill github-actions-pipeline-builder -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install curiositech/some_claude_skills github-actions-pipeline-builder --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/curiositech/some_claude_skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/github-actions-pipeline-builder .claude/skills/github-actions-pipeline-builder && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
github-actions-pipeline-builder
GitHub stars
243
Token cost
~2.8k tokens
SKILL.md length
475 words
Files
6 (incl. scripts, references, assets)
Skills in repo
108
Repo updated
First seen
Licence
MIT

At a glance

Build production CI/CD pipelines with GitHub Actions. An agent skill from curiositech/some_claude_skills.

  • Works in 3 steps: Repo Settings → Secrets and variables →… → New repository secret → Name: PRODUCTION_API_KEY, Value: sk-...
  • Automated testing
  • SKILL.md covers When to Use, Quick Decision Tree, Technology Selection and Common Anti-Patterns, plus 6 more sections
  • Runs TypeScript scripts from its folder; needs PRODUCTION_API_KEY and API_KEY

What it does

GitHub Actions Pipeline Builder is an agent skill from curiositech/some_claude_skills. Build production CI/CD pipelines with GitHub Actions. Implements matrix builds, caching, deployments, testing, security scanning. Use for automated testing, deployments, release workflows. Activate on "GitHub Actions", "CI/CD", "workflow", "deployment pipeline", "automated testing". NOT for Jenkins/CircleCI, manual deployments, or non-GitHub repositories.

Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including scripts, reference files and assets (for example `.claude-plugin/plugin.json`, `assets/workflows/full-stack-ci-cd.yml` and `references/advanced-caching.md`).

It sits in DevOps & Cloud, covering CI/CD. It works with GitHub Actions, GitHub and Jenkins. The repository describes itself as: Claude skills that make my life easier. The licence is MIT.

When your agent uses it

  • Automated testing
  • Release workflows

Example prompts

  • “GitHub Actions”
  • “workflow”
  • “deployment pipeline”
  • “/github-actions-pipeline-builder”

Requirements

  • Node.js
  • Docker
  • A credential in API_KEY
  • A credential in PRODUCTION_API_KEY
  • Pre-approved tools (allowed-tools): Read, Write, Edit, Bash

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Repo Settings → Secrets and variables → Actions
  2. New repository secret
  3. Name: PRODUCTION_API_KEY, Value: sk-...

What it can do on your machine

Read from SKILL.md and the folder at commit 6713fc7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Bash

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 2 files in scripts/ (TypeScript), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • PRODUCTION_API_KEY
    • API_KEY
    • GITHUB_TOKEN
    • AWS_ACCESS_KEY_ID
    • AWS_ACCESS_KEY
    • NODE_AUTH_TOKEN
    • NPM_TOKEN
    • DOCKERHUB_TOKEN

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

GitHub Actions Pipeline Builder loads about 2.8k tokens when it runs, and up to ~5.1k if it reads all its reference files. Until then it costs about 97 tokens; SKILL.md has 475 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~97
When it runs · the whole SKILL.md, loaded when a task matches
~2.8k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:202
    - Pre-2022: Some teams committed .env files
  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Write, Edit, Bash

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from curiositech/some_claude_skills at commit 6713fc7, republished under its MIT licence (© curiositech). 475 words, ~2,821 tokens.

Download SKILL.mdSave it as .claude/skills/github-actions-pipeline-builder/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
github-actions-pipeline-builder
description
Build production CI/CD pipelines with GitHub Actions. Implements matrix builds, caching, deployments, testing, security scanning. Use for automated testing, deployments, release workflows. Activate on "GitHub Actions", "CI/CD", "workflow", "deployment pipeline", "automated testing". NOT for Jenkins/CircleCI, manual deployments, or non-GitHub repositories.
allowed-tools
Read, Write, Edit, Bash
metadata.category
DevOps & Site Reliability
metadata.tags
github, actions, pipeline, github-actions, ci/cd

GitHub Actions Pipeline Builder

Expert in building production-grade CI/CD pipelines with GitHub Actions that are fast, reliable, and secure.

When to Use

✅ Use for:

  • Automated testing on every commit
  • Deployment to staging/production
  • Docker image building and publishing
  • Release automation with versioning
  • Security scanning and dependency audits
  • Code quality checks (linting, type checking)
  • Multi-environment workflows

❌ NOT for:

  • Non-GitHub repositories (use Jenkins, CircleCI, etc.)
  • Complex pipelines better suited for dedicated CI/CD tools
  • Self-hosted runners (covered in advanced patterns)

Quick Decision Tree

Does your project need:
├── Testing on every PR? → GitHub Actions
├── Automated deployments? → GitHub Actions
├── Matrix builds (Node 16, 18, 20)? → GitHub Actions
├── Secrets management? → GitHub Actions secrets
├── Multi-cloud deployments? → GitHub Actions + OIDC
└── Sub-second builds? → Consider build caching

Technology Selection

GitHub Actions vs Alternatives

Why GitHub Actions in 2024:

  • Native integration: No third-party setup
  • Free for public repos: 2000 minutes/month for private
  • Matrix builds: Test multiple versions in parallel
  • Marketplace: 10,000+ pre-built actions
  • OIDC support: Keyless cloud deployments

Timeline:

  • 2019: GitHub Actions released
  • 2020: Became standard for OSS projects
  • 2022: OIDC support for secure cloud auth
  • 2024: De facto CI/CD for GitHub repos
When to Use Alternatives
ScenarioUseWhy
Self-hosted GitLabGitLab CINative integration
Complex enterprise workflowsJenkinsMore flexible
Bitbucket reposBitbucket PipelinesNative integration
Extremely large repos (>10GB)BuildKiteBetter for monorepos

Common Anti-Patterns

Anti-Pattern 1: No Dependency Caching

Novice thinking: "Install dependencies fresh every time for consistency"

Problem: Wastes 2-5 minutes per build installing unchanged dependencies.

Wrong approach:

yaml
# ❌ Slow: Downloads all dependencies every run
- name: Install dependencies
  run: npm install

Correct approach:

yaml
# ✅ Fast: Cache dependencies, only download changes
- name: Cache node_modules
  uses: actions/cache@v3
  with:
    path: ~/.npm
    key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}
    restore-keys: |
      ${{ runner.os }}-node-

- name: Install dependencies
  run: npm ci  # Faster than npm install

Impact: Reduces install time from 3 minutes → 30 seconds.

Timeline:

  • Pre-2020: Most workflows had no caching
  • 2020+: Caching became standard
  • 2024: Setup actions include built-in caching

Anti-Pattern 2: Duplicate YAML (No Matrix Builds)

Problem: Copy-paste workflows for different Node versions.

Wrong approach:

yaml
# ❌ Duplicated workflows
jobs:
  test-node-16:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - uses: actions/setup-node@v3
        with:
          node-version: 16
      - run: npm test

  test-node-18:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - uses: actions/setup-node@v3
        with:
          node-version: 18
      - run: npm test

  test-node-20:
    # ... same steps again

Correct approach:

yaml
# ✅ DRY: Matrix build
jobs:
  test:
    runs-on: ubuntu-latest
    strategy:
      matrix:
        node-version: [16, 18, 20]
    steps:
      - uses: actions/checkout@v3
      - uses: actions/setup-node@v3
        with:
          node-version: ${{ matrix.node-version }}
          cache: 'npm'
      - run: npm ci
      - run: npm test

Benefits: 66% less YAML, tests run in parallel.


Show full SKILL.md (217 more words)Show less
Anti-Pattern 3: Secrets in Code

Problem: Hardcoded API keys, tokens visible in repo.

Symptoms: Security scanner alerts, leaked credentials.

Correct approach:

yaml
# ✅ Use GitHub Secrets
- name: Deploy to production
  env:
    API_KEY: ${{ secrets.PRODUCTION_API_KEY }}
    AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY }}
  run: |
    ./deploy.sh

Setting secrets:

  1. Repo Settings → Secrets and variables → Actions
  2. New repository secret
  3. Name: PRODUCTION_API_KEY, Value: sk-...

Timeline:

  • Pre-2022: Some teams committed .env files
  • 2022+: GitHub secret scanning blocks commits with keys
  • 2024: OIDC eliminates need for long-lived credentials

Anti-Pattern 4: No Failure Notifications

Problem: CI fails silently, team doesn't notice for hours.

Correct approach:

yaml
# ✅ Slack notification on failure
- name: Notify on failure
  if: failure()
  uses: slackapi/slack-github-action@v1
  with:
    payload: |
      {
        "text": "❌ Build failed: ${{ github.event.head_commit.message }}",
        "blocks": [
          {
            "type": "section",
            "text": {
              "type": "mrkdwn",
              "text": "*Build Failed*\n<${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}|View logs>"
            }
          }
        ]
      }
  env:
    SLACK_WEBHOOK_URL: ${{ secrets.SLACK_WEBHOOK }}

Anti-Pattern 5: Running All Tests on Every Commit

Problem: Slow feedback loop (10+ minute test suites).

Symptom: Developers avoid committing frequently.

Correct approach:

yaml
# ✅ Fast feedback: Run subset on PR, full suite on merge
on:
  pull_request:
    branches: [main]
  push:
    branches: [main]

jobs:
  quick-tests:
    if: github.event_name == 'pull_request'
    runs-on: ubuntu-latest
    steps:
      - run: npm run test:unit  # Fast: 2 minutes

  full-tests:
    if: github.event_name == 'push'
    runs-on: ubuntu-latest
    steps:
      - run: npm run test  # Slow: 10 minutes (unit + integration + e2e)

Alternative: Use changed-files action to run only affected tests.


Implementation Patterns

Pattern 1: Basic CI Pipeline
yaml
name: CI

on:
  push:
    branches: [main]
  pull_request:
    branches: [main]

jobs:
  test:
    runs-on: ubuntu-latest

    steps:
      - name: Checkout code
        uses: actions/checkout@v3

      - name: Setup Node.js
        uses: actions/setup-node@v3
        with:
          node-version: 18
          cache: 'npm'

      - name: Install dependencies
        run: npm ci

      - name: Run linter
        run: npm run lint

      - name: Run type check
        run: npm run typecheck

      - name: Run tests
        run: npm test

      - name: Build
        run: npm run build
Pattern 2: Multi-Environment Deployment
yaml
name: Deploy

on:
  push:
    branches:
      - main        # → staging
      - production  # → production

jobs:
  deploy:
    runs-on: ubuntu-latest
    environment: ${{ github.ref_name }}  # staging or production

    steps:
      - uses: actions/checkout@v3

      - name: Deploy to ${{ github.ref_name }}
        run: |
          if [ "${{ github.ref_name }}" == "production" ]; then
            ./deploy.sh production
          else
            ./deploy.sh staging
          fi
        env:
          API_KEY: ${{ secrets.API_KEY }}
          DATABASE_URL: ${{ secrets.DATABASE_URL }}
Pattern 3: Release Automation
yaml
name: Release

on:
  push:
    tags:
      - 'v*'  # Trigger on version tags (v1.0.0)

jobs:
  release:
    runs-on: ubuntu-latest
    permissions:
      contents: write  # Required for creating releases

    steps:
      - uses: actions/checkout@v3

      - name: Build artifacts
        run: npm run build

      - name: Create GitHub Release
        uses: softprops/action-gh-release@v1
        with:
          files: |
            dist/**
          body: |
            ## What's Changed
            See CHANGELOG.md for details.
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

      - name: Publish to npm
        run: npm publish
        env:
          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
Pattern 4: Docker Build & Push
yaml
name: Docker

on:
  push:
    branches: [main]

jobs:
  build-and-push:
    runs-on: ubuntu-latest

    steps:
      - uses: actions/checkout@v3

      - name: Set up Docker Buildx
        uses: docker/setup-buildx-action@v2

      - name: Login to DockerHub
        uses: docker/login-action@v2
        with:
          username: ${{ secrets.DOCKERHUB_USERNAME }}
          password: ${{ secrets.DOCKERHUB_TOKEN }}

      - name: Build and push
        uses: docker/build-push-action@v4
        with:
          context: .
          push: true
          tags: |
            myapp:latest
            myapp:${{ github.sha }}
          cache-from: type=gha
          cache-to: type=gha,mode=max

Production Checklist

□ Dependency caching configured
□ Matrix builds for multiple versions
□ Secrets stored in GitHub Secrets (not code)
□ Failure notifications (Slack, email, etc.)
□ Deploy previews for pull requests
□ Staging → Production promotion workflow
□ Release automation with versioning
□ Docker layer caching enabled
□ CODEOWNERS file for required reviews
□ Branch protection rules enabled
□ Status checks required before merge
□ Security scanning (Dependabot, CodeQL)

When to Use vs Avoid

ScenarioUse GitHub Actions?
GitHub-hosted repo✅ Yes
Need matrix builds✅ Yes
Deploying to AWS/GCP/Azure✅ Yes (with OIDC)
GitLab repo❌ No - use GitLab CI
Extremely large monorepo⚠️ Maybe - consider BuildKite
Need GUI pipeline builder❌ No - use Jenkins/Azure DevOps

References

  • /references/advanced-caching.md - Cache strategies for faster builds
  • /references/oidc-deployments.md - Keyless cloud authentication
  • /references/security-hardening.md - Security best practices

Scripts

  • scripts/workflow_validator.ts - Validate YAML syntax locally
  • scripts/action_usage_analyzer.ts - Find outdated actions

Assets

  • assets/workflows/ - Ready-to-use workflow templates

This skill guides: CI/CD pipelines | GitHub Actions workflows | Matrix builds | Caching | Deployments | Release automation

© curiositech, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (scripts, references, assets) in .claude/skills/github-actions-pipeline-builder of curiositech/some_claude_skills.

  • SKILL.md
  • .claude-plugin/plugin.json
  • assets/workflows/full-stack-ci-cd.yml
  • references/advanced-caching.md
  • scripts/action_usage_analyzer.ts
  • scripts/workflow_validator.ts

Open the folder on GitHubat commit 6713fc7

Compare with similar skills

GitHub Actions Pipeline Builder next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

GitHub Actions Pipeline Builder compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
GitHub Actions Pipeline Builder this skillcuriositech/some_claude_skills243—~2.8kAutomated safety check: NotesMIT
Migrate To TeamcityJetBrains/teamcity-cli125—~1.3kAutomated safety check: PassApache-2.0
Nushellccusage/ccusage19k—~938Automated safety check: PassCustom licence
AI News RadarLearnPrompt/ai-news-radar1.8k—~2.5kAutomated safety check: NotesMIT
Make GitHub Actions Workflowdotnet/efcore15k—~1.7kAutomated safety check: PassMIT
ONNX Runtime CI Managementmicrosoft/onnxruntime22k—~4.1kAutomated safety check: PassMIT

Similar skills

  • Migrate To Teamcity

    JetBrains/teamcity-cli

    Official

    Migrating CI/CD pipelines to TeamCity. An agent skill from JetBrains/teamcity-cli.

    125 GitHub stars~1.3k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Nushell

    ccusage/ccusage

    Guides ccusage Nushell scripts. An agent skill from ccusage/ccusage.

    19k GitHub stars~938 tokensUpdated today
    DevOps & CloudAuto-check passed
  • AI News Radar

    LearnPrompt/ai-news-radar

    A skill your agent uses when working on AI News Radar, 24 小时 AI 更新雷达, AI 更新雷达, 伯乐Skill, or Scout Skill: finding high-signal AI/tech sources, adding RSS/OPML/GitHub feeds, checking source health…

    1.8k GitHub stars~2.5k tokensUpdated today
    DevOps & CloudAuto-check: notes
  • Official

    Create GitHub Actions workflows for CI, automation, or PR management.

    15k GitHub stars~1.7k tokensUpdated today
    DevOps & CloudAuto-check passed
  • ONNX Runtime CI Management

    microsoft/onnxruntime

    Official

    Triggers, re-runs and unblocks the CI checks on an ONNX Runtime pull request, after diagnosing whether a failure is transient or needs a code change.

    22k GitHub stars~4.1k tokensUpdated today
    DevOps & CloudAuto-check passed
  • CI Watchdog

    latitude-dev/latitude-llm

    Continuously monitor GitHub PR CI checks and automatically fix failures until all checks pass.

    4.7k GitHub stars~1.6k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

More from curiositech/some_claude_skills

All 108 skills in this repo
  • Crisis Detection Intervention AI

    curiositech/some_claude_skills

    Detect crisis signals in user content using NLP, mental health sentiment analysis, and safe intervention protocols.

    243 GitHub starsUsed in 3 repos~3.8k tokens
    Auto-check passed
  • Form Validation Architect

    curiositech/some_claude_skills

    End-to-end form handling with react-hook-form, Zod schemas, validation patterns, error messaging, field arrays, and multi-step wizards.

    243 GitHub stars~3.8k tokensUpdated 1 mo ago
    Auto-check passed
  • Competitive Cartographer

    curiositech/some_claude_skills

    Strategic analyst that maps competitive landscapes, identifies white space opportunities, and provides positioning recommendations.

    243 GitHub starsUsed in 1 repo~1.3k tokens
    Auto-check passed
  • Computer Vision Pipeline

    curiositech/some_claude_skills

    Build production computer vision pipelines for object detection, tracking, and video analysis.

    243 GitHub starsUsed in 1 repo~4k tokens
    Auto-check passed
  • Design Archivist

    curiositech/some_claude_skills

    Long-running design anthropologist that builds comprehensive visual databases from 500-1000 real-world examples, extracting color palettes, typography patterns, layout systems, and interaction…

    243 GitHub starsUsed in 1 repo~1.6k tokens
    Auto-check passed
  • LLM Streaming Response Handler

    curiositech/some_claude_skills

    Build production LLM streaming UIs with Server-Sent Events, real-time token display, cancellation, error recovery.

    243 GitHub starsUsed in 1 repo~3.4k tokens
    Auto-check passed

Categories

Questions about GitHub Actions Pipeline Builder

What does GitHub Actions Pipeline Builder do?

Build production CI/CD pipelines with GitHub Actions. An agent skill from curiositech/some_claude_skills. GitHub Actions Pipeline Builder is an agent skill from curiositech/some_claude_skills. Build production CI/CD pipelines with GitHub Actions.

When should I use GitHub Actions Pipeline Builder?

GitHub Actions Pipeline Builder fits situations like: automated testing; release workflows.

How do I install GitHub Actions Pipeline Builder in Claude Code?

Run `npx skills add curiositech/some_claude_skills --skill github-actions-pipeline-builder -a claude-code`. Or copy the skill folder (.claude/skills/github-actions-pipeline-builder in curiositech/some_claude_skills) into .claude/skills/github-actions-pipeline-builder in your project. Claude Code loads it when a task matches its description.

How do I install GitHub Actions Pipeline Builder in Codex?

Run `npx skills add curiositech/some_claude_skills --skill github-actions-pipeline-builder -a codex`. Or copy the skill folder (.claude/skills/github-actions-pipeline-builder in curiositech/some_claude_skills) into .agents/skills/github-actions-pipeline-builder in your project. Codex loads it when a task matches its description.

Can I use GitHub Actions Pipeline Builder in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add curiositech/some_claude_skills --skill github-actions-pipeline-builder -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/github-actions-pipeline-builder, .gemini/skills/github-actions-pipeline-builder, .github/skills/github-actions-pipeline-builder and .opencode/skills/github-actions-pipeline-builder in your project.

What does GitHub Actions Pipeline Builder need to run?

Going by SKILL.md and its folder, GitHub Actions Pipeline Builder needs TypeScript for the scripts in its folder and credentials named PRODUCTION_API_KEY, API_KEY, GITHUB_TOKEN and AWS_ACCESS_KEY_ID. Our summary lists: Node.js; Docker; A credential in API_KEY; A credential in PRODUCTION_API_KEY. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash.

Does GitHub Actions Pipeline Builder access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is GitHub Actions Pipeline Builder safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file; pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does GitHub Actions Pipeline Builder use?

GitHub Actions Pipeline Builder is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does GitHub Actions Pipeline Builder use?

About 2.8k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.3k tokens, read only when the agent opens those files.

What are the alternatives to GitHub Actions Pipeline Builder?

Skills that share tags, products or a category with GitHub Actions Pipeline Builder: Migrate To Teamcity (JetBrains/teamcity-cli, 125 stars), Nushell (ccusage/ccusage, 19k stars), AI News Radar (LearnPrompt/ai-news-radar, 1.8k stars) and Make GitHub Actions Workflow (dotnet/efcore, 15k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains GitHub Actions Pipeline Builder?

curiositech (a GitHub organization) maintains it in curiositech/some_claude_skills, which has 243 GitHub stars. The repository holds 108 skills in this directory. The repository was last updated on September 6, 2026.

Source: curiositech/some_claude_skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.