[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EMW4DP4FWR8K2FW6071GQA":3,"skill-same:01M7EMW4DP4FWR8K2FW6071GQA":52},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7EMW4DP4FWR8K2FW6071GQA","github-actions-creator",null,"Use when the user wants to create, generate, or set up a GitHub Actions workflow. Handles CI\u002FCD pipelines, testing, deployment, linting, security scanning, release automation, Docker builds, scheduled tasks, and any custom workflow for any language or framework.","marnixGeerkens\u002Frocketlauncher-claude-code","marnixGeerkens","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F143275741?v=4","01M7EJY825SFPHDDZNFDAJHCA9","Marnix Geerkens","01M7EJY82TBA6ABXJ62JWR9B9F",0,"MIT","https:\u002F\u002Fgithub.com\u002FmarnixGeerkens\u002Frocketlauncher-claude-code\u002Fblob\u002Fmain\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fgithub-actions-creator\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: github-actions-creator\ndescription: \"Use when the user wants to create, generate, or set up a GitHub Actions workflow. Handles CI\u002FCD pipelines, testing, deployment, linting, security scanning, release automation, Docker builds, scheduled tasks, and any custom workflow for any language or framework.\"\n---\n\n# GitHub Actions Creator\n\nYou are an expert at creating GitHub Actions workflows. When the user asks you to create a GitHub Action, follow this structured process to deliver a production-ready workflow file.\n\n## Workflow Creation Process\n\n### Step 1: Analyze the Project\n\nBefore writing any YAML, scan the project to understand the stack:\n\n1. **Check for language\u002Fframework indicators:**\n   - `package.json` → Node.js (check for React, Next.js, Vue, Angular, Svelte, etc.)\n   - `requirements.txt` \u002F `pyproject.toml` \u002F `setup.py` → Python\n   - `go.mod` → Go\n   - `Cargo.toml` → Rust\n   - `pom.xml` \u002F `build.gradle` → Java\u002FKotlin\n   - `Gemfile` → Ruby\n   - `composer.json` → PHP\n   - `pubspec.yaml` → Dart\u002FFlutter\n   - `Package.swift` → Swift\n   - `*.csproj` \u002F `*.sln` → .NET\n\n2. **Check for existing CI\u002FCD:**\n   - `.github\u002Fworkflows\u002F` → existing workflows (avoid conflicts)\n   - `Dockerfile` → container builds available\n   - `docker-compose.yml` → multi-service setup\n   - `vercel.json` \u002F `netlify.toml` → deployment targets\n   - `terraform\u002F` \u002F `pulumi\u002F` → infrastructure as code\n\n3. **Check for tooling:**\n   - `.eslintrc*` \u002F `eslint.config.*` → ESLint configured\n   - `prettier*` → Prettier configured\n   - `jest.config*` \u002F `vitest.config*` \u002F `pytest.ini` → test framework\n   - `.env.example` → environment variables needed\n   - `Makefile` → build commands available\n\n### Step 2: Ask Clarifying Questions (if needed)\n\nIf the user's request is ambiguous, ask ONE focused question. Common clarifications:\n\n- **\"Create a CI pipeline\"** → \"Should it run tests only, or also lint and type-check?\"\n- **\"Add deployment\"** → \"Where does this deploy? (Vercel, AWS, GCP, Docker Hub, etc.)\"\n- **\"Set up tests\"** → \"Should tests run on PR only, or also on push to main?\"\n\nIf the intent is clear, skip this step and proceed.\n\n### Step 3: Generate the Workflow\n\nCreate the `.github\u002Fworkflows\u002F{name}.yml` file following these rules:\n\n#### File Naming\n- Use descriptive kebab-case names: `ci.yml`, `deploy-production.yml`, `release.yml`\n- For simple CI: `ci.yml`\n- For deployment: `deploy.yml` or `deploy-{target}.yml`\n- For scheduled tasks: `scheduled-{task}.yml`\n\n#### YAML Structure Rules\n\n```yaml\nname: Human-readable name        # Always include\n\non:                               # Use the most specific triggers\n  push:\n    branches: [main]              # Specify branches explicitly\n    paths-ignore:                 # Skip docs-only changes when appropriate\n      - '**.md'\n      - 'docs\u002F**'\n  pull_request:\n    branches: [main]\n\npermissions:                      # Always set minimal permissions\n  contents: read\n\nconcurrency:                      # Prevent duplicate runs on PRs\n  group: ${{ github.workflow }}-${{ github.ref }}\n  cancel-in-progress: true\n\njobs:\n  job-name:\n    runs-on: ubuntu-latest        # Default to ubuntu-latest\n    timeout-minutes: 15           # Always set a timeout\n    steps:\n      - uses: actions\u002Fcheckout@v4 # Always pin to major version\n```\n\n## Core Patterns by Use Case\n\n### CI (Test + Lint)\n\n**Trigger:** `pull_request` + `push` to main\n**Jobs:** lint, test (parallel when possible)\n**Key features:** dependency caching, matrix testing for multiple versions\n\n### Deployment\n\n**Trigger:** `push` to main (or release tags)\n**Jobs:** test → build → deploy (sequential with `needs`)\n**Key features:** environment protection, secrets for credentials, status checks\n\n### Release \u002F Publish\n\n**Trigger:** `push` tags matching `v*` or `workflow_dispatch`\n**Jobs:** test → build → publish → create GitHub Release\n**Key features:** changelog generation, artifact upload, npm\u002FPyPI\u002FDocker publish\n\n### Scheduled Tasks\n\n**Trigger:** `schedule` with cron expression\n**Jobs:** single job with the task\n**Key features:** `workflow_dispatch` for manual trigger too, failure notifications\n\n### Security Scanning\n\n**Trigger:** `pull_request` + `schedule` (weekly)\n**Jobs:** dependency audit, SAST, secret scanning\n**Key features:** SARIF upload to GitHub Security tab, fail on critical\n\n### Docker Build & Push\n\n**Trigger:** `push` to main + tags\n**Jobs:** build → push to registry\n**Key features:** multi-platform builds, layer caching, image tagging strategy\n\n## Essential Actions Reference\n\n### Setup Actions (always pin to major version)\n| Action | Purpose |\n|--------|---------|\n| `actions\u002Fcheckout@v4` | Clone repository |\n| `actions\u002Fsetup-node@v4` | Node.js with caching |\n| `actions\u002Fsetup-python@v5` | Python with caching |\n| `actions\u002Fsetup-go@v5` | Go with caching |\n| `actions\u002Fsetup-java@v4` | Java\u002FKotlin |\n| `dtolnay\u002Frust-toolchain@stable` | Rust toolchain |\n| `ruby\u002Fsetup-ruby@v1` | Ruby with bundler cache |\n| `actions\u002Fsetup-dotnet@v4` | .NET SDK |\n\n### Build & Deploy Actions\n| Action | Purpose |\n|--------|---------|\n| `docker\u002Fbuild-push-action@v6` | Docker multi-platform builds |\n| `docker\u002Flogin-action@v3` | Docker registry authentication |\n| `aws-actions\u002Fconfigure-aws-credentials@v4` | AWS authentication |\n| `google-github-actions\u002Fauth@v2` | GCP authentication |\n| `azure\u002Flogin@v2` | Azure authentication |\n| `cloudflare\u002Fwrangler-action@v3` | Cloudflare Workers deploy |\n| `amondnet\u002Fvercel-action@v25` | Vercel deployment |\n\n### Quality & Security Actions\n| Action | Purpose |\n|--------|---------|\n| `github\u002Fcodeql-action\u002Fanalyze@v3` | CodeQL SAST scanning |\n| `aquasecurity\u002Ftrivy-action@master` | Container vulnerability scan |\n| `codecov\u002Fcodecov-action@v4` | Coverage upload |\n| `actions\u002Fdependency-review-action@v4` | Dependency audit on PRs |\n\n### Utility Actions\n| Action | Purpose |\n|--------|---------|\n| `actions\u002Fcache@v4` | Generic caching |\n| `actions\u002Fupload-artifact@v4` | Store build artifacts |\n| `actions\u002Fdownload-artifact@v4` | Retrieve artifacts between jobs |\n| `softprops\u002Faction-gh-release@v2` | Create GitHub Releases |\n| `slackapi\u002Fslack-github-action@v2` | Slack notifications |\n| `peter-evans\u002Fcreate-pull-request@v7` | Automated PR creation |\n\n## Security Best Practices (ALWAYS follow)\n\n1. **Minimal permissions:** Always declare `permissions` at workflow or job level\n2. **Pin actions to major version:** Use `@v4` not `@main` or full SHA for readability\n3. **Never echo secrets:** Secrets are masked but avoid `echo ${{ secrets.X }}`\n4. **Use environments:** For production deploys, use GitHub Environments with protection rules\n5. **Validate inputs:** For `workflow_dispatch`, validate input values\n6. **Avoid script injection:** Never use `${{ github.event.*.body }}` directly in `run:` — pass via environment variables\n7. **Use GITHUB_TOKEN:** Prefer `${{ secrets.GITHUB_TOKEN }}` over PATs when possible\n8. **Concurrency controls:** Use `concurrency` to prevent parallel deploys\n\n```yaml\n# WRONG - script injection vulnerability\n- run: echo \"${{ github.event.issue.title }}\"\n\n# CORRECT - pass through environment variable\n- run: echo \"$ISSUE_TITLE\"\n  env:\n    ISSUE_TITLE: ${{ github.event.issue.title }}\n```\n\n## Caching Strategies\n\n### Node.js\n```yaml\n- uses: actions\u002Fsetup-node@v4\n  with:\n    node-version: 20\n    cache: 'npm'  # or 'yarn' or 'pnpm'\n```\n\n### Python\n```yaml\n- uses: actions\u002Fsetup-python@v5\n  with:\n    python-version: '3.12'\n    cache: 'pip'  # or 'poetry' or 'pipenv'\n```\n\n### Go\n```yaml\n- uses: actions\u002Fsetup-go@v5\n  with:\n    go-version: '1.22'\n    cache: true\n```\n\n### Rust\n```yaml\n- uses: actions\u002Fcache@v4\n  with:\n    path: |\n      ~\u002F.cargo\u002Fbin\u002F\n      ~\u002F.cargo\u002Fregistry\u002Findex\u002F\n      ~\u002F.cargo\u002Fregistry\u002Fcache\u002F\n      target\u002F\n    key: ${{ runner.os }}-cargo-${{ hashFiles('**\u002FCargo.lock') }}\n```\n\n### Docker\n```yaml\n- uses: docker\u002Fbuild-push-action@v6\n  with:\n    cache-from: type=gha\n    cache-to: type=gha,mode=max\n```\n\n## Matrix Testing Patterns\n\n### Multiple Node.js versions\n```yaml\nstrategy:\n  matrix:\n    node-version: [18, 20, 22]\n  fail-fast: false\n```\n\n### Multiple OS\n```yaml\nstrategy:\n  matrix:\n    os: [ubuntu-latest, macos-latest, windows-latest]\nruns-on: ${{ matrix.os }}\n```\n\n### Complex matrix with exclusions\n```yaml\nstrategy:\n  matrix:\n    os: [ubuntu-latest, windows-latest]\n    node-version: [18, 20]\n    exclude:\n      - os: windows-latest\n        node-version: 18\n```\n\n## Cron Syntax Quick Reference\n\n| Schedule | Cron |\n|----------|------|\n| Every hour | `0 * * * *` |\n| Daily at midnight UTC | `0 0 * * *` |\n| Weekdays at 9am UTC | `0 9 * * 1-5` |\n| Weekly on Sunday | `0 0 * * 0` |\n| Monthly 1st | `0 0 1 * *` |\n\n## Output Format\n\nAfter creating the workflow file, provide:\n\n1. **What the workflow does** — one-paragraph summary\n2. **Required secrets** — list any secrets the user needs to configure in Settings > Secrets\n3. **Required permissions** — if the workflow needs non-default repository permissions\n4. **How to test** — how to trigger the workflow (push, create PR, manual dispatch)\n\n## Common Patterns to Combine\n\nWhen the user asks for something generic like \"set up CI\u002FCD\", create a single workflow with multiple jobs:\n\n```yaml\njobs:\n  lint:        # Fast feedback\n  test:        # Core validation\n  build:       # Ensure it compiles\u002Fbundles\n    needs: [lint, test]\n  deploy:      # Only after everything passes\n    needs: build\n    if: github.ref == 'refs\u002Fheads\u002Fmain'\n```\n\nKeep workflows focused. Prefer one workflow per concern over one massive workflow, unless the jobs are tightly coupled.\n","# GitHub Actions Creator\n\nYou are an expert at creating GitHub Actions workflows. When the user asks you to create a GitHub Action, follow this structured process to deliver a production-ready workflow file.\n\n## Workflow Creation Process\n\n### Step 1: Analyze the Project\n\nBefore writing any YAML, scan the project to understand the stack:\n\n1. **Check for language\u002Fframework indicators:**\n   - `package.json` → Node.js (check for React, Next.js, Vue, Angular, Svelte, etc.)\n   - `requirements.txt` \u002F `pyproject.toml` \u002F `setup.py` → Python\n   - `go.mod` → Go\n   - `Cargo.toml` → Rust\n   - `pom.xml` \u002F `build.gradle` → Java\u002FKotlin\n   - `Gemfile` → Ruby\n   - `composer.json` → PHP\n   - `pubspec.yaml` → Dart\u002FFlutter\n   - `Package.swift` → Swift\n   - `*.csproj` \u002F `*.sln` → .NET\n\n2. **Check for existing CI\u002FCD:**\n   - `.github\u002Fworkflows\u002F` → existing workflows (avoid conflicts)\n   - `Dockerfile` → container builds available\n   - `docker-compose.yml` → multi-service setup\n   - `vercel.json` \u002F `netlify.toml` → deployment targets\n   - `terraform\u002F` \u002F `pulumi\u002F` → infrastructure as code\n\n3. **Check for tooling:**\n   - `.eslintrc*` \u002F `eslint.config.*` → ESLint configured\n   - `prettier*` → Prettier configured\n   - `jest.config*` \u002F `vitest.config*` \u002F `pytest.ini` → test framework\n   - `.env.example` → environment variables needed\n   - `Makefile` → build commands available\n\n### Step 2: Ask Clarifying Questions (if needed)\n\nIf the user's request is ambiguous, ask ONE focused question. Common clarifications:\n\n- **\"Create a CI pipeline\"** → \"Should it run tests only, or also lint and type-check?\"\n- **\"Add deployment\"** → \"Where does this deploy? (Vercel, AWS, GCP, Docker Hub, etc.)\"\n- **\"Set up tests\"** → \"Should tests run on PR only, or also on push to main?\"\n\nIf the intent is clear, skip this step and proceed.\n\n### Step 3: Generate the Workflow\n\nCreate the `.github\u002Fworkflows\u002F{name}.yml` file following these rules:\n\n#### File Naming\n- Use descriptive kebab-case names: `ci.yml`, `deploy-production.yml`, `release.yml`\n- For simple CI: `ci.yml`\n- For deployment: `deploy.yml` or `deploy-{target}.yml`\n- For scheduled tasks: `scheduled-{task}.yml`\n\n#### YAML Structure Rules\n\n```yaml\nname: Human-readable name        # Always include\n\non:                               # Use the most specific triggers\n  push:\n    branches: [main]              # Specify branches explicitly\n    paths-ignore:                 # Skip docs-only changes when appropriate\n      - '**.md'\n      - 'docs\u002F**'\n  pull_request:\n    branches: [main]\n\npermissions:                      # Always set minimal permissions\n  contents: read\n\nconcurrency:                      # Prevent duplicate runs on PRs\n  group: ${{ github.workflow }}-${{ github.ref }}\n  cancel-in-progress: true\n\njobs:\n  job-name:\n    runs-on: ubuntu-latest        # Default to ubuntu-latest\n    timeout-minutes: 15           # Always set a timeout\n    steps:\n      - uses: actions\u002Fcheckout@v4 # Always pin to major version\n```\n\n## Core Patterns by Use Case\n\n### CI (Test + Lint)\n\n**Trigger:** `pull_request` + `push` to main\n**Jobs:** lint, test (parallel when possible)\n**Key features:** dependency caching, matrix testing for multiple versions\n\n### Deployment\n\n**Trigger:** `push` to main (or release tags)\n**Jobs:** test → build → deploy (sequential with `needs`)\n**Key features:** environment protection, secrets for credentials, status checks\n\n### Release \u002F Publish\n\n**Trigger:** `push` tags matching `v*` or `workflow_dispatch`\n**Jobs:** test → build → publish → create GitHub Release\n**Key features:** changelog generation, artifact upload, npm\u002FPyPI\u002FDocker publish\n\n### Scheduled Tasks\n\n**Trigger:** `schedule` with cron expression\n**Jobs:** single job with the task\n**Key features:** `workflow_dispatch` for manual trigger too, failure notifications\n\n### Security Scanning\n\n**Trigger:** `pull_request` + `schedule` (weekly)\n**Jobs:** dependency audit, SAST, secret scanning\n**Key features:** SARIF upload to GitHub Security tab, fail on critical\n\n### Docker Build & Push\n\n**Trigger:** `push` to main + tags\n**Jobs:** build → push to registry\n**Key features:** multi-platform builds, layer caching, image tagging strategy\n\n## Essential Actions Reference\n\n### Setup Actions (always pin to major version)\n| Action | Purpose |\n|--------|---------|\n| `actions\u002Fcheckout@v4` | Clone repository |\n| `actions\u002Fsetup-node@v4` | Node.js with caching |\n| `actions\u002Fsetup-python@v5` | Python with caching |\n| `actions\u002Fsetup-go@v5` | Go with caching |\n| `actions\u002Fsetup-java@v4` | Java\u002FKotlin |\n| `dtolnay\u002Frust-toolchain@stable` | Rust toolchain |\n| `ruby\u002Fsetup-ruby@v1` | Ruby with bundler cache |\n| `actions\u002Fsetup-dotnet@v4` | .NET SDK |\n\n### Build & Deploy Actions\n| Action | Purpose |\n|--------|---------|\n| `docker\u002Fbuild-push-action@v6` | Docker multi-platform builds |\n| `docker\u002Flogin-action@v3` | Docker registry authentication |\n| `aws-actions\u002Fconfigure-aws-credentials@v4` | AWS authentication |\n| `google-github-actions\u002Fauth@v2` | GCP authentication |\n| `azure\u002Flogin@v2` | Azure authentication |\n| `cloudflare\u002Fwrangler-action@v3` | Cloudflare Workers deploy |\n| `amondnet\u002Fvercel-action@v25` | Vercel deployment |\n\n### Quality & Security Actions\n| Action | Purpose |\n|--------|---------|\n| `github\u002Fcodeql-action\u002Fanalyze@v3` | CodeQL SAST scanning |\n| `aquasecurity\u002Ftrivy-action@master` | Container vulnerability scan |\n| `codecov\u002Fcodecov-action@v4` | Coverage upload |\n| `actions\u002Fdependency-review-action@v4` | Dependency audit on PRs |\n\n### Utility Actions\n| Action | Purpose |\n|--------|---------|\n| `actions\u002Fcache@v4` | Generic caching |\n| `actions\u002Fupload-artifact@v4` | Store build artifacts |\n| `actions\u002Fdownload-artifact@v4` | Retrieve artifacts between jobs |\n| `softprops\u002Faction-gh-release@v2` | Create GitHub Releases |\n| `slackapi\u002Fslack-github-action@v2` | Slack notifications |\n| `peter-evans\u002Fcreate-pull-request@v7` | Automated PR creation |\n\n## Security Best Practices (ALWAYS follow)\n\n1. **Minimal permissions:** Always declare `permissions` at workflow or job level\n2. **Pin actions to major version:** Use `@v4` not `@main` or full SHA for readability\n3. **Never echo secrets:** Secrets are masked but avoid `echo ${{ secrets.X }}`\n4. **Use environments:** For production deploys, use GitHub Environments with protection rules\n5. **Validate inputs:** For `workflow_dispatch`, validate input values\n6. **Avoid script injection:** Never use `${{ github.event.*.body }}` directly in `run:` — pass via environment variables\n7. **Use GITHUB_TOKEN:** Prefer `${{ secrets.GITHUB_TOKEN }}` over PATs when possible\n8. **Concurrency controls:** Use `concurrency` to prevent parallel deploys\n\n```yaml\n# WRONG - script injection vulnerability\n- run: echo \"${{ github.event.issue.title }}\"\n\n# CORRECT - pass through environment variable\n- run: echo \"$ISSUE_TITLE\"\n  env:\n    ISSUE_TITLE: ${{ github.event.issue.title }}\n```\n\n## Caching Strategies\n\n### Node.js\n```yaml\n- uses: actions\u002Fsetup-node@v4\n  with:\n    node-version: 20\n    cache: 'npm'  # or 'yarn' or 'pnpm'\n```\n\n### Python\n```yaml\n- uses: actions\u002Fsetup-python@v5\n  with:\n    python-version: '3.12'\n    cache: 'pip'  # or 'poetry' or 'pipenv'\n```\n\n### Go\n```yaml\n- uses: actions\u002Fsetup-go@v5\n  with:\n    go-version: '1.22'\n    cache: true\n```\n\n### Rust\n```yaml\n- uses: actions\u002Fcache@v4\n  with:\n    path: |\n      ~\u002F.cargo\u002Fbin\u002F\n      ~\u002F.cargo\u002Fregistry\u002Findex\u002F\n      ~\u002F.cargo\u002Fregistry\u002Fcache\u002F\n      target\u002F\n    key: ${{ runner.os }}-cargo-${{ hashFiles('**\u002FCargo.lock') }}\n```\n\n### Docker\n```yaml\n- uses: docker\u002Fbuild-push-action@v6\n  with:\n    cache-from: type=gha\n    cache-to: type=gha,mode=max\n```\n\n## Matrix Testing Patterns\n\n### Multiple Node.js versions\n```yaml\nstrategy:\n  matrix:\n    node-version: [18, 20, 22]\n  fail-fast: false\n```\n\n### Multiple OS\n```yaml\nstrategy:\n  matrix:\n    os: [ubuntu-latest, macos-latest, windows-latest]\nruns-on: ${{ matrix.os }}\n```\n\n### Complex matrix with exclusions\n```yaml\nstrategy:\n  matrix:\n    os: [ubuntu-latest, windows-latest]\n    node-version: [18, 20]\n    exclude:\n      - os: windows-latest\n        node-version: 18\n```\n\n## Cron Syntax Quick Reference\n\n| Schedule | Cron |\n|----------|------|\n| Every hour | `0 * * * *` |\n| Daily at midnight UTC | `0 0 * * *` |\n| Weekdays at 9am UTC | `0 9 * * 1-5` |\n| Weekly on Sunday | `0 0 * * 0` |\n| Monthly 1st | `0 0 1 * *` |\n\n## Output Format\n\nAfter creating the workflow file, provide:\n\n1. **What the workflow does** — one-paragraph summary\n2. **Required secrets** — list any secrets the user needs to configure in Settings > Secrets\n3. **Required permissions** — if the workflow needs non-default repository permissions\n4. **How to test** — how to trigger the workflow (push, create PR, manual dispatch)\n\n## Common Patterns to Combine\n\nWhen the user asks for something generic like \"set up CI\u002FCD\", create a single workflow with multiple jobs:\n\n```yaml\njobs:\n  lint:        # Fast feedback\n  test:        # Core validation\n  build:       # Ensure it compiles\u002Fbundles\n    needs: [lint, test]\n  deploy:      # Only after everything passes\n    needs: build\n    if: github.ref == 'refs\u002Fheads\u002Fmain'\n```\n\nKeep workflows focused. Prefer one workflow per concern over one massive workflow, unless the jobs are tightly coupled.\n",{"name":5,"description":7},"main","4e647b68aabe849e143b6950971c380f7adccdef","components\u002Fskills\u002Fdevelopment\u002Fgithub-actions-creator","https:\u002F\u002Fgithub.com\u002FmarnixGeerkens\u002Frocketlauncher-claude-code","https:\u002F\u002Frocketlauncher.ai\u002Fclaude-code","https:\u002F\u002Fgithub.com\u002FmarnixGeerkens","CEO of Rocketlauncher.ai\r\n\r\nObsessed with AI\r\n\r\njoin  https:\u002F\u002Fwww.skool.com\u002Frocketlauncher-university\r\n👉🏻 it's free ","2026-10-13 00:52:14",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add marnixGeerkens\u002Frocketlauncher-claude-code --skill github-actions-creator",{"tool":38,"command":39},"bunx","bunx skills add marnixGeerkens\u002Frocketlauncher-claude-code --skill github-actions-creator",{"tool":41,"command":42},"pnpm","pnpm dlx skills add marnixGeerkens\u002Frocketlauncher-claude-code --skill github-actions-creator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FmarnixGeerkens\u002Frocketlauncher-claude-code\u002Fblob\u002Fmain\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fgithub-actions-creator\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fworkflow-templates.md","REFERENCE","参考文档",17875,"https:\u002F\u002Fgithub.com\u002FmarnixGeerkens\u002Frocketlauncher-claude-code\u002Fblob\u002Fmain\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fgithub-actions-creator\u002Freferences\u002Fworkflow-templates.md",[53,60,69,76,83,90],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7EQFDF4T3K89WMFVFQVT3C8","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points.  This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power","https:\u002F\u002Fgithub.com\u002FmarnixGeerkens\u002Frocketlauncher-claude-code\u002Fblob\u002Fmain\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fzapier-make-patterns\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":64,"licenseFileUrl":65,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7EQFA5XQ0811Q4Q0WCFASZG","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002FmarnixGeerkens\u002Frocketlauncher-claude-code\u002Fblob\u002Fmain\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FmarnixGeerkens\u002Frocketlauncher-claude-code\u002Fblob\u002Fmain\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7EQF4J6C2WKQWD9E2RQC6MJ","workflow-automation","Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, workflows resume exactly where they left off.  This skill covers the platforms (n8n, Temporal, Inngest) and patterns (sequential, parallel, orchestrator-worker) that turn brittle scripts into production-grade automation.  Key insight: The platforms make different tradeoffs. n8n optimizes for accessibility","https:\u002F\u002Fgithub.com\u002FmarnixGeerkens\u002Frocketlauncher-claude-code\u002Fblob\u002Fmain\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fworkflow-automation\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7EQF1AT655CYYZBEQ8V6Z9D","trigger-dev","Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design. Use when: trigger.dev, trigger dev, background task, ai background job, long running task.","https:\u002F\u002Fgithub.com\u002FmarnixGeerkens\u002Frocketlauncher-claude-code\u002Fblob\u002Fmain\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Ftrigger-dev\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7EQEY9ENH0G2EJ1WD6C1CE8","slack-automation","Automate Slack workspace operations including messaging, search, channel management, and reaction workflows through Composio's Slack toolkit.","https:\u002F\u002Fgithub.com\u002FmarnixGeerkens\u002Frocketlauncher-claude-code\u002Fblob\u002Fmain\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fslack-automation\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":64,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M7EQESHEKPTE0QPW9R6XV5K2","rote","Compile a proven agent skill (a SKILL.md plus references) into a deterministic pipeline that runs without an LLM in the loop, then serve it back to Claude as an MCP tool. Use when: rote, compile this skill, turn this skill into a workflow, make this skill deterministic, make this skill cheaper or faster, harden this skill for production, run this skill as a background job.","https:\u002F\u002Fgithub.com\u002FmarnixGeerkens\u002Frocketlauncher-claude-code\u002Fblob\u002Fmain\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Frote\u002FSKILL.md",[],[]]