action-builder
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".
What this skill does
# 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 }})
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.