[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79540WK4K32RAP5EQKV2RT6":3,"skill-same:01M79540WK4K32RAP5EQKV2RT6":57},{"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":34,"commitSha":35,"skillDirectory":36,"forksCount":37,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":40,"ownerDescription":41,"updatedAt":42,"install":43,"resources":56},"01M79540WK4K32RAP5EQKV2RT6","replit-multi-env-setup",null,"Configure Replit dev\u002Fstaging\u002Fproduction environments with separate databases, secrets, and deployment tiers.\nUse when setting up multi-environment deployments, managing per-environment secrets,\nor implementing environment-specific Replit configurations.\nTrigger with phrases like \"replit environments\", \"replit staging\",\n\"replit dev prod\", \"replit environment setup\", \"replit separate databases\".","jukeyman\u002Fjukeyman-skills","jukeyman","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F142960420?v=4","01M78FR4Y3DHMMCBCC0GXXNB3F","RICK JEFFERSON","01M78FR4Z8RVQRAD31Y5J7V6EB",1,"MIT","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--replit-pack--replit-multi-env-setup\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: replit-multi-env-setup\ndescription: |\n  Configure Replit dev\u002Fstaging\u002Fproduction environments with separate databases, secrets, and deployment tiers.\n  Use when setting up multi-environment deployments, managing per-environment secrets,\n  or implementing environment-specific Replit configurations.\n  Trigger with phrases like \"replit environments\", \"replit staging\",\n  \"replit dev prod\", \"replit environment setup\", \"replit separate databases\".\nallowed-tools: Read, Write, Edit\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\ntags: [saas, replit, deployment, environments]\n---\n# Replit Multi-Environment Setup\n\n## Overview\nConfigure development, staging, and production environments on Replit. Leverages Replit's built-in dev\u002Fprod database separation, environment-specific secrets, and deployment types. Covers the Replit-native approach (single Repl, dual databases) and the multi-Repl approach (separate Repls per environment).\n\n## Prerequisites\n- Replit Core or Teams plan (deployment access)\n- PostgreSQL provisioned in Database pane\n- Understanding of Replit Secrets\n\n## Environment Strategy\n\n### Approach 1: Single Repl, Dual Databases (Recommended)\nReplit natively provides separate development and production databases:\n```markdown\nWorkspace \"Run\" button → Development database\nDeployed app (.replit.app) → Production database\n\nBoth use the same DATABASE_URL env var — Replit routes automatically.\nNo code changes needed between environments.\n```\n\n### Approach 2: Multi-Repl (Staging + Production)\nFor teams that need a staging environment:\n```markdown\nRepl 1: my-app-staging → Autoscale deployment → staging.replit.app\nRepl 2: my-app-prod   → Reserved VM deployment → app.example.com\n\nEach Repl has its own:\n- Secrets (different API keys per environment)\n- PostgreSQL database (separate data)\n- Deployment configuration\n- GitHub branch (staging → staging, main → production)\n```\n\n## Instructions\n\n### Step 1: Environment Detection\n```typescript\n\u002F\u002F src\u002Fconfig\u002Fenvironment.ts\ntype Environment = 'development' | 'staging' | 'production';\n\nexport function detectEnvironment(): Environment {\n  \u002F\u002F Replit deployment context\n  if (process.env.REPL_DEPLOYMENT) {\n    \u002F\u002F Check if this is the staging Repl\n    if (process.env.REPL_SLUG?.includes('staging')) return 'staging';\n    return 'production';\n  }\n\n  \u002F\u002F Workspace \"Run\" context\n  if (process.env.REPL_SLUG) return 'development';\n\n  \u002F\u002F Fallback to NODE_ENV\n  const env = process.env.NODE_ENV || 'development';\n  if (env === 'production') return 'production';\n  if (env === 'staging') return 'staging';\n  return 'development';\n}\n\nexport const ENV = detectEnvironment();\nexport const IS_PROD = ENV === 'production';\n```\n\n### Step 2: Environment-Specific Configuration\n```typescript\n\u002F\u002F src\u002Fconfig\u002Findex.ts\nimport { ENV, IS_PROD } from '.\u002Fenvironment';\n\nconst configs = {\n  development: {\n    logLevel: 'debug',\n    corsOrigins: ['*'],\n    rateLimit: { windowMs: 60000, max: 1000 },\n    cache: { ttlMs: 5000 },\n    features: { debugEndpoints: true },\n  },\n  staging: {\n    logLevel: 'info',\n    corsOrigins: ['https:\u002F\u002Fstaging.example.com'],\n    rateLimit: { windowMs: 60000, max: 200 },\n    cache: { ttlMs: 30000 },\n    features: { debugEndpoints: true },\n  },\n  production: {\n    logLevel: 'warn',\n    corsOrigins: ['https:\u002F\u002Fapp.example.com'],\n    rateLimit: { windowMs: 60000, max: 100 },\n    cache: { ttlMs: 300000 },\n    features: { debugEndpoints: false },\n  },\n};\n\nexport const config = {\n  env: ENV,\n  port: parseInt(process.env.PORT || '3000'),\n  ...configs[ENV],\n  db: {\n    \u002F\u002F DATABASE_URL auto-switches between dev and prod on Replit\n    url: process.env.DATABASE_URL,\n  },\n};\n\n\u002F\u002F Validate production secrets\nif (IS_PROD) {\n  const required = ['DATABASE_URL', 'JWT_SECRET'];\n  const missing = required.filter(k => !process.env[k]);\n  if (missing.length) {\n    console.error(`FATAL: Missing production secrets: ${missing.join(', ')}`);\n    process.exit(1);\n  }\n}\n```\n\n### Step 3: Separate Secrets Per Environment\n```markdown\nFor Single Repl (dev\u002Fprod separation):\n- All secrets set once in Secrets tab\n- DATABASE_URL auto-switches (Replit manages)\n- Same JWT_SECRET for both (or use REPL_IDENTITY for dev)\n\nFor Multi-Repl (staging + prod):\n- Each Repl has its own Secrets tab\n- staging Repl: JWT_SECRET=staging-secret, API_KEY=test-key\n- production Repl: JWT_SECRET=prod-secret, API_KEY=live-key\n\nAccount-level secrets (shared across all Repls):\n- Settings > Secrets > Account secrets\n- Useful for: monitoring tokens, shared infrastructure keys\n```\n\n### Step 4: GitHub Branch Strategy (Multi-Repl)\n```markdown\nRepository setup:\n- main branch → connected to production Repl\n- staging branch → connected to staging Repl\n- feature branches → PR to staging first\n\nWorkflow:\n1. Feature branch → PR to staging\n2. Tests pass + review → merge to staging\n3. Staging Repl auto-deploys → verify staging\n4. Staging → PR to main\n5. Merge → production Repl auto-deploys\n```\n\n```yaml\n# .github\u002Fworkflows\u002Fdeploy.yml\nname: Deploy Pipeline\n\non:\n  push:\n    branches: [staging, main]\n\njobs:\n  test:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - run: npm ci && npm test\n\n  verify-staging:\n    if: github.ref == 'refs\u002Fheads\u002Fstaging'\n    needs: test\n    runs-on: ubuntu-latest\n    steps:\n      - name: Wait for Replit deploy\n        run: sleep 60\n      - name: Health check staging\n        run: curl -sf ${{ secrets.STAGING_URL }}\u002Fhealth\n\n  verify-production:\n    if: github.ref == 'refs\u002Fheads\u002Fmain'\n    needs: test\n    runs-on: ubuntu-latest\n    steps:\n      - name: Wait for Replit deploy\n        run: sleep 60\n      - name: Health check production\n        run: curl -sf ${{ secrets.PRODUCTION_URL }}\u002Fhealth\n```\n\n### Step 5: Database Migration Between Environments\n```typescript\n\u002F\u002F scripts\u002Fpromote-data.ts — Copy staging data to production (carefully!)\nimport { Pool } from 'pg';\n\nconst staging = new Pool({ connectionString: process.env.STAGING_DATABASE_URL });\nconst production = new Pool({ connectionString: process.env.PRODUCTION_DATABASE_URL });\n\nasync function promoteConfig() {\n  \u002F\u002F Only promote configuration\u002Freference data, never user data\n  const { rows: configs } = await staging.query('SELECT * FROM feature_flags');\n\n  for (const config of configs) {\n    await production.query(\n      `INSERT INTO feature_flags (key, value, updated_at)\n       VALUES ($1, $2, NOW())\n       ON CONFLICT (key) DO UPDATE SET value = $2, updated_at = NOW()`,\n      [config.key, config.value]\n    );\n  }\n\n  console.log(`Promoted ${configs.length} feature flags to production`);\n}\n```\n\n### Step 6: Environment Indicator in UI\n```typescript\n\u002F\u002F Show environment badge in development\u002Fstaging\napp.use((req, res, next) => {\n  if (!IS_PROD) {\n    res.setHeader('X-Environment', ENV);\n  }\n  next();\n});\n\napp.get('\u002Fapi\u002Fstatus', (req, res) => {\n  res.json({\n    environment: ENV,\n    version: process.env.npm_package_version,\n    repl: process.env.REPL_SLUG,\n  });\n});\n```\n\n## Error Handling\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Wrong database in prod | Manual DATABASE_URL override | Let Replit manage DB routing |\n| Staging secrets in prod | Copied secrets incorrectly | Each Repl has independent Secrets |\n| GitHub sync conflict | Both Repls on same branch | Use separate branches per Repl |\n| Config validation fails | Missing env-specific secret | Add secret to correct Repl's Secrets tab |\n\n## Resources\n- [Replit Deployments](https:\u002F\u002Fdocs.replit.com\u002Fhosting\u002Fdeployments)\n- [Replit Secrets](https:\u002F\u002Fdocs.replit.com\u002Freplit-workspace\u002Fworkspace-features\u002Fsecrets)\n- [Deploying from GitHub](https:\u002F\u002Fdocs.replit.com\u002Fhosting\u002Fdeployments\u002Fdeploying-a-github-repository)\n- [PostgreSQL Dev\u002FProd Databases](https:\u002F\u002Fdocs.replit.com\u002Fcloud-services\u002Fstorage-and-databases\u002Fpostgresql-on-replit)\n\n## Next Steps\nFor monitoring, see `replit-observability`. For deployment, see `replit-deploy-integration`.\n","# Replit Multi-Environment Setup\n\n## Overview\nConfigure development, staging, and production environments on Replit. Leverages Replit's built-in dev\u002Fprod database separation, environment-specific secrets, and deployment types. Covers the Replit-native approach (single Repl, dual databases) and the multi-Repl approach (separate Repls per environment).\n\n## Prerequisites\n- Replit Core or Teams plan (deployment access)\n- PostgreSQL provisioned in Database pane\n- Understanding of Replit Secrets\n\n## Environment Strategy\n\n### Approach 1: Single Repl, Dual Databases (Recommended)\nReplit natively provides separate development and production databases:\n```markdown\nWorkspace \"Run\" button → Development database\nDeployed app (.replit.app) → Production database\n\nBoth use the same DATABASE_URL env var — Replit routes automatically.\nNo code changes needed between environments.\n```\n\n### Approach 2: Multi-Repl (Staging + Production)\nFor teams that need a staging environment:\n```markdown\nRepl 1: my-app-staging → Autoscale deployment → staging.replit.app\nRepl 2: my-app-prod   → Reserved VM deployment → app.example.com\n\nEach Repl has its own:\n- Secrets (different API keys per environment)\n- PostgreSQL database (separate data)\n- Deployment configuration\n- GitHub branch (staging → staging, main → production)\n```\n\n## Instructions\n\n### Step 1: Environment Detection\n```typescript\n\u002F\u002F src\u002Fconfig\u002Fenvironment.ts\ntype Environment = 'development' | 'staging' | 'production';\n\nexport function detectEnvironment(): Environment {\n  \u002F\u002F Replit deployment context\n  if (process.env.REPL_DEPLOYMENT) {\n    \u002F\u002F Check if this is the staging Repl\n    if (process.env.REPL_SLUG?.includes('staging')) return 'staging';\n    return 'production';\n  }\n\n  \u002F\u002F Workspace \"Run\" context\n  if (process.env.REPL_SLUG) return 'development';\n\n  \u002F\u002F Fallback to NODE_ENV\n  const env = process.env.NODE_ENV || 'development';\n  if (env === 'production') return 'production';\n  if (env === 'staging') return 'staging';\n  return 'development';\n}\n\nexport const ENV = detectEnvironment();\nexport const IS_PROD = ENV === 'production';\n```\n\n### Step 2: Environment-Specific Configuration\n```typescript\n\u002F\u002F src\u002Fconfig\u002Findex.ts\nimport { ENV, IS_PROD } from '.\u002Fenvironment';\n\nconst configs = {\n  development: {\n    logLevel: 'debug',\n    corsOrigins: ['*'],\n    rateLimit: { windowMs: 60000, max: 1000 },\n    cache: { ttlMs: 5000 },\n    features: { debugEndpoints: true },\n  },\n  staging: {\n    logLevel: 'info',\n    corsOrigins: ['https:\u002F\u002Fstaging.example.com'],\n    rateLimit: { windowMs: 60000, max: 200 },\n    cache: { ttlMs: 30000 },\n    features: { debugEndpoints: true },\n  },\n  production: {\n    logLevel: 'warn',\n    corsOrigins: ['https:\u002F\u002Fapp.example.com'],\n    rateLimit: { windowMs: 60000, max: 100 },\n    cache: { ttlMs: 300000 },\n    features: { debugEndpoints: false },\n  },\n};\n\nexport const config = {\n  env: ENV,\n  port: parseInt(process.env.PORT || '3000'),\n  ...configs[ENV],\n  db: {\n    \u002F\u002F DATABASE_URL auto-switches between dev and prod on Replit\n    url: process.env.DATABASE_URL,\n  },\n};\n\n\u002F\u002F Validate production secrets\nif (IS_PROD) {\n  const required = ['DATABASE_URL', 'JWT_SECRET'];\n  const missing = required.filter(k => !process.env[k]);\n  if (missing.length) {\n    console.error(`FATAL: Missing production secrets: ${missing.join(', ')}`);\n    process.exit(1);\n  }\n}\n```\n\n### Step 3: Separate Secrets Per Environment\n```markdown\nFor Single Repl (dev\u002Fprod separation):\n- All secrets set once in Secrets tab\n- DATABASE_URL auto-switches (Replit manages)\n- Same JWT_SECRET for both (or use REPL_IDENTITY for dev)\n\nFor Multi-Repl (staging + prod):\n- Each Repl has its own Secrets tab\n- staging Repl: JWT_SECRET=staging-secret, API_KEY=test-key\n- production Repl: JWT_SECRET=prod-secret, API_KEY=live-key\n\nAccount-level secrets (shared across all Repls):\n- Settings > Secrets > Account secrets\n- Useful for: monitoring tokens, shared infrastructure keys\n```\n\n### Step 4: GitHub Branch Strategy (Multi-Repl)\n```markdown\nRepository setup:\n- main branch → connected to production Repl\n- staging branch → connected to staging Repl\n- feature branches → PR to staging first\n\nWorkflow:\n1. Feature branch → PR to staging\n2. Tests pass + review → merge to staging\n3. Staging Repl auto-deploys → verify staging\n4. Staging → PR to main\n5. Merge → production Repl auto-deploys\n```\n\n```yaml\n# .github\u002Fworkflows\u002Fdeploy.yml\nname: Deploy Pipeline\n\non:\n  push:\n    branches: [staging, main]\n\njobs:\n  test:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - run: npm ci && npm test\n\n  verify-staging:\n    if: github.ref == 'refs\u002Fheads\u002Fstaging'\n    needs: test\n    runs-on: ubuntu-latest\n    steps:\n      - name: Wait for Replit deploy\n        run: sleep 60\n      - name: Health check staging\n        run: curl -sf ${{ secrets.STAGING_URL }}\u002Fhealth\n\n  verify-production:\n    if: github.ref == 'refs\u002Fheads\u002Fmain'\n    needs: test\n    runs-on: ubuntu-latest\n    steps:\n      - name: Wait for Replit deploy\n        run: sleep 60\n      - name: Health check production\n        run: curl -sf ${{ secrets.PRODUCTION_URL }}\u002Fhealth\n```\n\n### Step 5: Database Migration Between Environments\n```typescript\n\u002F\u002F scripts\u002Fpromote-data.ts — Copy staging data to production (carefully!)\nimport { Pool } from 'pg';\n\nconst staging = new Pool({ connectionString: process.env.STAGING_DATABASE_URL });\nconst production = new Pool({ connectionString: process.env.PRODUCTION_DATABASE_URL });\n\nasync function promoteConfig() {\n  \u002F\u002F Only promote configuration\u002Freference data, never user data\n  const { rows: configs } = await staging.query('SELECT * FROM feature_flags');\n\n  for (const config of configs) {\n    await production.query(\n      `INSERT INTO feature_flags (key, value, updated_at)\n       VALUES ($1, $2, NOW())\n       ON CONFLICT (key) DO UPDATE SET value = $2, updated_at = NOW()`,\n      [config.key, config.value]\n    );\n  }\n\n  console.log(`Promoted ${configs.length} feature flags to production`);\n}\n```\n\n### Step 6: Environment Indicator in UI\n```typescript\n\u002F\u002F Show environment badge in development\u002Fstaging\napp.use((req, res, next) => {\n  if (!IS_PROD) {\n    res.setHeader('X-Environment', ENV);\n  }\n  next();\n});\n\napp.get('\u002Fapi\u002Fstatus', (req, res) => {\n  res.json({\n    environment: ENV,\n    version: process.env.npm_package_version,\n    repl: process.env.REPL_SLUG,\n  });\n});\n```\n\n## Error Handling\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Wrong database in prod | Manual DATABASE_URL override | Let Replit manage DB routing |\n| Staging secrets in prod | Copied secrets incorrectly | Each Repl has independent Secrets |\n| GitHub sync conflict | Both Repls on same branch | Use separate branches per Repl |\n| Config validation fails | Missing env-specific secret | Add secret to correct Repl's Secrets tab |\n\n## Resources\n- [Replit Deployments](https:\u002F\u002Fdocs.replit.com\u002Fhosting\u002Fdeployments)\n- [Replit Secrets](https:\u002F\u002Fdocs.replit.com\u002Freplit-workspace\u002Fworkspace-features\u002Fsecrets)\n- [Deploying from GitHub](https:\u002F\u002Fdocs.replit.com\u002Fhosting\u002Fdeployments\u002Fdeploying-a-github-repository)\n- [PostgreSQL Dev\u002FProd Databases](https:\u002F\u002Fdocs.replit.com\u002Fcloud-services\u002Fstorage-and-databases\u002Fpostgresql-on-replit)\n\n## Next Steps\nFor monitoring, see `replit-observability`. For deployment, see `replit-deploy-integration`.\n",{"name":5,"tags":24,"author":29,"license":15,"version":30,"description":31,"allowed-tools":32,"compatible-with":33},[25,26,27,28],"saas","replit","deployment","environments","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Configure Replit dev\u002Fstaging\u002Fproduction environments with separate databases, secrets, and deployment tiers.\nUse when setting up multi-environment deployments, managing per-environment secrets,\nor implementing environment-specific Replit configurations.\nTrigger with phrases like \"replit environments\", \"replit staging\",\n\"replit dev prod\", \"replit environment setup\", \"replit separate databases\".\n","Read, Write, Edit","claude-code, codex, openclaw","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--replit-pack--replit-multi-env-setup",0,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills","https:\u002F\u002Fgithub.com\u002Fjukeyman","https:\u002F\u002FRJBUSINESSSOLUTIONS.ORG","Credit and Finance Expert | Developer\r\n\r\nI'm Rick Jefferson, a seasoned credit and finance expert with over a decade of experience in financial literacy,","2026-07-13 07:03:29",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill replit-multi-env-setup",{"tool":49,"command":50},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill replit-multi-env-setup",{"tool":52,"command":53},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill replit-multi-env-setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--replit-pack--replit-multi-env-setup\u002FSKILL.md",true,[],[58,65,72,79,86,94],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M79ANS2SM329NEP5ZCX106RR","zustand-store-creator","Create zustand store creator operations. Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category. Use when working with zustand store creator functionality. Trigger with phrases like \"zustand store creator\", \"zustand creator\", \"zustand\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M79AMZKP4YDEZ7EHG1Y7PP74","zero-trust-config-helper","Configure with zero trust config helper operations. Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category. Use when configuring systems or services. Trigger with phrases like \"zero trust config helper\", \"zero helper\", \"zero\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M79AMJSBCEJQNBTYNAHYN5HM","zapier-integration-helper","Assist with zapier integration helper operations. Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category. Use when working with APIs or building integrations. Trigger with phrases like \"zapier integration helper\", \"zapier helper\", \"zapier\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M79AHJZGVMARS13VFQYRR1MP","yaml-config-validator","Validate yaml config validator operations. Auto-activating skill for DevOps Basics.\nTriggers on: yaml config validator, yaml config validator\nPart of the DevOps Basics skill category. Use when configuring systems or services. Trigger with phrases like \"yaml config validator\", \"yaml validator\", \"yaml\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fyaml-config-validator\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":90,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M79AHGDZRN0020RDQSQDPAM8","xvary-stock-research","Thesis-driven equity analysis from public SEC EDGAR and market data; \u002Fanalyze, \u002Fscore, \u002Fcompare workflows with bundled Python tools (Claude Code, Cursor, Codex).","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M79AHCYJ9FV9RMHQ24HDRN33","xss-vulnerability-scanner","Scan xss vulnerability scanner operations. Auto-activating skill for Security Fundamentals.\nTriggers on: xss vulnerability scanner, xss vulnerability scanner\nPart of the Security Fundamentals skill category. Use when working with xss vulnerability scanner functionality. Trigger with phrases like \"xss vulnerability scanner\", \"xss scanner\", \"xss\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxss-vulnerability-scanner\u002FSKILL.md",[],[]]