[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72C0CDY15DQWGXBYHJ8DXF3":3,"skill-same:01M72C0CDY15DQWGXBYHJ8DXF3":53},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M72C0CDY15DQWGXBYHJ8DXF3","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.","Sansar35\u002Fclaude-agent","Sansar35","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F145020281?v=4","01M724CQ2SCC86MGNSD87D0D4K","01M724CQ3965G9WJ3QXE3AJ5YY",1,"MIT","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fgithub-actions-creator\u002FSKILL.md",[],[],"2026-11-10 18:39:20",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","d046d088ce5a79a083f0abc0fe1b7ded73bc5b1f","claude-config\u002Fskills\u002Fgithub-actions-creator","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent","https:\u002F\u002Fgithub.com\u002FSansar35","2026-05-10 16:04:53",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add Sansar35\u002Fclaude-agent --skill github-actions-creator",{"tool":35,"command":36},"bunx","bunx skills add Sansar35\u002Fclaude-agent --skill github-actions-creator",{"tool":38,"command":39},"pnpm","pnpm dlx skills add Sansar35\u002Fclaude-agent --skill github-actions-creator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fgithub-actions-creator\u002FSKILL.md",true,[43,49],{"path":44,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":47,"sourceHtmlUrl":48},".skill-source.json","REFERENCE","参考文档",507,"https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fgithub-actions-creator\u002F.skill-source.json",{"path":50,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fworkflow-templates.md",17875,"https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fgithub-actions-creator\u002Freferences\u002Fworkflow-templates.md",[54,61,68,75,82,90],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M72DVAN1JYEA302MT0C5MGD6","zustand-store-ts","Create Zustand stores following established patterns with proper TypeScript types and middleware.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M72DV8J5NBRRM4RPDFRV95N7","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M72DV5EMHW0BHP9BZ167MDCB","zinc-database","Access ZINC (230M+ purchasable compounds). Search by ZINC ID\u002FSMILES, similarity searches, 3D-ready structures for docking, analog discovery, for virtual screening and drug discovery.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzinc-database\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M72DV216QY0E693ZPEVQ0DBS","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":86,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":18},"01M72DTXQREMCRKA8NHCVKHN4W","zapier-workflows","Manage and trigger pre-built Zapier workflows and MCP tool orchestration. Use when user mentions workflows, Zaps, automations, daily digest, research, search, lead tracking, expenses, or asks to \"run\" any process. Also handles Perplexity-based research and Google Sheets data tracking.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-workflows\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-workflows\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":18},"01M72DTT17TBSJ0Y8J2XZ4C9TZ","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\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-make-patterns\u002FSKILL.md",[],[]]