[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AEBAPH3Y97G498CD9R67GS":3,"skill-same:01M6AEBAPH3Y97G498CD9R67GS":82},{"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":23,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":58,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":62,"repositoryHomepageUrl":63,"ownerHtmlUrl":64,"ownerBlogUrl":65,"ownerDescription":66,"updatedAt":67,"install":68,"resources":81},"01M6AEBAPH3Y97G498CD9R67GS","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.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33418,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fandroid-cicd\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"android","cicd","android cicd","Production","2026","CI\u002FCD","native","community","bump","up","auto","react native","secrets","SET","google","pipeline","ci","beta","alpha","play","run","react","workflow","github","safe","2026-11-10 10:12:30",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.\"\nlicense: MIT\nmetadata:\n  author: ezescholz\n  version: \"1.0.0\"\n  npm: android-cicd\n  risk: safe\n  source: community\n  date_added: \"2026-05-12\"\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,"license":15,"metadata":54,"description":7},{"npm":5,"risk":48,"author":55,"source":31,"version":56,"date_added":57},"ezescholz","1.0.0","2026-05-12","main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fandroid-cicd",3926,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates","https:\u002F\u002Faitmpl.com","https:\u002F\u002Fgithub.com\u002Fdavila7","https:\u002F\u002Fdanielavila.me","Building AI dev tools with LLMs","2026-11-12 14:45:56",{"source":8,"skillName":5,"commands":69,"prompt":79,"zipAvailable":80},[70,73,76],{"tool":71,"command":72},"npx","npx skills add davila7\u002Fclaude-code-templates --skill android-cicd",{"tool":74,"command":75},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill android-cicd",{"tool":77,"command":78},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill android-cicd","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fandroid-cicd\u002FSKILL.md",true,[],[83,111,138,171,205,229],{"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":90,"publishedAt":49},"01M70NHBTQ8BV0A2SCAZXEPHCX","wealthville-pool-scoring","Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter\u002FHold\u002FExit\u002FReduce\u002FAvoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-data\u002Fwealthville-pool-scoring\u002FSKILL.md",[89],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110],"scoring","pool","wealthville pool scoring","liquidity","which","for","exit","now","use","when","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":118,"publishedAt":49},"01M70MB6VR8ERJ4EM8D5KHBMEV","technical-debt-auditor","Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO\u002FFIXME\u002FHACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like \"where should I focus refactoring\", \"find code smells\", \"audit my codebase\", \"what technical debt do we have\", \"prioritize cleanup work\", or asks about code quality metrics. Also trigger when the user mentions \"code rot\", \"legacy cleanup\", \"refactoring priorities\", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say \"technical debt\" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ftechnical-debt-auditor\u002FSKILL.md",[117],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[119,120,121,122,123,124,125,126,127,128,129,100,130,131,132,133,134,135,136,137],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":153,"publishedAt":49},"01M70KPYH9QNHCNME5GJQGE22K","readonly-sql-guard","Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production\u002FERP\u002Fanalytics database (a \"query\" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write\u002FDDL\u002Fside-effect\u002Ftransaction-escape risks. Checks what a statement CALLS, not just its shape.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdatabase\u002Freadonly-sql-guard\u002FSKILL.md",[144,147,148],{"categoryNo":145,"categoryName":146,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":149,"categoryName":150,"taxonomyType":151,"taxonomyTypeDesc":152},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[154,155,156,157,158,159,160,96,161,162,163,164,165,166,167,99,168,169,100,170],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":175,"licenseFileUrl":176,"sourceHtmlUrl":177,"categories":178,"keywords":182,"publishedAt":49},"01M6AFY6F7CC2BBZP1QD6VTNVC","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[179],{"categoryNo":180,"categoryName":181,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[183,184,185,186,187,188,189,190,191,192,193,194,195,196,197,198,45,199,200,201,202,203,96,204],"artifacts builder","web","web artifacts builder","artifacts","builder","state","routing","state management","component","css","frontend","ui","Tools","file","components","shadcn","Tailwind","suite","jsx","html","single-file","ui components",{"skillNo":206,"name":207,"nameZh":6,"description":208,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":175,"licenseFileUrl":209,"sourceHtmlUrl":210,"categories":211,"keywords":216,"publishedAt":49},"01M6AFWF33SFV9Z3SF4PEEE4BF","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[212,215],{"categoryNo":213,"categoryName":214,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":180,"categoryName":181,"taxonomyType":21,"taxonomyTypeDesc":22},[217,218,219,220,221,184,222,193,194,223,224,225,226,96,227,102,228],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":230,"name":231,"nameZh":6,"description":232,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":175,"licenseFileUrl":233,"sourceHtmlUrl":234,"categories":235,"keywords":243,"publishedAt":49},"01M6AF67Q67JJJ5V51JR2P52KA","discernment-nudge","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FSKILL.md",[236,239,240],{"categoryNo":237,"categoryName":238,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":241,"categoryName":242,"taxonomyType":151,"taxonomyTypeDesc":152},"01JBSEEDCAT000000000000036","内容创作者",[244,245,246,247,44,248,249,250,186,251,196,130,252,253,254,255,33,166,256,100,257,258,259,260,261,108,262],"discernment nudge","nudge","interpretation","help","reasoning","data","writing","lookup","content","review","conversation","short","invoke","you","analysis","claims","argument","assemble","recommendations"]