[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H6SFHTBXM8DV3XTJDZDH82":3,"skill-same:01M6H6SFHTBXM8DV3XTJDZDH82":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},"01M6H6SFHTBXM8DV3XTJDZDH82","granola-multi-env-setup",null,"Configure Granola across multiple workspaces and team environments.\nUse when setting up multi-team deployments, configuring workspace hierarchies,\nor managing enterprise-scale Granola installations.\nTrigger with phrases like \"granola workspaces\", \"granola multi-team\",\n\"granola environments\", \"granola organization\", \"granola multi-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\u002Fgranola-pack\u002Fskills\u002Fgranola-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","granola multi env setup","multi","env setup","env","granola","write","edit","up","workspaces","read","organization","across","configure","io","trigger","team","code","openclaw","environments","2026-11-10 10:12:30",false,"---\nname: granola-multi-env-setup\ndescription: |\n  Configure Granola across multiple workspaces and team environments.\n  Use when setting up multi-team deployments, configuring workspace hierarchies,\n  or managing enterprise-scale Granola installations.\n  Trigger with phrases like \"granola workspaces\", \"granola multi-team\",\n  \"granola environments\", \"granola organization\", \"granola multi-env\".\nallowed-tools: Read, Write, Edit\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\n---\n# Granola Multi-Environment Setup\n\n## Overview\nConfigure Granola for multi-workspace and multi-team enterprise deployments.\n\n## Prerequisites\n- Granola Business or Enterprise plan\n- Organization admin access\n- Team structure defined\n- SSO configured (recommended)\n\n## Workspace Architecture\n\n### Workspace Hierarchy\n```\nOrganization (acme-corp)\n├── Corporate Workspace\n│   ├── Settings: Strictest privacy\n│   ├── Access: Executive team only\n│   └── Integrations: Private Notion\n├── Engineering Workspace\n│   ├── Settings: Team sharing\n│   ├── Access: Engineering org\n│   └── Integrations: Linear, GitHub\n├── Sales Workspace\n│   ├── Settings: CRM sync enabled\n│   ├── Access: Sales + Success\n│   └── Integrations: HubSpot, Gong\n├── Customer Success Workspace\n│   ├── Settings: CRM sync enabled\n│   ├── Access: CS team\n│   └── Integrations: HubSpot, Zendesk\n└── HR Workspace\n    ├── Settings: Confidential\n    ├── Access: HR only\n    └── Integrations: Greenhouse\n```\n\n## Workspace Creation\n\n### Step 1: Plan Workspace Structure\n```markdown\n## Workspace Planning Template\n\nFor each workspace, define:\n- Name: [Workspace Name]\n- Purpose: [Primary use case]\n- Owner: [Admin name\u002Femail]\n- Members: [Group or individuals]\n- Access Level: [Public\u002FPrivate\u002FConfidential]\n- Integrations: [List required]\n- Templates: [Shared\u002FCustom]\n- Retention: [Days\u002FMonths\u002FForever]\n```\n\n### Step 2: Create Workspaces\n```markdown\n## Workspace Creation\n\n1. Organization Settings > Workspaces\n2. Click \"Create Workspace\"\n3. Configure:\n   - Name: Engineering\n   - Slug: engineering\n   - Description: Engineering team meetings\n   - Owner: eng-lead@company.com\n4. Save and proceed to settings\n```\n\n### Step 3: Configure Per-Workspace Settings\n```yaml\n# Engineering Workspace Settings\nWorkspace: Engineering\n\nPrivacy:\n  default_sharing: team\n  external_sharing: disabled\n  transcript_access: members_only\n\nIntegrations:\n  - Slack: #dev-meetings channel\n  - Linear: Auto-create tasks\n  - Notion: Engineering wiki database\n  - GitHub: Link PRs in notes\n\nTemplates:\n  - Sprint Planning\n  - Code Review\n  - Tech Design\n  - 1:1 Engineering\n\nRetention:\n  notes: 1 year\n  transcripts: 90 days\n  audio: 7 days\n\nPermissions:\n  - Admins: Full access\n  - Members: Create, edit own\n  - Viewers: Read only (for PMs)\n```\n\n## User Management\n\n### User Provisioning\n```markdown\n## Provisioning Methods\n\nManual:\n1. Settings > Members\n2. Invite by email\n3. Assign to workspace(s)\n4. Set role\n\nSSO\u002FSCIM:\n1. Configure SSO provider\n2. Enable SCIM provisioning\n3. Map groups to workspaces\n4. Roles assigned by group\n\nJIT (Just-in-Time):\n1. Enable JIT provisioning\n2. User signs in via SSO\n3. Auto-added to default workspace\n4. Upgrade as needed\n```\n\n### Role Definitions\n| Role | Permissions | Use Case |\n|------|------------|----------|\n| Owner | Full admin + billing | Organization owner |\n| Admin | Workspace management | Team leads |\n| Member | Create + edit notes | Regular users |\n| Viewer | Read only | Stakeholders |\n| Guest | Single workspace | Contractors |\n\n### Group Mappings\n```yaml\n# SSO Group → Granola Workspace Mapping\n\nSSO Groups:\n  engineering-team:\n    workspace: Engineering\n    role: member\n\n  engineering-leads:\n    workspace: Engineering\n    role: admin\n\n  sales-team:\n    workspace: Sales\n    role: member\n\n  all-employees:\n    workspace: General\n    role: member\n```\n\n## Integration Per Environment\n\n### Environment-Specific Integrations\n```yaml\n# Production Environment\nEnvironment: Production\n\nWorkspaces:\n  Sales:\n    hubspot:\n      portal_id: prod-12345  # port 12345 - example\u002Ftest\n      sync: bidirectional\n      auto_create: true\n    slack:\n      workspace: acme-corp\n      channel: #sales-meetings\n\n  Engineering:\n    linear:\n      team_id: ENG\n      auto_tasks: true\n    github:\n      org: acme-corp\n      repo_linking: true\n\n# Staging Environment (for testing)\nEnvironment: Staging\n\nWorkspaces:\n  Test-Sales:\n    hubspot:\n      portal_id: sandbox-67890  # 67890 = configured value\n      sync: unidirectional\n      auto_create: false\n```\n\n### Integration Testing\n```markdown\n## Pre-Production Testing\n\nFor each integration:\n1. [ ] Test in staging workspace\n2. [ ] Verify data flow\n3. [ ] Check permissions\n4. [ ] Validate error handling\n5. [ ] Document configuration\n6. [ ] Enable in production\n```\n\n## Cross-Workspace Features\n\n### Shared Templates\n```markdown\n## Organization Templates\n\nLocation: Organization Settings > Templates\n\nTemplate Sharing:\n- Organization-wide templates\n- Workspace-specific templates\n- Personal templates\n\nHierarchy:\nOrg Templates > Workspace Templates > Personal Templates\n\nAdministration:\n- Org templates: Org admins only\n- Workspace templates: Workspace admins\n- Personal: Individual users\n```\n\n### Cross-Workspace Search\n```markdown\n## Search Configuration\n\nEnable:\n1. Settings > Search > Cross-workspace search\n2. Select participating workspaces\n3. Configure access levels\n\nVisibility Rules:\n- Only sees notes they have access to\n- Respects workspace permissions\n- Excludes confidential workspaces\n```\n\n## Compliance Configuration\n\n### Per-Workspace Compliance\n```yaml\n# HR Workspace - Strict Compliance\nWorkspace: HR\n\nCompliance Settings:\n  data_residency: us-west-2\n  encryption: customer-managed-keys\n  audit_logging: enabled\n  retention:\n    override: 30 days\n    legal_hold: supported\n  sharing:\n    external: prohibited\n    download: restricted\n  access:\n    mfa_required: true\n    session_timeout: 4 hours\n```\n\n### Audit Configuration\n```markdown\n## Audit Log Settings\n\nEvents Logged:\n- User sign-in\u002Fout\n- Note created\u002Fedited\u002Fdeleted\n- Sharing changes\n- Export requests\n- Admin actions\n\nRetention: 2 years\nExport: Daily to SIEM\nFormat: JSON\nDestination: Splunk\u002FDatadog\n```\n\n## Environment Promotion\n\n### Staging to Production\n```markdown\n## Configuration Promotion\n\n1. Test in Staging Workspace\n   - Create test workspace\n   - Configure integrations\n   - Validate with sample data\n\n2. Document Configuration\n   - Export settings (JSON)\n   - Screenshot integrations\n   - Note manual steps\n\n3. Promote to Production\n   - Create production workspace\n   - Apply documented settings\n   - Re-authorize integrations\n   - Verify connections\n\n4. Validate\n   - Test meeting capture\n   - Verify integration flow\n   - Confirm permissions\n   - Monitor for 24 hours\n```\n\n## Troubleshooting Multi-Env\n\n### Common Issues\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| User in wrong workspace | SSO mapping error | Check group assignments |\n| Integration not syncing | Wrong environment config | Verify API keys |\n| Notes not visible | Permission mismatch | Check role assignment |\n| Cross-workspace search failing | Feature not enabled | Enable in org settings |\n\n## Resources\n- [Granola Enterprise Admin](https:\u002F\u002Fgranola.ai\u002Fadmin)\n- [SSO Configuration](https:\u002F\u002Fgranola.ai\u002Fhelp\u002Fsso)\n- [SCIM Provisioning](https:\u002F\u002Fgranola.ai\u002Fhelp\u002Fscim)\n\n## Next Steps\nProceed to `granola-observability` for monitoring and analytics.\n\n## Instructions\n\n1. Assess the current state of the deployment configuration\n2. Identify the specific requirements and constraints\n3. Apply the recommended patterns from this skill\n4. Validate the changes against expected behavior\n5. Document the configuration for team reference\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\n\n## Error Handling\n\n| Error | Cause | Resolution |\n|-------|-------|------------|\n| Authentication failure | Invalid or expired credentials | Refresh tokens or re-authenticate with deployment |\n| Configuration conflict | Incompatible settings detected | Review and resolve conflicting parameters |\n| Resource not found | Referenced resource missing | Verify resource exists and permissions are correct |\n\n## Examples\n\n**Basic usage**: Apply granola multi env setup to a standard project setup with default configuration options.\n\n**Advanced scenario**: Customize granola multi env setup for production environments with multiple constraints and team-specific requirements.","# Granola Multi-Environment Setup\n\n## Overview\nConfigure Granola for multi-workspace and multi-team enterprise deployments.\n\n## Prerequisites\n- Granola Business or Enterprise plan\n- Organization admin access\n- Team structure defined\n- SSO configured (recommended)\n\n## Workspace Architecture\n\n### Workspace Hierarchy\n```\nOrganization (acme-corp)\n├── Corporate Workspace\n│   ├── Settings: Strictest privacy\n│   ├── Access: Executive team only\n│   └── Integrations: Private Notion\n├── Engineering Workspace\n│   ├── Settings: Team sharing\n│   ├── Access: Engineering org\n│   └── Integrations: Linear, GitHub\n├── Sales Workspace\n│   ├── Settings: CRM sync enabled\n│   ├── Access: Sales + Success\n│   └── Integrations: HubSpot, Gong\n├── Customer Success Workspace\n│   ├── Settings: CRM sync enabled\n│   ├── Access: CS team\n│   └── Integrations: HubSpot, Zendesk\n└── HR Workspace\n    ├── Settings: Confidential\n    ├── Access: HR only\n    └── Integrations: Greenhouse\n```\n\n## Workspace Creation\n\n### Step 1: Plan Workspace Structure\n```markdown\n## Workspace Planning Template\n\nFor each workspace, define:\n- Name: [Workspace Name]\n- Purpose: [Primary use case]\n- Owner: [Admin name\u002Femail]\n- Members: [Group or individuals]\n- Access Level: [Public\u002FPrivate\u002FConfidential]\n- Integrations: [List required]\n- Templates: [Shared\u002FCustom]\n- Retention: [Days\u002FMonths\u002FForever]\n```\n\n### Step 2: Create Workspaces\n```markdown\n## Workspace Creation\n\n1. Organization Settings > Workspaces\n2. Click \"Create Workspace\"\n3. Configure:\n   - Name: Engineering\n   - Slug: engineering\n   - Description: Engineering team meetings\n   - Owner: eng-lead@company.com\n4. Save and proceed to settings\n```\n\n### Step 3: Configure Per-Workspace Settings\n```yaml\n# Engineering Workspace Settings\nWorkspace: Engineering\n\nPrivacy:\n  default_sharing: team\n  external_sharing: disabled\n  transcript_access: members_only\n\nIntegrations:\n  - Slack: #dev-meetings channel\n  - Linear: Auto-create tasks\n  - Notion: Engineering wiki database\n  - GitHub: Link PRs in notes\n\nTemplates:\n  - Sprint Planning\n  - Code Review\n  - Tech Design\n  - 1:1 Engineering\n\nRetention:\n  notes: 1 year\n  transcripts: 90 days\n  audio: 7 days\n\nPermissions:\n  - Admins: Full access\n  - Members: Create, edit own\n  - Viewers: Read only (for PMs)\n```\n\n## User Management\n\n### User Provisioning\n```markdown\n## Provisioning Methods\n\nManual:\n1. Settings > Members\n2. Invite by email\n3. Assign to workspace(s)\n4. Set role\n\nSSO\u002FSCIM:\n1. Configure SSO provider\n2. Enable SCIM provisioning\n3. Map groups to workspaces\n4. Roles assigned by group\n\nJIT (Just-in-Time):\n1. Enable JIT provisioning\n2. User signs in via SSO\n3. Auto-added to default workspace\n4. Upgrade as needed\n```\n\n### Role Definitions\n| Role | Permissions | Use Case |\n|------|------------|----------|\n| Owner | Full admin + billing | Organization owner |\n| Admin | Workspace management | Team leads |\n| Member | Create + edit notes | Regular users |\n| Viewer | Read only | Stakeholders |\n| Guest | Single workspace | Contractors |\n\n### Group Mappings\n```yaml\n# SSO Group → Granola Workspace Mapping\n\nSSO Groups:\n  engineering-team:\n    workspace: Engineering\n    role: member\n\n  engineering-leads:\n    workspace: Engineering\n    role: admin\n\n  sales-team:\n    workspace: Sales\n    role: member\n\n  all-employees:\n    workspace: General\n    role: member\n```\n\n## Integration Per Environment\n\n### Environment-Specific Integrations\n```yaml\n# Production Environment\nEnvironment: Production\n\nWorkspaces:\n  Sales:\n    hubspot:\n      portal_id: prod-12345  # port 12345 - example\u002Ftest\n      sync: bidirectional\n      auto_create: true\n    slack:\n      workspace: acme-corp\n      channel: #sales-meetings\n\n  Engineering:\n    linear:\n      team_id: ENG\n      auto_tasks: true\n    github:\n      org: acme-corp\n      repo_linking: true\n\n# Staging Environment (for testing)\nEnvironment: Staging\n\nWorkspaces:\n  Test-Sales:\n    hubspot:\n      portal_id: sandbox-67890  # 67890 = configured value\n      sync: unidirectional\n      auto_create: false\n```\n\n### Integration Testing\n```markdown\n## Pre-Production Testing\n\nFor each integration:\n1. [ ] Test in staging workspace\n2. [ ] Verify data flow\n3. [ ] Check permissions\n4. [ ] Validate error handling\n5. [ ] Document configuration\n6. [ ] Enable in production\n```\n\n## Cross-Workspace Features\n\n### Shared Templates\n```markdown\n## Organization Templates\n\nLocation: Organization Settings > Templates\n\nTemplate Sharing:\n- Organization-wide templates\n- Workspace-specific templates\n- Personal templates\n\nHierarchy:\nOrg Templates > Workspace Templates > Personal Templates\n\nAdministration:\n- Org templates: Org admins only\n- Workspace templates: Workspace admins\n- Personal: Individual users\n```\n\n### Cross-Workspace Search\n```markdown\n## Search Configuration\n\nEnable:\n1. Settings > Search > Cross-workspace search\n2. Select participating workspaces\n3. Configure access levels\n\nVisibility Rules:\n- Only sees notes they have access to\n- Respects workspace permissions\n- Excludes confidential workspaces\n```\n\n## Compliance Configuration\n\n### Per-Workspace Compliance\n```yaml\n# HR Workspace - Strict Compliance\nWorkspace: HR\n\nCompliance Settings:\n  data_residency: us-west-2\n  encryption: customer-managed-keys\n  audit_logging: enabled\n  retention:\n    override: 30 days\n    legal_hold: supported\n  sharing:\n    external: prohibited\n    download: restricted\n  access:\n    mfa_required: true\n    session_timeout: 4 hours\n```\n\n### Audit Configuration\n```markdown\n## Audit Log Settings\n\nEvents Logged:\n- User sign-in\u002Fout\n- Note created\u002Fedited\u002Fdeleted\n- Sharing changes\n- Export requests\n- Admin actions\n\nRetention: 2 years\nExport: Daily to SIEM\nFormat: JSON\nDestination: Splunk\u002FDatadog\n```\n\n## Environment Promotion\n\n### Staging to Production\n```markdown\n## Configuration Promotion\n\n1. Test in Staging Workspace\n   - Create test workspace\n   - Configure integrations\n   - Validate with sample data\n\n2. Document Configuration\n   - Export settings (JSON)\n   - Screenshot integrations\n   - Note manual steps\n\n3. Promote to Production\n   - Create production workspace\n   - Apply documented settings\n   - Re-authorize integrations\n   - Verify connections\n\n4. Validate\n   - Test meeting capture\n   - Verify integration flow\n   - Confirm permissions\n   - Monitor for 24 hours\n```\n\n## Troubleshooting Multi-Env\n\n### Common Issues\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| User in wrong workspace | SSO mapping error | Check group assignments |\n| Integration not syncing | Wrong environment config | Verify API keys |\n| Notes not visible | Permission mismatch | Check role assignment |\n| Cross-workspace search failing | Feature not enabled | Enable in org settings |\n\n## Resources\n- [Granola Enterprise Admin](https:\u002F\u002Fgranola.ai\u002Fadmin)\n- [SSO Configuration](https:\u002F\u002Fgranola.ai\u002Fhelp\u002Fsso)\n- [SCIM Provisioning](https:\u002F\u002Fgranola.ai\u002Fhelp\u002Fscim)\n\n## Next Steps\nProceed to `granola-observability` for monitoring and analytics.\n\n## Instructions\n\n1. Assess the current state of the deployment configuration\n2. Identify the specific requirements and constraints\n3. Apply the recommended patterns from this skill\n4. Validate the changes against expected behavior\n5. Document the configuration for team reference\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\n\n## Error Handling\n\n| Error | Cause | Resolution |\n|-------|-------|------------|\n| Authentication failure | Invalid or expired credentials | Refresh tokens or re-authenticate with deployment |\n| Configuration conflict | Incompatible settings detected | Review and resolve conflicting parameters |\n| Resource not found | Referenced resource missing | Verify resource exists and permissions are correct |\n\n## Examples\n\n**Basic usage**: Apply granola multi env setup to a standard project setup with default configuration options.\n\n**Advanced scenario**: Customize granola multi env setup for production environments with multiple constraints and team-specific requirements.",{"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 Granola across multiple workspaces and team environments.\nUse when setting up multi-team deployments, configuring workspace hierarchies,\nor managing enterprise-scale Granola installations.\nTrigger with phrases like \"granola workspaces\", \"granola multi-team\",\n\"granola environments\", \"granola organization\", \"granola multi-env\".\n","Read, Write, Edit","claude-code, codex, openclaw","master","3f5d983eb4ef375b749adcd6b07ec03bd82ae8a8","claude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsaas-packs\u002Fgranola-pack\u002Fskills\u002Fgranola-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 granola-multi-env-setup",{"tool":61,"command":62},"bunx","bunx skills add micsapp\u002Fmicstec-skills --skill granola-multi-env-setup",{"tool":64,"command":65},"pnpm","pnpm dlx skills add micsapp\u002Fmicstec-skills --skill granola-multi-env-setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsaas-packs\u002Fgranola-pack\u002Fskills\u002Fgranola-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,96,34,97,98,27,99,100,101,102,103,104],"architecture","azure","azure apim architecture","component","authentication","gateway","topology","Optimization","network","api","environment","multi-environment","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,35,125,126,127,128,129,96,34,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,96,34,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,96,149,166,88,120,167,168,169,170,34,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,96,189,190,191,25,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"]