Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Action Builder

ASecurity

Create custom GitHub Actions (composite, Docker, or JavaScript). Use when building reusable actions, creating custom workflow steps, or packaging logic for distribution. Trigger words include "create action", "custom action", "build action", "composite action", "Docker action".

29 stars
0 votes
0 copies
8 views
Added 12/21/2025
devopsjavascriptjavashellbashnodedockerawsgitapidocumentation

Works with

api

Security Analysis

A100/100

Pro scans all 4 files and shows the line behind each finding

Scanned 2/12/2026

$npx -y skills add armanzeroeight/fastagent-plugins --skill action-builder --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Action Builder?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Action Builder
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/armanzeroeight-action-builder/badge)](https://www.skillsdirectory.com/skills/armanzeroeight-action-builder)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: action-builder
description: Create custom GitHub Actions (composite, Docker, or JavaScript). Use when building reusable actions, creating custom workflow steps, or packaging logic for distribution. Trigger words include "create action", "custom action", "build action", "composite action", "Docker action".
---

# Action Builder

Build custom GitHub Actions for reusable workflow logic.

## Quick Start

Choose action type based on requirements:
- **Composite**: Combine multiple workflow steps (simplest, no code)
- **Docker**: Run containerized logic (any language, slower startup)
- **JavaScript**: Fast execution, Node.js required

## Instructions

### Step 1: Choose Action Type

**Use Composite when:**
- Combining existing actions and shell commands
- No custom code needed
- Fast execution required
- Example: Setup environment with multiple tools

**Use Docker when:**
- Need specific runtime environment
- Using non-JavaScript languages
- Complex dependencies
- Example: Custom linting tool, data processing

**Use JavaScript when:**
- Need programmatic control
- Fast startup time critical
- Interacting with GitHub API
- Example: Issue labeler, PR validator

### Step 2: Create Action Structure

**All action types need:**
```
action-name/
├── action.yml          # Action metadata
├── README.md           # Documentation
└── [implementation]    # Type-specific files
```

### Step 3: Define action.yml

**Required fields:**
```yaml
name: 'Action Name'
description: 'What the action does'
author: 'Your Name'

inputs:
  input-name:
    description: 'Input description'
    required: true
    default: 'default-value'

outputs:
  output-name:
    description: 'Output description'
    value: ${{ steps.step-id.outputs.output-name }}

runs:
  using: 'composite|docker|node16'
  # Type-specific configuration
```

### Step 4: Implement Action Logic

**For Composite Actions:**
```yaml
runs:
  using: 'composite'
  steps:
    - name: Step name
      run: echo "Command"
      shell: bash
    - uses: actions/checkout@v3
```

**For Docker Actions:**
```yaml
runs:
  using: 'docker'
  image: 'Dockerfile'
  args:
    - ${{ inputs.input-name }}
```

**For JavaScript Actions:**
```yaml
runs:
  using: 'node16'
  main: 'dist/index.js'
```

### Step 5: Test Action Locally

**Test in workflow:**
```yaml
jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - uses: ./  # Test local action
        with:
          input-name: 'test-value'
```

### Step 6: Version and Publish

**Versioning:**
- Use semantic versioning (v1.0.0)
- Create Git tags for releases
- Maintain major version tags (v1, v2)

**Publishing:**
- Push to GitHub repository
- Create release with tag
- Add to GitHub Marketplace (optional)

## Common Patterns

### Input Validation

```yaml
inputs:
  environment:
    description: 'Deployment environment'
    required: true
  region:
    description: 'AWS region'
    required: false
    default: 'us-east-1'
```

### Output Setting

**Composite:**
```bash
echo "output-name=value" >> $GITHUB_OUTPUT
```

**JavaScript:**
```javascript
core.setOutput('output-name', 'value');
```

### Error Handling

**Composite:**
```bash
if [ $? -ne 0 ]; then
  echo "::error::Operation failed"
  exit 1
fi
```

**JavaScript:**
```javascript
try {
  // Action logic
} catch (error) {
  core.setFailed(error.message);
}
```

## Advanced

For detailed implementation guides:
- [Composite Actions](reference/composite-actions.md) - Multi-step workflows
- [Docker Actions](reference/docker-actions.md) - Containerized actions
- [Inputs and Outputs](reference/inputs-outputs.md) - Data handling patterns

## Troubleshooting

**Action not found:**
- Verify action.yml exists in repository root
- Check action path in workflow (uses: owner/repo@version)

**Inputs not working:**
- Confirm input names match action.yml
- Check required vs. optional inputs
- Verify default values

**Outputs not available:**
- Ensure output is set before job completes
- Check step ID matches output reference
- Verify output syntax (${{ steps.id.outputs.name }})

Attribution

armanzeroeightarmanzeroeight
View sourceSee grades on GitHubMore from armanzeroeight →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Terraform Module Library

Build reusable Terraform modules for AWS, Azure, and GCP infrastructure following infrastructure-as-code best practices. Use when creating infrastructure modules, standardizing cloud provisioning, or implementing reusable IaC components.

401991 votes

sematext-otel

Wire a service's OpenTelemetry output to Sematext Cloud. Walks through region, App-type, instrumentation flow (managed OTLP endpoint vs Sematext Agent), and signal selection (traces/metrics/logs), then produces the exact env-var block and points at a runnable reference example in this repo. Invoke when instrumenting a new app for Sematext.

01 votes

Deployment Patterns

Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.

2699140 votes

Babysit

Watch a pull request or review cycle until it is ready to merge. Use when asked to babysit, monitor, or keep checking PR comments, reviews, and CI until all actionable issues are resolved.

971540 votes

V7 Roster

Interact with the Paperclip control plane API for task coordination and governance. Use when checking assignments, updating issue status, posting comments, delegating work, managing routines, or calling Paperclip API endpoints.

953190 votes
View all in devops →