[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AMRE4TWECTCH04KB73EQFM":3,"skill-same:01M7AMRE4TWECTCH04KB73EQFM":51},{"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":30,"commitSha":31,"skillDirectory":32,"forksCount":14,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":6,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M7AMRE4TWECTCH04KB73EQFM","android-cicd",null,"Automated Android CI\u002FCD pipeline to Google Play — supports TWA, React Native, Flutter, and native Android. Run npx android-cicd to set up keystore generation, GitHub Secrets, and a multi-stage workflow (internal\u002Falpha\u002Fbeta\u002Fproduction) with auto-bump versionCode.","GongYuanCaiJi\u002Fdsh-claude-code-templates","GongYuanCaiJi","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F129952120?v=4","01M7AK39Q4W3VPF7C1K8M58BFX","劉昱廷 Yu-Ting Liu","01M7AK39QPS2RAJKRQY0EPQJPZ",0,"MIT","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fdevelopment\u002Fandroid-cicd\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: android-cicd\ndescription: \"Automated Android CI\u002FCD pipeline to Google Play — supports TWA, React Native, Flutter, and native Android. Run npx android-cicd to set up keystore generation, GitHub Secrets, and a multi-stage workflow (internal\u002Falpha\u002Fbeta\u002Fproduction) with auto-bump versionCode.\"\nrisk: safe\nsource: community\ndate_added: \"2026-05-12\"\nlicense: MIT\nmetadata:\n  author: ezescholz\n  version: \"1.0.0\"\n  npm: android-cicd\n---\n\n# Skill: android-cicd\n\n## Purpose\n\nSet up a complete, multi-stage Android CI\u002FCD pipeline that automatically builds and publishes to Google Play via GitHub Actions. Supports TWA (Trusted Web Activity \u002F Bubblewrap), React Native, Flutter, and native Android (Gradle) projects.\n\n## When to Use\n\n- The project has an Android app tracked in a GitHub repository\n- No CI\u002FCD pipeline exists yet for the Android build\n- Goal: automate publishing to Google Play on every push to `main` and on version tags\n- User wants to avoid manual `versionCode` bumping\n\n---\n\n## Quick Start\n\nRun the interactive setup wizard from the root of the target project:\n\n```sh\nnpx android-cicd\n```\n\nThe wizard handles: framework detection → keystore generation → GitHub Secrets → workflow scaffold.\n\n---\n\n## Prerequisites\n\nBefore running the wizard, ensure:\n\n- Node.js ≥ 18\n- JDK 17 installed with `keytool` accessible (`JAVA_HOME` set, or installed via Eclipse Adoptium \u002F Android Studio)\n- [`gh` CLI](https:\u002F\u002Fcli.github.com) installed and authenticated (`gh auth login`)\n- App already created in [Google Play Console](https:\u002F\u002Fplay.google.com\u002Fconsole) — at least **one manual AAB\u002FAPK upload** done (required before the API can publish)\n- App enrolled in **Play App Signing** (Google manages the signing key; you manage the upload key)\n- Google Play Android Developer API enabled in Google Cloud Console\n- Service account JSON key downloaded (see Manual Steps below)\n\n---\n\n## Framework Detection\n\nThe wizard auto-detects the framework from the project directory structure:\n\n| Condition | Detected framework |\n|---|---|\n| `pubspec.yaml` contains `flutter:` | `flutter` |\n| `android\u002Fapp\u002Fbuild.gradle` exists + `package.json` has `react-native` dep | `react-native` |\n| `android-root-app\u002Fbuild.gradle` or `twa-manifest.json` or `.bubblewrap\u002Fconfig.json` exists | `twa` |\n| `app\u002Fbuild.gradle` exists | `native` |\n| `android\u002Fapp\u002Fbuild.gradle` exists (fallback) | `native` |\n\nThe user can override the detected framework during the wizard.\n\n---\n\n## Multi-Stage Pipeline\n\nThe scaffolded workflow publishes to different tracks based on the git ref:\n\n| Git event | Google Play track |\n|---|---|\n| Push to `main` | `internal` |\n| Tag matching `v*-alpha` (e.g. `v1.2-alpha`) | `alpha` |\n| Tag matching `v*-beta` (e.g. `v1.2-beta`) | `beta` |\n| Tag matching `v*` (e.g. `v1.2.0`) | `production` |\n| Manual `workflow_dispatch` | User-selectable (internal \u002F alpha \u002F beta \u002F production) |\n\nTo release to production:\n```sh\ngit tag v1.2.0\ngit push origin v1.2.0\n```\n\n---\n\n## Auto-Bump versionCode\n\nOn every push to `main`, CI automatically:\n\n1. Reads the current `versionCode` from the version file for the detected framework\n2. Increments it by 1\n3. Commits the change with `[skip ci]` (prevents re-triggering the workflow)\n4. Pushes the commit back to `main`\n\nVersion file by framework:\n\n| Framework | Version file | Field |\n|---|---|---|\n| TWA | `android-root-app\u002Fbuild.gradle` | `versionCode` |\n| React Native | `android\u002Fapp\u002Fbuild.gradle` | `versionCode` |\n| Flutter | `pubspec.yaml` | `version: x.y.z+N` (the `+N` build number) |\n| Native | `app\u002Fbuild.gradle` | `versionCode` |\n\nFor tag-based builds (alpha \u002F beta \u002F production), auto-bump does **not** run — the tag represents a pinned commit. Increment the version manually before tagging.\n\n---\n\n## Required GitHub Secrets\n\nThe wizard sets these automatically via `gh secret set`:\n\n| Secret | Description |\n|---|---|\n| `KEYSTORE_FILE` | Base64-encoded upload keystore (`.jks`) |\n| `KEYSTORE_PASSWORD` | Keystore password |\n| `KEY_ALIAS` | Key alias (e.g. `upload`) |\n| `KEY_PASSWORD` | Key password (usually same as `KEYSTORE_PASSWORD`) |\n| `GOOGLE_PLAY_SERVICE_ACCOUNT_JSON` | Full JSON content of the service account key |\n\n---\n\n## Signing Configuration\n\n### TWA \u002F Native Android\n\nAdd to your `build.gradle` (see `templates\u002Fgradle\u002Fsigning.gradle`):\n\n```groovy\nandroid {\n    signingConfigs {\n        release {\n            storeFile file(\"keystore.jks\")\n            storePassword System.getenv(\"KEYSTORE_PASSWORD\")\n            keyAlias System.getenv(\"KEY_ALIAS\")\n            keyPassword System.getenv(\"KEY_PASSWORD\")\n        }\n    }\n    buildTypes {\n        release {\n            minifyEnabled true\n            signingConfig signingConfigs.release\n        }\n    }\n}\n```\n\n> **Never** set `org.gradle.java.home` in `gradle.properties` — it breaks Linux CI runners.\n\n### Flutter\n\nThe CI workflow creates `android\u002Fkey.properties` at build time (from secrets) and cleans it up after. Your `android\u002Fapp\u002Fbuild.gradle` should read from it:\n\n```groovy\ndef keystoreProperties = new Properties()\ndef keystorePropertiesFile = rootProject.file('key.properties')\nif (keystorePropertiesFile.exists()) {\n    keystoreProperties.load(new FileInputStream(keystorePropertiesFile))\n}\n\nandroid {\n    signingConfigs {\n        release {\n            keyAlias keystoreProperties['keyAlias']\n            keyPassword keystoreProperties['keyPassword']\n            storeFile keystoreProperties['storeFile'] ? file(keystoreProperties['storeFile']) : null\n            storePassword keystoreProperties['storePassword']\n        }\n    }\n    buildTypes {\n        release {\n            signingConfig signingConfigs.release\n        }\n    }\n}\n```\n\n---\n\n## Manual Steps (Cannot Be Automated)\n\n### 1. Create the service account\n\n1. [Google Cloud Console](https:\u002F\u002Fconsole.cloud.google.com) → your project → **IAM & Admin** → **Service Accounts**\n2. **Create service account** → name: `github-play-publisher` → **Done** (no roles needed)\n3. Click the service account → **Keys** tab → **Add key** → **Create new key** → **JSON** → download\n\n### 2. Enable the Play API\n\nGoogle Cloud Console → **APIs & Services** → search **Google Play Android Developer API** → **Enable**\n\n### 3. Invite the service account in Play Console\n\n1. Play Console → **Users and permissions** → **Invite new user**\n2. Email: `github-play-publisher@YOUR-PROJECT.iam.gserviceaccount.com`\n3. Account-level permissions:\n   - ✅ Release apps to testing tracks\n   - ✅ Manage testing tracks and edit testers\n4. **Apply**\n\n### 4. First manual upload\n\nGoogle Play requires at least one manually uploaded AAB before the API can publish. If this is a brand-new app, upload the first build from your local machine before running the CI pipeline.\n\n---\n\n## Troubleshooting\n\n| Error | Cause | Fix |\n|---|---|---|\n| `Java home supplied is invalid` | `org.gradle.java.home` hardcoded in `gradle.properties` | Remove that line |\n| `signed with the wrong key` | Keystore in secret doesn't match Play's registered upload key | Update `KEYSTORE_FILE` secret |\n| `The caller does not have permission` | Service account missing permissions or API not enabled | Re-check Manual Steps 2 and 3 |\n| `Upload failed — wrong versionCode` | versionCode not incremented (tag-based build) | Increment versionCode manually before tagging |\n| `shallow update not allowed` | Shallow git checkout when pushing version bump | Workflow uses `fetch-depth: 0` — verify the checkout step |\n| Workflow not triggering on tag | Tag not pushed to remote | Run `git push origin TAG_NAME` |\n| `gh: command not found` | gh CLI not installed | Install from https:\u002F\u002Fcli.github.com |\n| `keytool not found` | JDK not installed or not on PATH | Set `JAVA_HOME` or install JDK 17 |\n\n---\n\n## Recovering a Lost Upload Keystore\n\nIf the app uses **Play App Signing** (recommended):\n\n1. Generate a new keystore: `npx android-cicd` and choose \"I already have a keystore: No\"\n2. Export the PEM certificate:\n   ```sh\n   keytool -export -rfc -keystore upload.jks -alias ALIAS -storepass PASSWORD -file cert.pem\n   ```\n3. Play Console → app → **App integrity** → **App signing** → **Request upload key reset**\n4. Select \"I forgot my password\" → upload `cert.pem`\n5. Wait 1–2 business days for Google approval\n6. Update the `KEYSTORE_FILE` secret with the new keystore base64\n\n---\n\n## Manually Bumping the Version (Tag Releases)\n\nBefore pushing a tag for alpha \u002F beta \u002F production:\n\n**TWA \u002F Native \u002F React Native** — edit `build.gradle`:\n```groovy\nversionCode 8   \u002F\u002F increment\nversionName \"1.2.0\"\n```\n\n**Flutter** — edit `pubspec.yaml`:\n```yaml\nversion: 1.2.0+8\n```\n\nThen tag and push:\n```sh\ngit add .\ngit commit -m \"chore: bump version to 1.2.0\"\ngit tag v1.2.0\ngit push origin main --tags\n```\n","# Skill: android-cicd\n\n## Purpose\n\nSet up a complete, multi-stage Android CI\u002FCD pipeline that automatically builds and publishes to Google Play via GitHub Actions. Supports TWA (Trusted Web Activity \u002F Bubblewrap), React Native, Flutter, and native Android (Gradle) projects.\n\n## When to Use\n\n- The project has an Android app tracked in a GitHub repository\n- No CI\u002FCD pipeline exists yet for the Android build\n- Goal: automate publishing to Google Play on every push to `main` and on version tags\n- User wants to avoid manual `versionCode` bumping\n\n---\n\n## Quick Start\n\nRun the interactive setup wizard from the root of the target project:\n\n```sh\nnpx android-cicd\n```\n\nThe wizard handles: framework detection → keystore generation → GitHub Secrets → workflow scaffold.\n\n---\n\n## Prerequisites\n\nBefore running the wizard, ensure:\n\n- Node.js ≥ 18\n- JDK 17 installed with `keytool` accessible (`JAVA_HOME` set, or installed via Eclipse Adoptium \u002F Android Studio)\n- [`gh` CLI](https:\u002F\u002Fcli.github.com) installed and authenticated (`gh auth login`)\n- App already created in [Google Play Console](https:\u002F\u002Fplay.google.com\u002Fconsole) — at least **one manual AAB\u002FAPK upload** done (required before the API can publish)\n- App enrolled in **Play App Signing** (Google manages the signing key; you manage the upload key)\n- Google Play Android Developer API enabled in Google Cloud Console\n- Service account JSON key downloaded (see Manual Steps below)\n\n---\n\n## Framework Detection\n\nThe wizard auto-detects the framework from the project directory structure:\n\n| Condition | Detected framework |\n|---|---|\n| `pubspec.yaml` contains `flutter:` | `flutter` |\n| `android\u002Fapp\u002Fbuild.gradle` exists + `package.json` has `react-native` dep | `react-native` |\n| `android-root-app\u002Fbuild.gradle` or `twa-manifest.json` or `.bubblewrap\u002Fconfig.json` exists | `twa` |\n| `app\u002Fbuild.gradle` exists | `native` |\n| `android\u002Fapp\u002Fbuild.gradle` exists (fallback) | `native` |\n\nThe user can override the detected framework during the wizard.\n\n---\n\n## Multi-Stage Pipeline\n\nThe scaffolded workflow publishes to different tracks based on the git ref:\n\n| Git event | Google Play track |\n|---|---|\n| Push to `main` | `internal` |\n| Tag matching `v*-alpha` (e.g. `v1.2-alpha`) | `alpha` |\n| Tag matching `v*-beta` (e.g. `v1.2-beta`) | `beta` |\n| Tag matching `v*` (e.g. `v1.2.0`) | `production` |\n| Manual `workflow_dispatch` | User-selectable (internal \u002F alpha \u002F beta \u002F production) |\n\nTo release to production:\n```sh\ngit tag v1.2.0\ngit push origin v1.2.0\n```\n\n---\n\n## Auto-Bump versionCode\n\nOn every push to `main`, CI automatically:\n\n1. Reads the current `versionCode` from the version file for the detected framework\n2. Increments it by 1\n3. Commits the change with `[skip ci]` (prevents re-triggering the workflow)\n4. Pushes the commit back to `main`\n\nVersion file by framework:\n\n| Framework | Version file | Field |\n|---|---|---|\n| TWA | `android-root-app\u002Fbuild.gradle` | `versionCode` |\n| React Native | `android\u002Fapp\u002Fbuild.gradle` | `versionCode` |\n| Flutter | `pubspec.yaml` | `version: x.y.z+N` (the `+N` build number) |\n| Native | `app\u002Fbuild.gradle` | `versionCode` |\n\nFor tag-based builds (alpha \u002F beta \u002F production), auto-bump does **not** run — the tag represents a pinned commit. Increment the version manually before tagging.\n\n---\n\n## Required GitHub Secrets\n\nThe wizard sets these automatically via `gh secret set`:\n\n| Secret | Description |\n|---|---|\n| `KEYSTORE_FILE` | Base64-encoded upload keystore (`.jks`) |\n| `KEYSTORE_PASSWORD` | Keystore password |\n| `KEY_ALIAS` | Key alias (e.g. `upload`) |\n| `KEY_PASSWORD` | Key password (usually same as `KEYSTORE_PASSWORD`) |\n| `GOOGLE_PLAY_SERVICE_ACCOUNT_JSON` | Full JSON content of the service account key |\n\n---\n\n## Signing Configuration\n\n### TWA \u002F Native Android\n\nAdd to your `build.gradle` (see `templates\u002Fgradle\u002Fsigning.gradle`):\n\n```groovy\nandroid {\n    signingConfigs {\n        release {\n            storeFile file(\"keystore.jks\")\n            storePassword System.getenv(\"KEYSTORE_PASSWORD\")\n            keyAlias System.getenv(\"KEY_ALIAS\")\n            keyPassword System.getenv(\"KEY_PASSWORD\")\n        }\n    }\n    buildTypes {\n        release {\n            minifyEnabled true\n            signingConfig signingConfigs.release\n        }\n    }\n}\n```\n\n> **Never** set `org.gradle.java.home` in `gradle.properties` — it breaks Linux CI runners.\n\n### Flutter\n\nThe CI workflow creates `android\u002Fkey.properties` at build time (from secrets) and cleans it up after. Your `android\u002Fapp\u002Fbuild.gradle` should read from it:\n\n```groovy\ndef keystoreProperties = new Properties()\ndef keystorePropertiesFile = rootProject.file('key.properties')\nif (keystorePropertiesFile.exists()) {\n    keystoreProperties.load(new FileInputStream(keystorePropertiesFile))\n}\n\nandroid {\n    signingConfigs {\n        release {\n            keyAlias keystoreProperties['keyAlias']\n            keyPassword keystoreProperties['keyPassword']\n            storeFile keystoreProperties['storeFile'] ? file(keystoreProperties['storeFile']) : null\n            storePassword keystoreProperties['storePassword']\n        }\n    }\n    buildTypes {\n        release {\n            signingConfig signingConfigs.release\n        }\n    }\n}\n```\n\n---\n\n## Manual Steps (Cannot Be Automated)\n\n### 1. Create the service account\n\n1. [Google Cloud Console](https:\u002F\u002Fconsole.cloud.google.com) → your project → **IAM & Admin** → **Service Accounts**\n2. **Create service account** → name: `github-play-publisher` → **Done** (no roles needed)\n3. Click the service account → **Keys** tab → **Add key** → **Create new key** → **JSON** → download\n\n### 2. Enable the Play API\n\nGoogle Cloud Console → **APIs & Services** → search **Google Play Android Developer API** → **Enable**\n\n### 3. Invite the service account in Play Console\n\n1. Play Console → **Users and permissions** → **Invite new user**\n2. Email: `github-play-publisher@YOUR-PROJECT.iam.gserviceaccount.com`\n3. Account-level permissions:\n   - ✅ Release apps to testing tracks\n   - ✅ Manage testing tracks and edit testers\n4. **Apply**\n\n### 4. First manual upload\n\nGoogle Play requires at least one manually uploaded AAB before the API can publish. If this is a brand-new app, upload the first build from your local machine before running the CI pipeline.\n\n---\n\n## Troubleshooting\n\n| Error | Cause | Fix |\n|---|---|---|\n| `Java home supplied is invalid` | `org.gradle.java.home` hardcoded in `gradle.properties` | Remove that line |\n| `signed with the wrong key` | Keystore in secret doesn't match Play's registered upload key | Update `KEYSTORE_FILE` secret |\n| `The caller does not have permission` | Service account missing permissions or API not enabled | Re-check Manual Steps 2 and 3 |\n| `Upload failed — wrong versionCode` | versionCode not incremented (tag-based build) | Increment versionCode manually before tagging |\n| `shallow update not allowed` | Shallow git checkout when pushing version bump | Workflow uses `fetch-depth: 0` — verify the checkout step |\n| Workflow not triggering on tag | Tag not pushed to remote | Run `git push origin TAG_NAME` |\n| `gh: command not found` | gh CLI not installed | Install from https:\u002F\u002Fcli.github.com |\n| `keytool not found` | JDK not installed or not on PATH | Set `JAVA_HOME` or install JDK 17 |\n\n---\n\n## Recovering a Lost Upload Keystore\n\nIf the app uses **Play App Signing** (recommended):\n\n1. Generate a new keystore: `npx android-cicd` and choose \"I already have a keystore: No\"\n2. Export the PEM certificate:\n   ```sh\n   keytool -export -rfc -keystore upload.jks -alias ALIAS -storepass PASSWORD -file cert.pem\n   ```\n3. Play Console → app → **App integrity** → **App signing** → **Request upload key reset**\n4. Select \"I forgot my password\" → upload `cert.pem`\n5. Wait 1–2 business days for Google approval\n6. Update the `KEYSTORE_FILE` secret with the new keystore base64\n\n---\n\n## Manually Bumping the Version (Tag Releases)\n\nBefore pushing a tag for alpha \u002F beta \u002F production:\n\n**TWA \u002F Native \u002F React Native** — edit `build.gradle`:\n```groovy\nversionCode 8   \u002F\u002F increment\nversionName \"1.2.0\"\n```\n\n**Flutter** — edit `pubspec.yaml`:\n```yaml\nversion: 1.2.0+8\n```\n\nThen tag and push:\n```sh\ngit add .\ngit commit -m \"chore: bump version to 1.2.0\"\ngit tag v1.2.0\ngit push origin main --tags\n```\n",{"name":5,"risk":24,"source":25,"license":15,"metadata":26,"date_added":29,"description":7},"safe","community",{"npm":5,"author":27,"version":28},"ezescholz","1.0.0","2026-05-12","main","51493f354fd03e3f941d4df7fd64c0b8c7a2632d","skills\u002Fdevelopment\u002Fandroid-cicd","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi","漏洞研究、根因分析、黑箱測試｜做 AI agent 工具｜Vulnerability research, root-cause analysis, AI agent tooling","2026-08-16 02:24:07",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add GongYuanCaiJi\u002Fdsh-claude-code-templates --skill android-cicd",{"tool":43,"command":44},"bunx","bunx skills add GongYuanCaiJi\u002Fdsh-claude-code-templates --skill android-cicd",{"tool":46,"command":47},"pnpm","pnpm dlx skills add GongYuanCaiJi\u002Fdsh-claude-code-templates --skill android-cicd","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fdevelopment\u002Fandroid-cicd\u002FSKILL.md",true,[],[52,59,68,75,82,89],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7ARMYTZ5D4B7N5SKFXV345V","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\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fzapier-make-patterns\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":63,"licenseFileUrl":64,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7ARMX1BVNEAR98SBANMDF2V","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\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7ARMPR4RQ417MG1HMPGNQHH","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\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fworkflow-automation\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7ARMHBERDMKGDMV7K6MQ6YP","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\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Ftrigger-dev\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7ARME0A7KFT330Q2H25HE2B","slack-automation","Automate Slack workspace operations including messaging, search, channel management, and reaction workflows through Composio's Slack toolkit.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fslack-automation\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7ARM8D87V18WDG0GEZS11ZT","planning-with-files","Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fplanning-with-files\u002FSKILL.md",[],[]]