[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M792NGNZC5DF90SBF3C6H0FQ":3,"skill-same:01M792NGNZC5DF90SBF3C6H0FQ":56},{"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":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":39,"ownerDescription":40,"updatedAt":41,"install":42,"resources":55},"01M792NGNZC5DF90SBF3C6H0FQ","lindy-multi-env-setup",null,"Configure Lindy AI across development, staging, and production environments.\nUse when setting up isolated workspaces, per-environment secrets,\nor environment-specific agent configurations.\nTrigger with phrases like \"lindy environments\", \"lindy staging\",\n\"lindy dev prod\", \"lindy environment setup\", \"lindy workspace isolation\".","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--lindy-pack--lindy-multi-env-setup\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: lindy-multi-env-setup\ndescription: |\n  Configure Lindy AI across development, staging, and production environments.\n  Use when setting up isolated workspaces, per-environment secrets,\n  or environment-specific agent configurations.\n  Trigger with phrases like \"lindy environments\", \"lindy staging\",\n  \"lindy dev prod\", \"lindy environment setup\", \"lindy workspace isolation\".\nallowed-tools: Read, Write, Edit, Bash(aws:*), Bash(gcloud:*), Bash(vault:*)\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\ntags: [saas, lindy, deployment]\n---\n# Lindy Multi-Environment Setup\n\n## Overview\nIsolate Lindy AI agents across development, staging, and production using separate\nworkspaces, dedicated API keys, and environment-specific webhook configurations.\nLindy agents live in workspaces — each environment should use its own workspace\nto prevent cross-environment data leakage.\n\n## Prerequisites\n- Multiple Lindy workspaces (one per environment) or Enterprise plan\n- Secret management solution (env vars, Vault, AWS\u002FGCP secrets)\n- CI\u002FCD pipeline with environment-aware deployment\n- Application with environment detection logic\n\n## Environment Strategy\n\n| Environment | Workspace | API Key Source | Agent Config |\n|-------------|-----------|---------------|-------------|\n| Development | `dev-workspace` | `.env.local` | Debug prompts, test integrations |\n| Staging | `staging-workspace` | CI\u002FCD secrets | Production-like, test data |\n| Production | `prod-workspace` | Secret manager | Hardened prompts, live integrations |\n\n## Instructions\n\n### Step 1: Create Separate Workspaces\n1. Log in at https:\u002F\u002Fapp.lindy.ai\n2. Create workspace for each environment: `[company]-dev`, `[company]-staging`, `[company]-prod`\n3. Generate separate API keys in each workspace\n4. Store each key in the appropriate secret store\n\n### Step 2: Environment Configuration\n```typescript\n\u002F\u002F config\u002Flindy.ts — Environment-aware Lindy configuration\ninterface LindyConfig {\n  apiKey: string;\n  webhookUrl: string;\n  webhookSecret: string;\n  workspace: string;\n  model: string;\n}\n\nfunction getLindyConfig(): LindyConfig {\n  const env = process.env.NODE_ENV || 'development';\n\n  const configs: Record\u003Cstring, LindyConfig> = {\n    development: {\n      apiKey: process.env.LINDY_API_KEY_DEV!,\n      webhookUrl: process.env.LINDY_WEBHOOK_URL_DEV!,\n      webhookSecret: process.env.LINDY_WEBHOOK_SECRET_DEV!,\n      workspace: 'dev',\n      model: 'gemini-flash', \u002F\u002F Cheap model for dev\n    },\n    staging: {\n      apiKey: process.env.LINDY_API_KEY_STAGING!,\n      webhookUrl: process.env.LINDY_WEBHOOK_URL_STAGING!,\n      webhookSecret: process.env.LINDY_WEBHOOK_SECRET_STAGING!,\n      workspace: 'staging',\n      model: 'claude-sonnet', \u002F\u002F Match prod model\n    },\n    production: {\n      apiKey: process.env.LINDY_API_KEY_PROD!,\n      webhookUrl: process.env.LINDY_WEBHOOK_URL_PROD!,\n      webhookSecret: process.env.LINDY_WEBHOOK_SECRET_PROD!,\n      workspace: 'production',\n      model: 'claude-sonnet',\n    },\n  };\n\n  const config = configs[env];\n  if (!config) throw new Error(`Unknown environment: ${env}`);\n  return config;\n}\n\nexport const lindyConfig = getLindyConfig();\n```\n\n### Step 3: Startup Validation\n```typescript\n\u002F\u002F validate-env.ts — Fail fast if Lindy config is missing\nimport { z } from 'zod';\n\nconst LindyEnvSchema = z.object({\n  LINDY_API_KEY: z.string().min(1, 'LINDY_API_KEY required'),\n  LINDY_WEBHOOK_SECRET: z.string().min(1, 'LINDY_WEBHOOK_SECRET required'),\n  LINDY_WEBHOOK_URL: z.string().url('LINDY_WEBHOOK_URL must be valid URL'),\n});\n\nexport function validateLindyEnv() {\n  const result = LindyEnvSchema.safeParse({\n    LINDY_API_KEY: process.env.LINDY_API_KEY,\n    LINDY_WEBHOOK_SECRET: process.env.LINDY_WEBHOOK_SECRET,\n    LINDY_WEBHOOK_URL: process.env.LINDY_WEBHOOK_URL,\n  });\n\n  if (!result.success) {\n    console.error('Lindy environment validation failed:');\n    result.error.issues.forEach(i => console.error(`  - ${i.path}: ${i.message}`));\n    process.exit(1);\n  }\n\n  console.log('Lindy environment validated successfully');\n}\n```\n\n### Step 4: Secret Management\n```bash\n# Development — .env.local (gitignored)\nLINDY_API_KEY=lnd_dev_xxxxxxxxxxxx\nLINDY_WEBHOOK_URL=https:\u002F\u002Fpublic.lindy.ai\u002Fapi\u002Fv1\u002Fwebhooks\u002Fdev-id\nLINDY_WEBHOOK_SECRET=whsec_dev_xxxxxxxxxxxx\n\n# Staging — CI\u002FCD secrets (GitHub Actions)\ngh secret set LINDY_API_KEY_STAGING --body \"lnd_staging_xxxx\"\ngh secret set LINDY_WEBHOOK_SECRET_STAGING --body \"whsec_staging_xxxx\"\n\n# Production — Cloud secret manager\n# AWS\naws secretsmanager create-secret \\\n  --name prod\u002Flindy\u002Fapi-key \\\n  --secret-string \"lnd_prod_xxxxxxxxxxxx\"\n\n# GCP\necho -n \"lnd_prod_xxxxxxxxxxxx\" | \\\n  gcloud secrets create lindy-api-key-prod --data-file=-\n```\n\n### Step 5: Agent Promotion (Dev to Staging to Prod)\n```\n1. Build and test agent in dev workspace\n2. Share agent as Template\n3. Import template into staging workspace\n4. Re-authorize integrations with staging accounts\n5. Update webhook URLs to staging endpoints\n6. Test with staging data for 24-48 hours\n7. Repeat for production workspace\n8. Update webhook URLs to production endpoints\n9. Verify all integrations authorized with production accounts\n```\n\n**Critical**: OAuth tokens, webhook URLs, and phone numbers do NOT transfer\nbetween workspaces. Each must be reconfigured per environment.\n\n### Step 6: CI\u002FCD Integration\n```yaml\n# .github\u002Fworkflows\u002Fdeploy.yml\njobs:\n  deploy-staging:\n    if: github.ref == 'refs\u002Fheads\u002Fdevelop'\n    environment: staging\n    env:\n      LINDY_API_KEY: ${{ secrets.LINDY_API_KEY_STAGING }}\n      LINDY_WEBHOOK_SECRET: ${{ secrets.LINDY_WEBHOOK_SECRET_STAGING }}\n    steps:\n      - run: npm run deploy:staging\n      - run: npm run test:lindy:smoke\n\n  deploy-prod:\n    if: github.ref == 'refs\u002Fheads\u002Fmain'\n    environment: production\n    env:\n      LINDY_API_KEY: ${{ secrets.LINDY_API_KEY_PROD }}\n      LINDY_WEBHOOK_SECRET: ${{ secrets.LINDY_WEBHOOK_SECRET_PROD }}\n    steps:\n      - run: npm run deploy:prod\n      - run: npm run test:lindy:smoke\n```\n\n## Error Handling\n\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Dev agent hits prod data | Shared workspace | Use separate workspaces per environment |\n| Staging integration fails | OAuth token expired | Re-authorize with staging service accounts |\n| Webhook URL mismatch | Dev URL in prod config | Validate webhook URLs at startup |\n| Secret not found in CI | Missing environment secret | Add via `gh secret set` per environment |\n\n## Resources\n- [Lindy Documentation](https:\u002F\u002Fdocs.lindy.ai)\n- [Lindy Templates](https:\u002F\u002Fdocs.lindy.ai\u002Ffundamentals\u002Flindy-101\u002Ftemplates)\n\n## Next Steps\nProceed to `lindy-observability` for monitoring and alerting.\n","# Lindy Multi-Environment Setup\n\n## Overview\nIsolate Lindy AI agents across development, staging, and production using separate\nworkspaces, dedicated API keys, and environment-specific webhook configurations.\nLindy agents live in workspaces — each environment should use its own workspace\nto prevent cross-environment data leakage.\n\n## Prerequisites\n- Multiple Lindy workspaces (one per environment) or Enterprise plan\n- Secret management solution (env vars, Vault, AWS\u002FGCP secrets)\n- CI\u002FCD pipeline with environment-aware deployment\n- Application with environment detection logic\n\n## Environment Strategy\n\n| Environment | Workspace | API Key Source | Agent Config |\n|-------------|-----------|---------------|-------------|\n| Development | `dev-workspace` | `.env.local` | Debug prompts, test integrations |\n| Staging | `staging-workspace` | CI\u002FCD secrets | Production-like, test data |\n| Production | `prod-workspace` | Secret manager | Hardened prompts, live integrations |\n\n## Instructions\n\n### Step 1: Create Separate Workspaces\n1. Log in at https:\u002F\u002Fapp.lindy.ai\n2. Create workspace for each environment: `[company]-dev`, `[company]-staging`, `[company]-prod`\n3. Generate separate API keys in each workspace\n4. Store each key in the appropriate secret store\n\n### Step 2: Environment Configuration\n```typescript\n\u002F\u002F config\u002Flindy.ts — Environment-aware Lindy configuration\ninterface LindyConfig {\n  apiKey: string;\n  webhookUrl: string;\n  webhookSecret: string;\n  workspace: string;\n  model: string;\n}\n\nfunction getLindyConfig(): LindyConfig {\n  const env = process.env.NODE_ENV || 'development';\n\n  const configs: Record\u003Cstring, LindyConfig> = {\n    development: {\n      apiKey: process.env.LINDY_API_KEY_DEV!,\n      webhookUrl: process.env.LINDY_WEBHOOK_URL_DEV!,\n      webhookSecret: process.env.LINDY_WEBHOOK_SECRET_DEV!,\n      workspace: 'dev',\n      model: 'gemini-flash', \u002F\u002F Cheap model for dev\n    },\n    staging: {\n      apiKey: process.env.LINDY_API_KEY_STAGING!,\n      webhookUrl: process.env.LINDY_WEBHOOK_URL_STAGING!,\n      webhookSecret: process.env.LINDY_WEBHOOK_SECRET_STAGING!,\n      workspace: 'staging',\n      model: 'claude-sonnet', \u002F\u002F Match prod model\n    },\n    production: {\n      apiKey: process.env.LINDY_API_KEY_PROD!,\n      webhookUrl: process.env.LINDY_WEBHOOK_URL_PROD!,\n      webhookSecret: process.env.LINDY_WEBHOOK_SECRET_PROD!,\n      workspace: 'production',\n      model: 'claude-sonnet',\n    },\n  };\n\n  const config = configs[env];\n  if (!config) throw new Error(`Unknown environment: ${env}`);\n  return config;\n}\n\nexport const lindyConfig = getLindyConfig();\n```\n\n### Step 3: Startup Validation\n```typescript\n\u002F\u002F validate-env.ts — Fail fast if Lindy config is missing\nimport { z } from 'zod';\n\nconst LindyEnvSchema = z.object({\n  LINDY_API_KEY: z.string().min(1, 'LINDY_API_KEY required'),\n  LINDY_WEBHOOK_SECRET: z.string().min(1, 'LINDY_WEBHOOK_SECRET required'),\n  LINDY_WEBHOOK_URL: z.string().url('LINDY_WEBHOOK_URL must be valid URL'),\n});\n\nexport function validateLindyEnv() {\n  const result = LindyEnvSchema.safeParse({\n    LINDY_API_KEY: process.env.LINDY_API_KEY,\n    LINDY_WEBHOOK_SECRET: process.env.LINDY_WEBHOOK_SECRET,\n    LINDY_WEBHOOK_URL: process.env.LINDY_WEBHOOK_URL,\n  });\n\n  if (!result.success) {\n    console.error('Lindy environment validation failed:');\n    result.error.issues.forEach(i => console.error(`  - ${i.path}: ${i.message}`));\n    process.exit(1);\n  }\n\n  console.log('Lindy environment validated successfully');\n}\n```\n\n### Step 4: Secret Management\n```bash\n# Development — .env.local (gitignored)\nLINDY_API_KEY=lnd_dev_xxxxxxxxxxxx\nLINDY_WEBHOOK_URL=https:\u002F\u002Fpublic.lindy.ai\u002Fapi\u002Fv1\u002Fwebhooks\u002Fdev-id\nLINDY_WEBHOOK_SECRET=whsec_dev_xxxxxxxxxxxx\n\n# Staging — CI\u002FCD secrets (GitHub Actions)\ngh secret set LINDY_API_KEY_STAGING --body \"lnd_staging_xxxx\"\ngh secret set LINDY_WEBHOOK_SECRET_STAGING --body \"whsec_staging_xxxx\"\n\n# Production — Cloud secret manager\n# AWS\naws secretsmanager create-secret \\\n  --name prod\u002Flindy\u002Fapi-key \\\n  --secret-string \"lnd_prod_xxxxxxxxxxxx\"\n\n# GCP\necho -n \"lnd_prod_xxxxxxxxxxxx\" | \\\n  gcloud secrets create lindy-api-key-prod --data-file=-\n```\n\n### Step 5: Agent Promotion (Dev to Staging to Prod)\n```\n1. Build and test agent in dev workspace\n2. Share agent as Template\n3. Import template into staging workspace\n4. Re-authorize integrations with staging accounts\n5. Update webhook URLs to staging endpoints\n6. Test with staging data for 24-48 hours\n7. Repeat for production workspace\n8. Update webhook URLs to production endpoints\n9. Verify all integrations authorized with production accounts\n```\n\n**Critical**: OAuth tokens, webhook URLs, and phone numbers do NOT transfer\nbetween workspaces. Each must be reconfigured per environment.\n\n### Step 6: CI\u002FCD Integration\n```yaml\n# .github\u002Fworkflows\u002Fdeploy.yml\njobs:\n  deploy-staging:\n    if: github.ref == 'refs\u002Fheads\u002Fdevelop'\n    environment: staging\n    env:\n      LINDY_API_KEY: ${{ secrets.LINDY_API_KEY_STAGING }}\n      LINDY_WEBHOOK_SECRET: ${{ secrets.LINDY_WEBHOOK_SECRET_STAGING }}\n    steps:\n      - run: npm run deploy:staging\n      - run: npm run test:lindy:smoke\n\n  deploy-prod:\n    if: github.ref == 'refs\u002Fheads\u002Fmain'\n    environment: production\n    env:\n      LINDY_API_KEY: ${{ secrets.LINDY_API_KEY_PROD }}\n      LINDY_WEBHOOK_SECRET: ${{ secrets.LINDY_WEBHOOK_SECRET_PROD }}\n    steps:\n      - run: npm run deploy:prod\n      - run: npm run test:lindy:smoke\n```\n\n## Error Handling\n\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Dev agent hits prod data | Shared workspace | Use separate workspaces per environment |\n| Staging integration fails | OAuth token expired | Re-authorize with staging service accounts |\n| Webhook URL mismatch | Dev URL in prod config | Validate webhook URLs at startup |\n| Secret not found in CI | Missing environment secret | Add via `gh secret set` per environment |\n\n## Resources\n- [Lindy Documentation](https:\u002F\u002Fdocs.lindy.ai)\n- [Lindy Templates](https:\u002F\u002Fdocs.lindy.ai\u002Ffundamentals\u002Flindy-101\u002Ftemplates)\n\n## Next Steps\nProceed to `lindy-observability` for monitoring and alerting.\n",{"name":5,"tags":24,"author":28,"license":15,"version":29,"description":30,"allowed-tools":31,"compatible-with":32},[25,26,27],"saas","lindy","deployment","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Configure Lindy AI across development, staging, and production environments.\nUse when setting up isolated workspaces, per-environment secrets,\nor environment-specific agent configurations.\nTrigger with phrases like \"lindy environments\", \"lindy staging\",\n\"lindy dev prod\", \"lindy environment setup\", \"lindy workspace isolation\".\n","Read, Write, Edit, Bash(aws:*), Bash(gcloud:*), Bash(vault:*)","claude-code, codex, openclaw","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--lindy-pack--lindy-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":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill lindy-multi-env-setup",{"tool":48,"command":49},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill lindy-multi-env-setup",{"tool":51,"command":52},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill lindy-multi-env-setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--lindy-pack--lindy-multi-env-setup\u002FSKILL.md",true,[],[57,64,71,78,85,93],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"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":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"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":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"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":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"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",[],[]]