[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H6DDP2SB4BM5SH503DB6WC":3,"skill-same:01M6H6DDP2SB4BM5SH503DB6WC":69},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":54,"install":55,"resources":68},"01M6H6DDP2SB4BM5SH503DB6WC","exa-multi-env-setup",null,"Configure Exa neural search API across development, staging, and production environments.\nUse when setting up multi-environment search pipelines, managing API key isolation,\nor configuring caching and result limits per deployment tier.\nTrigger with phrases like \"exa environments\", \"exa staging\", \"exa dev prod\",\n\"exa environment setup\", \"exa api key by env\".","micsapp\u002Fmicstec-skills","micsapp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F82411001?v=4","01M6GWCFQ6D3PV8EHNY62NN5VW","01M6GWCFVE1PA5HG0DKC7AMFJ3",4,"MIT","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsaas-packs\u002Fexa-pack\u002Fskills\u002Fexa-multi-env-setup\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"setup","exa multi env setup","multi","env setup","env","exa","configure","read","write","edit","up","multi-environment","Bash","caching","across","api","io","search","code","openclaw","2026-11-10 10:12:30",false,"---\nname: exa-multi-env-setup\ndescription: |\n  Configure Exa neural search API across development, staging, and production environments.\n  Use when setting up multi-environment search pipelines, managing API key isolation,\n  or configuring caching and result limits per deployment tier.\n  Trigger with phrases like \"exa environments\", \"exa staging\", \"exa dev prod\",\n  \"exa environment setup\", \"exa api key by env\".\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\n---\n# Exa Multi-Environment Setup\n\n## Overview\nExa's neural search API (`api.exa.ai`) charges per search request. Multi-environment setup focuses on API key isolation, request caching to reduce costs in staging\u002Fproduction, and controlling `numResults` and `text.maxCharacters` per environment (higher values cost more).\n\n## Prerequisites\n- Exa API key(s) from dashboard.exa.ai\n- `exa-js` npm package (`npm install exa-js`)\n- Optional: Redis for search result caching in staging\u002Fproduction\n\n## Environment Strategy\n\n| Environment | Key Isolation | numResults | Cache TTL | Rate Limit |\n|-------------|---------------|------------|-----------|------------|\n| Development | Shared dev key | 3 (low cost) | None | Low |\n| Staging | Staging key | 5 | 5 minutes | Moderate |\n| Production | Prod key | 5-10 per query | 1 hour | Full |\n\n## Instructions\n\n### Step 1: Configuration Structure\n```typescript\n\u002F\u002F config\u002Fexa.ts\nimport Exa from \"exa-js\";\n\ntype Env = \"development\" | \"staging\" | \"production\";\n\ninterface ExaConfig {\n  apiKey: string;\n  defaultNumResults: number;\n  maxCharacters: number;       \u002F\u002F per result content length\n  cacheEnabled: boolean;\n  cacheTtlSeconds: number;\n}\n\nconst configs: Record\u003CEnv, ExaConfig> = {\n  development: {\n    apiKey: process.env.EXA_API_KEY!,\n    defaultNumResults: 3,       \u002F\u002F fewer results = lower cost in dev\n    maxCharacters: 500,  # HTTP 500 Internal Server Error\n    cacheEnabled: false,        \u002F\u002F don't bother caching in dev\n    cacheTtlSeconds: 0,\n  },\n  staging: {\n    apiKey: process.env.EXA_API_KEY_STAGING!,\n    defaultNumResults: 5,\n    maxCharacters: 1000,  # 1000: 1 second in ms\n    cacheEnabled: true,\n    cacheTtlSeconds: 300,       \u002F\u002F 5-minute cache in staging  # 300: timeout: 5 minutes\n  },\n  production: {\n    apiKey: process.env.EXA_API_KEY_PROD!,\n    defaultNumResults: 5,\n    maxCharacters: 1000,  # 1 second in ms\n    cacheEnabled: true,\n    cacheTtlSeconds: 3600,      \u002F\u002F 1-hour cache for repeated queries  # 3600: timeout: 1 hour\n  },\n};\n\nexport function getExaConfig(): ExaConfig {\n  const env = (process.env.NODE_ENV || \"development\") as Env;\n  const config = configs[env] || configs.development;\n  if (!config.apiKey) {\n    throw new Error(`EXA_API_KEY not set for ${env} environment`);\n  }\n  return config;\n}\n\nexport function getExaClient(): Exa {\n  return new Exa(getExaConfig().apiKey);\n}\n```\n\n### Step 2: Search Service with Caching\n```typescript\n\u002F\u002F lib\u002Fexa-search.ts\nimport { getExaClient, getExaConfig } from \"..\u002Fconfig\u002Fexa\";\nimport { Redis } from \"ioredis\";\n\nconst redis = process.env.REDIS_URL ? new Redis(process.env.REDIS_URL) : null;\n\nexport async function search(query: string, numResults?: number) {\n  const exa = getExaClient();\n  const cfg = getExaConfig();\n  const n = numResults ?? cfg.defaultNumResults;\n\n  \u002F\u002F Check cache if enabled\n  if (cfg.cacheEnabled && redis) {\n    const cacheKey = `exa:${Buffer.from(`${query}:${n}`).toString(\"base64\")}`;\n    const cached = await redis.get(cacheKey);\n    if (cached) return JSON.parse(cached);\n\n    const results = await exa.searchAndContents(query, {\n      type: \"neural\",\n      numResults: n,\n      text: { maxCharacters: cfg.maxCharacters },\n    });\n\n    await redis.set(cacheKey, JSON.stringify(results), \"EX\", cfg.cacheTtlSeconds);\n    return results;\n  }\n\n  return exa.searchAndContents(query, {\n    type: \"neural\",\n    numResults: n,\n    text: { maxCharacters: cfg.maxCharacters },\n  });\n}\n```\n\n### Step 3: Environment Variable Setup\n```bash\n# .env.local (development)\nEXA_API_KEY=exa-dev-abc123\n\n# GitHub Actions - Staging\nEXA_API_KEY_STAGING=exa-staging-def456\n\n# GitHub Actions - Production\nEXA_API_KEY_PROD=exa-prod-xyz789\nREDIS_URL=redis:\u002F\u002Fprod-redis:6379  # 6379: Redis port\n```\n\n### Step 4: Health Check Per Environment\n```typescript\n\u002F\u002F lib\u002Fexa-health.ts\nexport async function checkExaHealth(): Promise\u003C{ status: string; env: string }> {\n  try {\n    const exa = getExaClient();\n    await exa.search(\"test connectivity\", { numResults: 1 });\n    return { status: \"healthy\", env: process.env.NODE_ENV || \"development\" };\n  } catch (err: any) {\n    return { status: \"unhealthy\", env: process.env.NODE_ENV || \"development\" };\n  }\n}\n```\n\n### Step 5: CI\u002FCD Configuration\n```yaml\n# .github\u002Fworkflows\u002Fdeploy.yml\njobs:\n  deploy-staging:\n    environment: staging\n    env:\n      EXA_API_KEY_STAGING: ${{ secrets.EXA_API_KEY_STAGING }}\n      NODE_ENV: staging\n    steps:\n      - run: npm run build && npm run deploy:staging\n\n  deploy-production:\n    environment: production\n    env:\n      EXA_API_KEY_PROD: ${{ secrets.EXA_API_KEY_PROD }}\n      NODE_ENV: production\n    steps:\n      - run: npm run deploy:prod\n```\n\n## Error Handling\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| `401 Unauthorized` | Wrong API key for environment | Verify `EXA_API_KEY` in env vars |\n| `429 rate_limit_exceeded` | Too many requests | Implement caching and request queuing |\n| High API costs in staging | No caching enabled | Enable Redis cache with 5-minute TTL |\n| Empty results | Query too narrow | Broaden query terms for neural search |\n\n## Examples\n\n### Check Active Configuration\n```typescript\nimport { getExaConfig } from \".\u002Fconfig\u002Fexa\";\n\nconst cfg = getExaConfig();\nconsole.log(`Results per query: ${cfg.defaultNumResults}`);\nconsole.log(`Cache enabled: ${cfg.cacheEnabled}, TTL: ${cfg.cacheTtlSeconds}s`);\n```\n\n## Resources\n- [Exa API Documentation](https:\u002F\u002Fdocs.exa.ai)\n- [Exa JavaScript SDK](https:\u002F\u002Fgithub.com\u002Fexa-labs\u002Fexa-js)\n- [Exa Pricing](https:\u002F\u002Fexa.ai\u002Fpricing)\n\n## Next Steps\nFor deployment configuration, see `exa-deploy-integration`.\n\n## Output\n\n- Configuration files or code changes applied to the project\n- Validation report confirming correct implementation\n- Summary of changes made and their rationale","# Exa Multi-Environment Setup\n\n## Overview\nExa's neural search API (`api.exa.ai`) charges per search request. Multi-environment setup focuses on API key isolation, request caching to reduce costs in staging\u002Fproduction, and controlling `numResults` and `text.maxCharacters` per environment (higher values cost more).\n\n## Prerequisites\n- Exa API key(s) from dashboard.exa.ai\n- `exa-js` npm package (`npm install exa-js`)\n- Optional: Redis for search result caching in staging\u002Fproduction\n\n## Environment Strategy\n\n| Environment | Key Isolation | numResults | Cache TTL | Rate Limit |\n|-------------|---------------|------------|-----------|------------|\n| Development | Shared dev key | 3 (low cost) | None | Low |\n| Staging | Staging key | 5 | 5 minutes | Moderate |\n| Production | Prod key | 5-10 per query | 1 hour | Full |\n\n## Instructions\n\n### Step 1: Configuration Structure\n```typescript\n\u002F\u002F config\u002Fexa.ts\nimport Exa from \"exa-js\";\n\ntype Env = \"development\" | \"staging\" | \"production\";\n\ninterface ExaConfig {\n  apiKey: string;\n  defaultNumResults: number;\n  maxCharacters: number;       \u002F\u002F per result content length\n  cacheEnabled: boolean;\n  cacheTtlSeconds: number;\n}\n\nconst configs: Record\u003CEnv, ExaConfig> = {\n  development: {\n    apiKey: process.env.EXA_API_KEY!,\n    defaultNumResults: 3,       \u002F\u002F fewer results = lower cost in dev\n    maxCharacters: 500,  # HTTP 500 Internal Server Error\n    cacheEnabled: false,        \u002F\u002F don't bother caching in dev\n    cacheTtlSeconds: 0,\n  },\n  staging: {\n    apiKey: process.env.EXA_API_KEY_STAGING!,\n    defaultNumResults: 5,\n    maxCharacters: 1000,  # 1000: 1 second in ms\n    cacheEnabled: true,\n    cacheTtlSeconds: 300,       \u002F\u002F 5-minute cache in staging  # 300: timeout: 5 minutes\n  },\n  production: {\n    apiKey: process.env.EXA_API_KEY_PROD!,\n    defaultNumResults: 5,\n    maxCharacters: 1000,  # 1 second in ms\n    cacheEnabled: true,\n    cacheTtlSeconds: 3600,      \u002F\u002F 1-hour cache for repeated queries  # 3600: timeout: 1 hour\n  },\n};\n\nexport function getExaConfig(): ExaConfig {\n  const env = (process.env.NODE_ENV || \"development\") as Env;\n  const config = configs[env] || configs.development;\n  if (!config.apiKey) {\n    throw new Error(`EXA_API_KEY not set for ${env} environment`);\n  }\n  return config;\n}\n\nexport function getExaClient(): Exa {\n  return new Exa(getExaConfig().apiKey);\n}\n```\n\n### Step 2: Search Service with Caching\n```typescript\n\u002F\u002F lib\u002Fexa-search.ts\nimport { getExaClient, getExaConfig } from \"..\u002Fconfig\u002Fexa\";\nimport { Redis } from \"ioredis\";\n\nconst redis = process.env.REDIS_URL ? new Redis(process.env.REDIS_URL) : null;\n\nexport async function search(query: string, numResults?: number) {\n  const exa = getExaClient();\n  const cfg = getExaConfig();\n  const n = numResults ?? cfg.defaultNumResults;\n\n  \u002F\u002F Check cache if enabled\n  if (cfg.cacheEnabled && redis) {\n    const cacheKey = `exa:${Buffer.from(`${query}:${n}`).toString(\"base64\")}`;\n    const cached = await redis.get(cacheKey);\n    if (cached) return JSON.parse(cached);\n\n    const results = await exa.searchAndContents(query, {\n      type: \"neural\",\n      numResults: n,\n      text: { maxCharacters: cfg.maxCharacters },\n    });\n\n    await redis.set(cacheKey, JSON.stringify(results), \"EX\", cfg.cacheTtlSeconds);\n    return results;\n  }\n\n  return exa.searchAndContents(query, {\n    type: \"neural\",\n    numResults: n,\n    text: { maxCharacters: cfg.maxCharacters },\n  });\n}\n```\n\n### Step 3: Environment Variable Setup\n```bash\n# .env.local (development)\nEXA_API_KEY=exa-dev-abc123\n\n# GitHub Actions - Staging\nEXA_API_KEY_STAGING=exa-staging-def456\n\n# GitHub Actions - Production\nEXA_API_KEY_PROD=exa-prod-xyz789\nREDIS_URL=redis:\u002F\u002Fprod-redis:6379  # 6379: Redis port\n```\n\n### Step 4: Health Check Per Environment\n```typescript\n\u002F\u002F lib\u002Fexa-health.ts\nexport async function checkExaHealth(): Promise\u003C{ status: string; env: string }> {\n  try {\n    const exa = getExaClient();\n    await exa.search(\"test connectivity\", { numResults: 1 });\n    return { status: \"healthy\", env: process.env.NODE_ENV || \"development\" };\n  } catch (err: any) {\n    return { status: \"unhealthy\", env: process.env.NODE_ENV || \"development\" };\n  }\n}\n```\n\n### Step 5: CI\u002FCD Configuration\n```yaml\n# .github\u002Fworkflows\u002Fdeploy.yml\njobs:\n  deploy-staging:\n    environment: staging\n    env:\n      EXA_API_KEY_STAGING: ${{ secrets.EXA_API_KEY_STAGING }}\n      NODE_ENV: staging\n    steps:\n      - run: npm run build && npm run deploy:staging\n\n  deploy-production:\n    environment: production\n    env:\n      EXA_API_KEY_PROD: ${{ secrets.EXA_API_KEY_PROD }}\n      NODE_ENV: production\n    steps:\n      - run: npm run deploy:prod\n```\n\n## Error Handling\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| `401 Unauthorized` | Wrong API key for environment | Verify `EXA_API_KEY` in env vars |\n| `429 rate_limit_exceeded` | Too many requests | Implement caching and request queuing |\n| High API costs in staging | No caching enabled | Enable Redis cache with 5-minute TTL |\n| Empty results | Query too narrow | Broaden query terms for neural search |\n\n## Examples\n\n### Check Active Configuration\n```typescript\nimport { getExaConfig } from \".\u002Fconfig\u002Fexa\";\n\nconst cfg = getExaConfig();\nconsole.log(`Results per query: ${cfg.defaultNumResults}`);\nconsole.log(`Cache enabled: ${cfg.cacheEnabled}, TTL: ${cfg.cacheTtlSeconds}s`);\n```\n\n## Resources\n- [Exa API Documentation](https:\u002F\u002Fdocs.exa.ai)\n- [Exa JavaScript SDK](https:\u002F\u002Fgithub.com\u002Fexa-labs\u002Fexa-js)\n- [Exa Pricing](https:\u002F\u002Fexa.ai\u002Fpricing)\n\n## Next Steps\nFor deployment configuration, see `exa-deploy-integration`.\n\n## Output\n\n- Configuration files or code changes applied to the project\n- Validation report confirming correct implementation\n- Summary of changes made and their rationale",{"name":5,"author":43,"license":14,"version":44,"description":45,"allowed-tools":46,"compatible-with":47},"Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Configure Exa neural search API across development, staging, and production environments.\nUse when setting up multi-environment search pipelines, managing API key isolation,\nor configuring caching and result limits per deployment tier.\nTrigger with phrases like \"exa environments\", \"exa staging\", \"exa dev prod\",\n\"exa environment setup\", \"exa api key by env\".\n","Read, Write, Edit, Bash(aws:*), Bash(gcloud:*), Bash(vault:*)","claude-code, codex, openclaw","master","3f5d983eb4ef375b749adcd6b07ec03bd82ae8a8","claude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsaas-packs\u002Fexa-pack\u002Fskills\u002Fexa-multi-env-setup",0,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills","https:\u002F\u002Fgithub.com\u002Fmicsapp","2026-03-20 11:24:18",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add micsapp\u002Fmicstec-skills --skill exa-multi-env-setup",{"tool":61,"command":62},"bunx","bunx skills add micsapp\u002Fmicstec-skills --skill exa-multi-env-setup",{"tool":64,"command":65},"pnpm","pnpm dlx skills add micsapp\u002Fmicstec-skills --skill exa-multi-env-setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsaas-packs\u002Fexa-pack\u002Fskills\u002Fexa-multi-env-setup\u002FSKILL.md",true,[],[70,105,134,155,175,199],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":86,"publishedAt":38},"01M6HBTJ02FXBFG9NYEHHYAP52","azure-apim-architecture","Analyzes and explains Azure API Management architecture decisions for enterprise API marketplace implementations using VNet Internal mode, Front Door, hybrid authentication, and multi-environment strategies. Use when discussing APIM component selection, network topology, cost optimization, or comparing alternatives like workspaces vs instances, VNet Internal vs External mode, or Front Door vs Application Gateway.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fazure-apim-architecture\u002FSKILL.md",[76,81],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[87,88,89,90,91,92,93,94,95,33,96,97,29,98,99,100,101,102,103,104],"architecture","azure","azure apim architecture","component","authentication","gateway","topology","Optimization","network","team","environment","workspaces","instances","selection","strategies","azure api management","mode","for",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":119,"publishedAt":38},"01M6HBT7J4H082JEEA670B3EQ9","apiops-deployment","Guides deployment of Azure API Management infrastructure using Infrastructure as Code (Bicep\u002FTerraform), CI\u002FCD pipelines (GitHub Actions\u002FAzure DevOps), and APIOps workflows. Use when deploying APIM, creating pipelines, or implementing dev→test→prod promotion strategies.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapiops-deployment\u002FSKILL.md",[111,112,115,118],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},{"categoryNo":113,"categoryName":114,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":116,"categoryName":117,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},[120,121,122,123,88,124,36,125,126,127,128,129,33,96,101,130,131,102,132,133],"deployment","apiops deployment","workflows","azure devops","infrastructure","infrastructure as code","actions","ci","github actions","github-actions","as","guides","CI\u002FCD","implementing",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":141,"publishedAt":38},"01M6HBT2HEA23THNE9E00GYQBE","apim-policy-authoring","Creates production-ready Azure API Management policy XML for authentication (OAuth 2.0, JWT validation, subscription keys), rate limiting, CORS configuration, error handling, and API transformations. Use when implementing API security, access control, or request\u002Fresponse processing logic.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapim-policy-authoring\u002FSKILL.md",[140],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},[142,143,144,145,88,91,33,96,146,147,148,149,150,151,152,102,153,154,133,104],"policy","authoring","apim policy authoring","security","access","use","ready","api security","Access Control","error","processing","cors configuration","production-ready",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":163,"publishedAt":38},"01M6HBSY65SB29J9WE9KYD0K6T","api-security-review","Reviews Azure API Management configurations for security vulnerabilities, OWASP API Security Top 10 compliance, VNet Internal mode validation, Private Link verification, and Azure Security Benchmark alignment. Use when performing security audits, pre-deployment validation, or compliance reviews.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapi-security-review\u002FSKILL.md",[161,162],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},[164,145,165,33,149,166,88,120,167,168,169,170,96,171,102,172,173,174,103,104],"review","security review","api security review","benchmark","verification","owasp","owasp-api","alignment","azure security","reviews","top",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":181,"publishedAt":38},"01M6HBSRW4PDFE6K4F8JYPZQ05","jira-cli","Interact with Jira from the command line to create, list, view, edit, and transition issues, manage sprints and epics, and perform common Jira workflows. Use when the user asks about Jira tasks, tickets, issues, sprints, or needs to manage project work items.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fawesome-copilot-agents\u002Fskills\u002Fjira-cli\u002FSKILL.md",[],[182,183,184,122,185,186,187,188,33,189,190,191,27,192,193,194,195,196,197,198],"cli","jira","jira cli","init","tasks","create","issues","common","work","command","list","view","project","project work","token","line","sprints",{"skillNo":200,"name":201,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":203,"categories":204,"keywords":205,"publishedAt":38},"01M6HBSNS3JHMW603G47TWE31H","calculator","Performs arbitrary-precision arithmetic calculations including addition, subtraction, multiplication, division, and exponents. Use when the user asks to calculate, compute, or evaluate math expressions, or when precise decimal arithmetic is needed to avoid floating-point errors.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fawesome-copilot-agents\u002Fskills\u002Fcalculator\u002FSKILL.md",[],[201,206,207,208,209,210,211,147,212,213],"npm","js","calculate","node","math","user","compute","errors"]