[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H7JWT2PZCV4JVCYY7MTHEJ":3,"skill-same:01M6H7JWT2PZCV4JVCYY7MTHEJ":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},"01M6H7JWT2PZCV4JVCYY7MTHEJ","langfuse-multi-env-setup",null,"Configure Langfuse across development, staging, and production environments.\nUse when setting up multi-environment deployments, configuring per-environment keys,\nor implementing environment-specific Langfuse configurations.\nTrigger with phrases like \"langfuse environments\", \"langfuse staging\",\n\"langfuse dev prod\", \"langfuse environment setup\", \"langfuse config 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\u002Flangfuse-pack\u002Fskills\u002Flangfuse-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","langfuse","langfuse multi env setup","multi","env setup","env","up","implementing","environments","io","across","multi-environment","openclaw","edit","write","read","configure","Bash","code","config","2026-11-10 10:12:30",false,"---\nname: langfuse-multi-env-setup\ndescription: |\n  Configure Langfuse across development, staging, and production environments.\n  Use when setting up multi-environment deployments, configuring per-environment keys,\n  or implementing environment-specific Langfuse configurations.\n  Trigger with phrases like \"langfuse environments\", \"langfuse staging\",\n  \"langfuse dev prod\", \"langfuse environment setup\", \"langfuse config 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# Langfuse Multi-Environment Setup\n\n## Overview\nConfigure Langfuse across development, staging, and production environments with isolated API keys, environment-specific settings, and proper secret management. Each environment gets its own credentials and configuration to prevent cross-environment data leakage.\n\n## Prerequisites\n- Separate Langfuse API keys per environment\n- Secret management solution (environment variables, Vault, or cloud secrets)\n- CI\u002FCD pipeline with environment-aware deployment\n- Application with environment detection logic\n\n## Environment Strategy\n\n| Environment | Purpose | API Key Source | Settings |\n|-------------|---------|---------------|----------|\n| Development | Local development | `.env.local` | Debug enabled, relaxed limits |\n| Staging | Pre-production testing | CI\u002FCD secrets | Production-like settings |\n| Production | Live traffic | Secret manager | Optimized, hardened |\n\n## Instructions\n\n### Step 1: Configuration Structure\n```\nconfig\u002F\n  langfuse\u002F\n    base.ts           # Shared defaults\n    development.ts    # Dev overrides\n    staging.ts        # Staging overrides\n    production.ts     # Prod overrides\n    index.ts          # Environment resolver\n```\n\n### Step 2: Base Configuration\n```typescript\n\u002F\u002F config\u002Flangfuse\u002Fbase.ts\nexport const baseConfig = {\n  timeout: 30000,  # 30000: 30 seconds in ms\n  maxRetries: 3,\n  cache: {\n    enabled: true,\n    ttlSeconds: 300,  # 300: timeout: 5 minutes\n  },\n};\n```\n\n### Step 3: Environment-Specific Configs\n```typescript\n\u002F\u002F config\u002Flangfuse\u002Fdevelopment.ts\nimport { baseConfig } from \".\u002Fbase\";\n\nexport const developmentConfig = {\n  ...baseConfig,\n  apiKey: process.env.LANGFUSE_SECRET_KEY_DEV,\n  debug: true,\n  cache: { enabled: false, ttlSeconds: 60 },\n};\n\n\u002F\u002F config\u002Flangfuse\u002Fstaging.ts\nimport { baseConfig } from \".\u002Fbase\";\n\nexport const stagingConfig = {\n  ...baseConfig,\n  apiKey: process.env.LANGFUSE_SECRET_KEY_STAGING,\n  debug: false,\n};\n\n\u002F\u002F config\u002Flangfuse\u002Fproduction.ts\nimport { baseConfig } from \".\u002Fbase\";\n\nexport const productionConfig = {\n  ...baseConfig,\n  apiKey: process.env.LANGFUSE_SECRET_KEY_PROD,\n  debug: false,\n  timeout: 60000,  # 60000: 1 minute in ms\n  maxRetries: 5,\n  cache: { enabled: true, ttlSeconds: 600 },  # 600: timeout: 10 minutes\n};\n```\n\n### Step 4: Environment Resolver\n```typescript\n\u002F\u002F config\u002Flangfuse\u002Findex.ts\nimport { developmentConfig } from \".\u002Fdevelopment\";\nimport { stagingConfig } from \".\u002Fstaging\";\nimport { productionConfig } from \".\u002Fproduction\";\n\ntype Environment = \"development\" | \"staging\" | \"production\";\n\nconst configs = {\n  development: developmentConfig,\n  staging: stagingConfig,\n  production: productionConfig,\n};\n\nexport function detectEnvironment(): Environment {\n  const env = process.env.NODE_ENV || \"development\";\n  if (env === \"production\") return \"production\";\n  if (env === \"staging\" || process.env.VERCEL_ENV === \"preview\") return \"staging\";\n  return \"development\";\n}\n\nexport function getLangfuseConfig() {\n  const env = detectEnvironment();\n  const config = configs[env];\n\n  if (!config.apiKey) {\n    throw new Error(`LANGFUSE_SECRET_KEY not set for environment: ${env}`);\n  }\n\n  return { ...config, environment: env };\n}\n```\n\n### Step 5: Secret Management\n```bash\n# Local development (.env.local - git-ignored)\nLANGFUSE_SECRET_KEY_DEV=your-dev-key\n\n# GitHub Actions\n# Settings > Environments > staging\u002Fproduction > Secrets\n# Add LANGFUSE_SECRET_KEY_STAGING and LANGFUSE_SECRET_KEY_PROD\n\n# AWS Secrets Manager\naws secretsmanager create-secret \\\n  --name langfuse\u002Fproduction\u002Fapi-key \\\n  --secret-string \"your-prod-key\"\n\n# GCP Secret Manager\necho -n \"your-prod-key\" | gcloud secrets create langfuse-api-key-prod --data-file=-\n```\n\n```yaml\n# .github\u002Fworkflows\u002Fdeploy.yml\njobs:\n  deploy-staging:\n    environment: staging\n    env:\n      LANGFUSE_SECRET_KEY_STAGING: ${{ secrets.LANGFUSE_SECRET_KEY_STAGING }}\n\n  deploy-production:\n    environment: production\n    env:\n      LANGFUSE_SECRET_KEY_PROD: ${{ secrets.LANGFUSE_SECRET_KEY_PROD }}\n```\n\n## Error Handling\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Wrong environment | Missing NODE_ENV | Set environment variable in deployment |\n| Secret not found | Wrong secret path | Verify secret manager configuration |\n| Cross-env data leak | Shared API key | Use separate keys per environment |\n| Config validation fail | Missing field | Add startup validation with Zod schema |\n\n## Examples\n\n### Quick Environment Check\n```typescript\nconst config = getLangfuseConfig();\nconsole.log(`Running in ${config.environment}`);\nconsole.log(`Cache enabled: ${config.cache.enabled}`);\n```\n\n### Startup Validation\n```typescript\nimport { z } from \"zod\";\n\nconst configSchema = z.object({\n  apiKey: z.string().min(1, \"LANGFUSE_SECRET_KEY is required\"),\n  environment: z.enum([\"development\", \"staging\", \"production\"]),\n  timeout: z.number().positive(),\n});\n\nconst config = configSchema.parse(getLangfuseConfig());\n```\n\n## Resources\n- [Langfuse Documentation](https:\u002F\u002Flangfuse.com\u002Fdocs)\n- [Langfuse SDK](https:\u002F\u002Flangfuse.com\u002Fdocs\u002Fsdk)\n\n## Next Steps\nFor deployment, see `langfuse-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","# Langfuse Multi-Environment Setup\n\n## Overview\nConfigure Langfuse across development, staging, and production environments with isolated API keys, environment-specific settings, and proper secret management. Each environment gets its own credentials and configuration to prevent cross-environment data leakage.\n\n## Prerequisites\n- Separate Langfuse API keys per environment\n- Secret management solution (environment variables, Vault, or cloud secrets)\n- CI\u002FCD pipeline with environment-aware deployment\n- Application with environment detection logic\n\n## Environment Strategy\n\n| Environment | Purpose | API Key Source | Settings |\n|-------------|---------|---------------|----------|\n| Development | Local development | `.env.local` | Debug enabled, relaxed limits |\n| Staging | Pre-production testing | CI\u002FCD secrets | Production-like settings |\n| Production | Live traffic | Secret manager | Optimized, hardened |\n\n## Instructions\n\n### Step 1: Configuration Structure\n```\nconfig\u002F\n  langfuse\u002F\n    base.ts           # Shared defaults\n    development.ts    # Dev overrides\n    staging.ts        # Staging overrides\n    production.ts     # Prod overrides\n    index.ts          # Environment resolver\n```\n\n### Step 2: Base Configuration\n```typescript\n\u002F\u002F config\u002Flangfuse\u002Fbase.ts\nexport const baseConfig = {\n  timeout: 30000,  # 30000: 30 seconds in ms\n  maxRetries: 3,\n  cache: {\n    enabled: true,\n    ttlSeconds: 300,  # 300: timeout: 5 minutes\n  },\n};\n```\n\n### Step 3: Environment-Specific Configs\n```typescript\n\u002F\u002F config\u002Flangfuse\u002Fdevelopment.ts\nimport { baseConfig } from \".\u002Fbase\";\n\nexport const developmentConfig = {\n  ...baseConfig,\n  apiKey: process.env.LANGFUSE_SECRET_KEY_DEV,\n  debug: true,\n  cache: { enabled: false, ttlSeconds: 60 },\n};\n\n\u002F\u002F config\u002Flangfuse\u002Fstaging.ts\nimport { baseConfig } from \".\u002Fbase\";\n\nexport const stagingConfig = {\n  ...baseConfig,\n  apiKey: process.env.LANGFUSE_SECRET_KEY_STAGING,\n  debug: false,\n};\n\n\u002F\u002F config\u002Flangfuse\u002Fproduction.ts\nimport { baseConfig } from \".\u002Fbase\";\n\nexport const productionConfig = {\n  ...baseConfig,\n  apiKey: process.env.LANGFUSE_SECRET_KEY_PROD,\n  debug: false,\n  timeout: 60000,  # 60000: 1 minute in ms\n  maxRetries: 5,\n  cache: { enabled: true, ttlSeconds: 600 },  # 600: timeout: 10 minutes\n};\n```\n\n### Step 4: Environment Resolver\n```typescript\n\u002F\u002F config\u002Flangfuse\u002Findex.ts\nimport { developmentConfig } from \".\u002Fdevelopment\";\nimport { stagingConfig } from \".\u002Fstaging\";\nimport { productionConfig } from \".\u002Fproduction\";\n\ntype Environment = \"development\" | \"staging\" | \"production\";\n\nconst configs = {\n  development: developmentConfig,\n  staging: stagingConfig,\n  production: productionConfig,\n};\n\nexport function detectEnvironment(): Environment {\n  const env = process.env.NODE_ENV || \"development\";\n  if (env === \"production\") return \"production\";\n  if (env === \"staging\" || process.env.VERCEL_ENV === \"preview\") return \"staging\";\n  return \"development\";\n}\n\nexport function getLangfuseConfig() {\n  const env = detectEnvironment();\n  const config = configs[env];\n\n  if (!config.apiKey) {\n    throw new Error(`LANGFUSE_SECRET_KEY not set for environment: ${env}`);\n  }\n\n  return { ...config, environment: env };\n}\n```\n\n### Step 5: Secret Management\n```bash\n# Local development (.env.local - git-ignored)\nLANGFUSE_SECRET_KEY_DEV=your-dev-key\n\n# GitHub Actions\n# Settings > Environments > staging\u002Fproduction > Secrets\n# Add LANGFUSE_SECRET_KEY_STAGING and LANGFUSE_SECRET_KEY_PROD\n\n# AWS Secrets Manager\naws secretsmanager create-secret \\\n  --name langfuse\u002Fproduction\u002Fapi-key \\\n  --secret-string \"your-prod-key\"\n\n# GCP Secret Manager\necho -n \"your-prod-key\" | gcloud secrets create langfuse-api-key-prod --data-file=-\n```\n\n```yaml\n# .github\u002Fworkflows\u002Fdeploy.yml\njobs:\n  deploy-staging:\n    environment: staging\n    env:\n      LANGFUSE_SECRET_KEY_STAGING: ${{ secrets.LANGFUSE_SECRET_KEY_STAGING }}\n\n  deploy-production:\n    environment: production\n    env:\n      LANGFUSE_SECRET_KEY_PROD: ${{ secrets.LANGFUSE_SECRET_KEY_PROD }}\n```\n\n## Error Handling\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Wrong environment | Missing NODE_ENV | Set environment variable in deployment |\n| Secret not found | Wrong secret path | Verify secret manager configuration |\n| Cross-env data leak | Shared API key | Use separate keys per environment |\n| Config validation fail | Missing field | Add startup validation with Zod schema |\n\n## Examples\n\n### Quick Environment Check\n```typescript\nconst config = getLangfuseConfig();\nconsole.log(`Running in ${config.environment}`);\nconsole.log(`Cache enabled: ${config.cache.enabled}`);\n```\n\n### Startup Validation\n```typescript\nimport { z } from \"zod\";\n\nconst configSchema = z.object({\n  apiKey: z.string().min(1, \"LANGFUSE_SECRET_KEY is required\"),\n  environment: z.enum([\"development\", \"staging\", \"production\"]),\n  timeout: z.number().positive(),\n});\n\nconst config = configSchema.parse(getLangfuseConfig());\n```\n\n## Resources\n- [Langfuse Documentation](https:\u002F\u002Flangfuse.com\u002Fdocs)\n- [Langfuse SDK](https:\u002F\u002Flangfuse.com\u002Fdocs\u002Fsdk)\n\n## Next Steps\nFor deployment, see `langfuse-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 Langfuse across development, staging, and production environments.\nUse when setting up multi-environment deployments, configuring per-environment keys,\nor implementing environment-specific Langfuse configurations.\nTrigger with phrases like \"langfuse environments\", \"langfuse staging\",\n\"langfuse dev prod\", \"langfuse environment setup\", \"langfuse config 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\u002Flangfuse-pack\u002Fskills\u002Flangfuse-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 langfuse-multi-env-setup",{"tool":61,"command":62},"bunx","bunx skills add micsapp\u002Fmicstec-skills --skill langfuse-multi-env-setup",{"tool":64,"command":65},"pnpm","pnpm dlx skills add micsapp\u002Fmicstec-skills --skill langfuse-multi-env-setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsaas-packs\u002Flangfuse-pack\u002Fskills\u002Flangfuse-multi-env-setup\u002FSKILL.md",true,[],[70,106,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,96,97,98,29,99,100,101,102,103,104,105],"architecture","azure","azure apim architecture","component","authentication","gateway","topology","Optimization","network","api","team","environment","workspaces","instances","selection","strategies","azure api management","mode","for",{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":120,"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",[112,113,116,119],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},{"categoryNo":114,"categoryName":115,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":117,"categoryName":118,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},[121,122,123,124,88,125,36,126,127,128,129,130,96,97,102,131,132,103,133,25],"deployment","apiops deployment","workflows","azure devops","infrastructure","infrastructure as code","actions","ci","github actions","github-actions","as","guides","CI\u002FCD",{"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,96,97,146,147,148,149,150,151,152,103,153,154,25,105],"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,96,149,166,88,121,167,168,169,170,97,171,103,172,173,174,104,105],"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,123,185,186,187,188,96,189,190,191,31,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"]