[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69BAQJEXSKJH6ERZH3E9E4N":3,"skill-same:01M69BAQJEXSKJH6ERZH3E9E4N":80},{"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":21,"linkOnly":22,"markdownContent":23,"markdownBody":24,"frontMatter":25,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M69BAQJEXSKJH6ERZH3E9E4N","6-azure-impact-analyze",null,"Calculate severity and migration effort for Azure resources with detected features. Configurable severity thresholds based on usage patterns and business impact. Works with any Azure product deprecation scenario.","microsoft\u002Facs-resource-explorer","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69BA2FBF27EHVMWBDYE4QN5",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Facs-resource-explorer\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fazure\u002F6-azure-impact-analyze\u002FSKILL.md",[],[19,20],"azure","6 azure impact analyze","2026-11-10 10:12:30",false,"---\nname: 6-azure-impact-analyze\ndescription: Calculate severity and migration effort for Azure resources with detected features. Configurable severity thresholds based on usage patterns and business impact. Works with any Azure product deprecation scenario.\n---\n\n## When to use this skill\nUse this skill after feature detection to assess business impact and prioritize migration efforts.\n\nExamples:\n  - \"Analyze the impact of these detected features\"\n  - \"Calculate severity for resources with retiring services\"\n  - \"Estimate migration effort for these resources\"\n  - \"Which resources should I prioritize for migration?\"\n\n## Preconditions\n- Azure authentication completed (use **1-azure-auth-check** skill)\n- Resources discovered (use **3-azure-resource-scan** skill)\n- Features detected (use **4-azure-channel-detect** or **5-azure-metrics-collect** skill)\n- Session state contains resource inventory with feature detection results\n\n## Workflow\n\n### 1) **Load Resource Inventory with Detection Results**\n   - Retrieve resource inventory from session state\n   - Verify each resource has feature detection data:\n     - `FeaturesDetected` array\n     - `FeatureUsage` object (if metrics collected)\n     - `TotalFeaturesDetected` count\n   - If no detection data: Exit with message \"Run azure-channel-detect or azure-metrics-collect first\"\n\n### 2) **Configure Severity Thresholds**\n\n   **Interactive Mode:**\n   - Ask user: \"Do you want to use predefined severity rules or define custom thresholds?\"\n   - Present options:\n     ```\n     Severity Configuration:\n     1. Use predefined rules (recommended for common Azure products)\n     2. Define custom usage thresholds\n     3. Define custom business impact rules\n     ```\n\n   **Predefined Severity Rules (Examples):**\n\n   **Azure Communication Services:**\n   ```\n   Critical Severity:\n     - Email usage > 1,000 messages\u002Fday average\n     - Calling usage > 500 calls\u002Fday average\n     - Any feature with >10,000 operations in period\n\n   Warning Severity:\n     - Email usage > 100 messages\u002Fday average\n     - SMS usage > 50 messages\u002Fday average\n     - Any feature with >1,000 operations in period\n\n   Info Severity:\n     - Any feature detected with usage below Warning threshold\n     - Resources with features detected but low usage\n   ```\n\n   **Storage Accounts:**\n   ```\n   Critical Severity:\n     - Total transactions > 1,000,000 in period\n     - Data stored > 10 TB\n     - Business-critical tag present\n\n   Warning Severity:\n     - Total transactions > 100,000 in period\n     - Data stored > 1 TB\n\n   Info Severity:\n     - Feature detected with minimal usage\n   ```\n\n   **Custom Threshold Configuration:**\n   - Allow user to specify:\n     - Usage thresholds per feature\n     - Retirement timeline urgency (days until retirement)\n     - Business criticality tags\n     - Custom severity rules\n\n### 3) **For Each Resource in Inventory**\n   - Display: \"? Analyzing impact: [Resource Name]\"\n   - Initialize impact assessment:\n     ```\n     {\n       ResourceId: \"...\",\n       ResourceName: \"...\",\n       SubscriptionName: \"...\",\n       ResourceGroup: \"...\",\n       Location: \"...\",\n\n       TotalFeaturesImpacted: 0,\n       FeaturesWithUsage: [],\n\n       HighestSeverity: \"None\",\n       SeverityReason: \"\",\n\n       MigrationEffortEstimate: \"None\",\n       EffortReason: \"\",\n\n       RecommendedPriority: 0,\n       NextSteps: []\n     }\n     ```\n\n### 4) **Calculate Severity for Each Feature**\n   - For each detected feature:\n     - Get usage count (if metrics available)\n     - Get lookback period (to calculate average)\n     - Apply severity rules:\n\n       **Usage-Based Severity:**\n       - Calculate daily average: `usageCount \u002F lookbackDays`\n       - Compare against thresholds\n       - Assign severity: Critical \u002F Warning \u002F Info\n\n       **Timeline-Based Severity:**\n       - If retirement date known:\n         - Days until retirement \u003C 30: Increase severity\n         - Days until retirement \u003C 90: Add urgency flag\n\n       **Business Impact:**\n       - Check resource tags (e.g., \"Environment=Production\")\n       - Increase severity for production resources\n\n   - Select highest severity across all features\n   - Store severity reason:\n     ```\n     Example: \"Critical: Email usage (1,250 messages over 90 days = 14\u002Fday average) exceeds threshold (10\u002Fday)\"\n     ```\n\n### 5) **Estimate Migration Effort**\n   - Calculate based on multiple factors:\n\n     **Factor 1: Number of Impacted Features**\n     ```\n     High Effort:   3+ features with usage\n     Medium Effort: 2 features with usage\n     Low Effort:    1 feature with usage\n     ```\n\n     **Factor 2: Usage Volume**\n     ```\n     High Effort:   Any feature with >10,000 operations\n     Medium Effort: Any feature with >1,000 operations\n     Low Effort:    All features with \u003C1,000 operations\n     ```\n\n     **Factor 3: Feature Complexity**\n     ```\n     High Effort:   Features requiring code changes + testing\n     Medium Effort: Features requiring configuration changes\n     Low Effort:    Features with direct drop-in replacements\n     ```\n\n     **Factor 4: Integration Depth**\n     ```\n     High Effort:   Deeply integrated (multiple callsites, custom logic)\n     Medium Effort: Moderately integrated (few callsites, standard patterns)\n     Low Effort:    Lightly integrated (single callsite, simple usage)\n     ```\n\n   - Combine factors using weighted scoring\n   - Assign final effort estimate: High \u002F Medium \u002F Low\n   - Store effort reason\n\n### 6) **Calculate Recommended Priority**\n   - Priority scoring formula:\n     ```\n     Priority Score =\n       (Severity Weight) +\n       (Effort Weight) +\n       (Usage Volume Weight) +\n       (Timeline Urgency Weight)\n\n     Weights:\n       Critical Severity: +100 points\n       Warning Severity:  +50 points\n       Info Severity:     +10 points\n\n       High Effort:       +30 points (needs more time)\n       Medium Effort:     +20 points\n       Low Effort:        +10 points\n\n       High Usage:        +20 points (high business impact)\n       Timeline \u003C 30 days: +50 points (urgent)\n       Timeline \u003C 90 days: +25 points\n     ```\n\n   - Sort resources by priority score (highest first)\n   - Assign priority ranks: 1 (highest), 2, 3, ...\n\n### 7) **Generate Recommended Next Steps**\n   - Based on severity, effort, and priority, generate actionable recommendations:\n\n     **Critical Severity + High Priority:**\n     ```\n     1. ⚠️ URGENT: Schedule migration planning meeting immediately\n     2. Review migration guide for [Feature Name]\n     3. Allocate engineering resources (estimated [Effort] effort)\n     4. Plan for testing and rollback strategy\n     5. Set migration completion target: [Date based on retirement timeline]\n     ```\n\n     **Warning Severity + Medium Priority:**\n     ```\n     1. Review usage patterns to confirm feature necessity\n     2. Read migration guide: [Link]\n     3. Plan migration for [Timeframe]\n     4. Consider using migration grace period if available\n     ```\n\n     **Info Severity + Low Priority:**\n     ```\n     1. Monitor usage trends\n     2. Review migration guide: [Link]\n     3. Plan migration for [Timeframe]\n     4. Consider if feature is still needed (low usage detected)\n     ```\n\n### 8) **Display Impact Analysis Results**\n   - Show comprehensive table:\n     ```\n     === Impact Analysis Results ===\n\n     ┌─────────────────┬────────────┬──────────────┬──────────────┬──────────┐\n     │ Resource        │ Features   │ Severity     │ Effort       │ Priority │\n     ├─────────────────┼────────────┼──────────────┼──────────────┼──────────┤\n     │ ACSProd         │ 3          │ Critical     │ High         │ 1        │\n     │ StorageMain     │ 2          │ Warning      │ Medium       │ 2        │\n     │ ACSDevAndTest   │ 1          │ Info         │ Low          │ 3        │\n     └─────────────────┴────────────┴──────────────┴──────────────┴──────────┘\n\n     Severity Breakdown:\n       ? Critical: 1 resource(s) - IMMEDIATE ACTION REQUIRED\n       ? Warning:  1 resource(s) - Plan migration soon\n       ℹ️ Info:     1 resource(s) - Low priority\n\n     Migration Effort:\n       High:   1 resource(s) - Allocate 3-4 weeks per resource\n       Medium: 1 resource(s) - Allocate 1-2 weeks per resource\n       Low:    1 resource(s) - Allocate \u003C1 week per resource\n     ```\n\n### 9) **Display Priority List**\n   - Show resources in priority order:\n     ```\n     ? Recommended Migration Order:\n\n     1. [Priority 1] ACSProd\n        Severity: Critical | Effort: High | Features: Email, Chat, Phone Numbers\n        Reason: High usage (1,250 emails, 543 chats) + Production environment\n        Next Step: Schedule migration planning immediately\n\n     2. [Priority 2] StorageMain\n        Severity: Warning | Effort: Medium | Features: Blob Storage, File Shares\n        Reason: Moderate usage (50k transactions) + Approaching retirement date\n        Next Step: Review migration guide and plan timeline\n\n     3. [Priority 3] ACSDevAndTest\n        Severity: Info | Effort: Low | Features: Email\n        Reason: Zero usage detected in last 90 days\n        Next Step: Consider decommissioning if no longer needed\n     ```\n\n### 10) **Save Impact Analysis**\n   - Update resource inventory with impact data:\n     - Add severity, effort, priority fields\n     - Add next steps recommendations\n     - Add analysis metadata (thresholds used, date analyzed)\n   - Store updated inventory in session state\n\n### 11) **Provide Summary Recommendations**\n   - Display overall guidance:\n     ```\n     ? Summary Recommendations:\n\n     Immediate Actions (Critical):\n       • 1 resource requires immediate attention\n       • Estimated total effort: High (3-4 weeks)\n       • Start with: ACSProd\n\n     Upcoming Actions (Warning):\n       • 1 resource should be migrated within 30 days\n       • Estimated total effort: Medium (1-2 weeks)\n\n     Low Priority (Info):\n       • 1 resource with low usage - review necessity\n       • Consider decommissioning unused resources\n\n     Next Steps:\n       1. Use azure-report-generate to export detailed report\n       2. Review migration guides for each impacted feature\n       3. Schedule planning meetings for Critical resources\n       4. Set up project tracking for migration efforts\n     ```\n\n## Output\n- Severity assessment per resource\n- Migration effort estimates\n- Prioritized resource list (highest priority first)\n- Recommended next steps for each resource\n- Summary statistics and recommendations\n- Updated resource inventory with impact analysis\n\n## Customization Options\n- Custom severity thresholds\n- Custom effort estimation rules\n- Business-specific priority weighting\n- Timeline urgency adjustments\n- Tag-based impact rules\n\n## Related Skills\n- Use **3-azure-resource-scan**, **4-azure-channel-detect**, or **5-azure-metrics-collect** before this skill\n- Use **7-azure-report-generate** after this skill to export results\n\n## Example Invocation\n```\nUser: \"Analyze the impact and prioritize my resources for migration\"\nAgent: [Runs 6-azure-impact-analyze skill]\nOutput:\n  ? Analyzing impact: ACSProd\n  ? Critical Severity: Email usage (1,250 messages) exceeds threshold\n  ? Migration Effort: High (3 features impacted)\n\n  ? Analyzing impact: ACSDevAndTest\n  ℹ️ Info Severity: Zero usage detected\n  ? Migration Effort: Low (0 features with usage)\n\n  === Impact Analysis Results ===\n  Critical Resources: 1\n  Warning Resources:  0\n  Info Resources:     1\n\n  ? Priority 1: ACSProd - Immediate action required\n```\n\n","## When to use this skill\nUse this skill after feature detection to assess business impact and prioritize migration efforts.\n\nExamples:\n  - \"Analyze the impact of these detected features\"\n  - \"Calculate severity for resources with retiring services\"\n  - \"Estimate migration effort for these resources\"\n  - \"Which resources should I prioritize for migration?\"\n\n## Preconditions\n- Azure authentication completed (use **1-azure-auth-check** skill)\n- Resources discovered (use **3-azure-resource-scan** skill)\n- Features detected (use **4-azure-channel-detect** or **5-azure-metrics-collect** skill)\n- Session state contains resource inventory with feature detection results\n\n## Workflow\n\n### 1) **Load Resource Inventory with Detection Results**\n   - Retrieve resource inventory from session state\n   - Verify each resource has feature detection data:\n     - `FeaturesDetected` array\n     - `FeatureUsage` object (if metrics collected)\n     - `TotalFeaturesDetected` count\n   - If no detection data: Exit with message \"Run azure-channel-detect or azure-metrics-collect first\"\n\n### 2) **Configure Severity Thresholds**\n\n   **Interactive Mode:**\n   - Ask user: \"Do you want to use predefined severity rules or define custom thresholds?\"\n   - Present options:\n     ```\n     Severity Configuration:\n     1. Use predefined rules (recommended for common Azure products)\n     2. Define custom usage thresholds\n     3. Define custom business impact rules\n     ```\n\n   **Predefined Severity Rules (Examples):**\n\n   **Azure Communication Services:**\n   ```\n   Critical Severity:\n     - Email usage > 1,000 messages\u002Fday average\n     - Calling usage > 500 calls\u002Fday average\n     - Any feature with >10,000 operations in period\n\n   Warning Severity:\n     - Email usage > 100 messages\u002Fday average\n     - SMS usage > 50 messages\u002Fday average\n     - Any feature with >1,000 operations in period\n\n   Info Severity:\n     - Any feature detected with usage below Warning threshold\n     - Resources with features detected but low usage\n   ```\n\n   **Storage Accounts:**\n   ```\n   Critical Severity:\n     - Total transactions > 1,000,000 in period\n     - Data stored > 10 TB\n     - Business-critical tag present\n\n   Warning Severity:\n     - Total transactions > 100,000 in period\n     - Data stored > 1 TB\n\n   Info Severity:\n     - Feature detected with minimal usage\n   ```\n\n   **Custom Threshold Configuration:**\n   - Allow user to specify:\n     - Usage thresholds per feature\n     - Retirement timeline urgency (days until retirement)\n     - Business criticality tags\n     - Custom severity rules\n\n### 3) **For Each Resource in Inventory**\n   - Display: \"? Analyzing impact: [Resource Name]\"\n   - Initialize impact assessment:\n     ```\n     {\n       ResourceId: \"...\",\n       ResourceName: \"...\",\n       SubscriptionName: \"...\",\n       ResourceGroup: \"...\",\n       Location: \"...\",\n\n       TotalFeaturesImpacted: 0,\n       FeaturesWithUsage: [],\n\n       HighestSeverity: \"None\",\n       SeverityReason: \"\",\n\n       MigrationEffortEstimate: \"None\",\n       EffortReason: \"\",\n\n       RecommendedPriority: 0,\n       NextSteps: []\n     }\n     ```\n\n### 4) **Calculate Severity for Each Feature**\n   - For each detected feature:\n     - Get usage count (if metrics available)\n     - Get lookback period (to calculate average)\n     - Apply severity rules:\n\n       **Usage-Based Severity:**\n       - Calculate daily average: `usageCount \u002F lookbackDays`\n       - Compare against thresholds\n       - Assign severity: Critical \u002F Warning \u002F Info\n\n       **Timeline-Based Severity:**\n       - If retirement date known:\n         - Days until retirement \u003C 30: Increase severity\n         - Days until retirement \u003C 90: Add urgency flag\n\n       **Business Impact:**\n       - Check resource tags (e.g., \"Environment=Production\")\n       - Increase severity for production resources\n\n   - Select highest severity across all features\n   - Store severity reason:\n     ```\n     Example: \"Critical: Email usage (1,250 messages over 90 days = 14\u002Fday average) exceeds threshold (10\u002Fday)\"\n     ```\n\n### 5) **Estimate Migration Effort**\n   - Calculate based on multiple factors:\n\n     **Factor 1: Number of Impacted Features**\n     ```\n     High Effort:   3+ features with usage\n     Medium Effort: 2 features with usage\n     Low Effort:    1 feature with usage\n     ```\n\n     **Factor 2: Usage Volume**\n     ```\n     High Effort:   Any feature with >10,000 operations\n     Medium Effort: Any feature with >1,000 operations\n     Low Effort:    All features with \u003C1,000 operations\n     ```\n\n     **Factor 3: Feature Complexity**\n     ```\n     High Effort:   Features requiring code changes + testing\n     Medium Effort: Features requiring configuration changes\n     Low Effort:    Features with direct drop-in replacements\n     ```\n\n     **Factor 4: Integration Depth**\n     ```\n     High Effort:   Deeply integrated (multiple callsites, custom logic)\n     Medium Effort: Moderately integrated (few callsites, standard patterns)\n     Low Effort:    Lightly integrated (single callsite, simple usage)\n     ```\n\n   - Combine factors using weighted scoring\n   - Assign final effort estimate: High \u002F Medium \u002F Low\n   - Store effort reason\n\n### 6) **Calculate Recommended Priority**\n   - Priority scoring formula:\n     ```\n     Priority Score =\n       (Severity Weight) +\n       (Effort Weight) +\n       (Usage Volume Weight) +\n       (Timeline Urgency Weight)\n\n     Weights:\n       Critical Severity: +100 points\n       Warning Severity:  +50 points\n       Info Severity:     +10 points\n\n       High Effort:       +30 points (needs more time)\n       Medium Effort:     +20 points\n       Low Effort:        +10 points\n\n       High Usage:        +20 points (high business impact)\n       Timeline \u003C 30 days: +50 points (urgent)\n       Timeline \u003C 90 days: +25 points\n     ```\n\n   - Sort resources by priority score (highest first)\n   - Assign priority ranks: 1 (highest), 2, 3, ...\n\n### 7) **Generate Recommended Next Steps**\n   - Based on severity, effort, and priority, generate actionable recommendations:\n\n     **Critical Severity + High Priority:**\n     ```\n     1. ⚠️ URGENT: Schedule migration planning meeting immediately\n     2. Review migration guide for [Feature Name]\n     3. Allocate engineering resources (estimated [Effort] effort)\n     4. Plan for testing and rollback strategy\n     5. Set migration completion target: [Date based on retirement timeline]\n     ```\n\n     **Warning Severity + Medium Priority:**\n     ```\n     1. Review usage patterns to confirm feature necessity\n     2. Read migration guide: [Link]\n     3. Plan migration for [Timeframe]\n     4. Consider using migration grace period if available\n     ```\n\n     **Info Severity + Low Priority:**\n     ```\n     1. Monitor usage trends\n     2. Review migration guide: [Link]\n     3. Plan migration for [Timeframe]\n     4. Consider if feature is still needed (low usage detected)\n     ```\n\n### 8) **Display Impact Analysis Results**\n   - Show comprehensive table:\n     ```\n     === Impact Analysis Results ===\n\n     ┌─────────────────┬────────────┬──────────────┬──────────────┬──────────┐\n     │ Resource        │ Features   │ Severity     │ Effort       │ Priority │\n     ├─────────────────┼────────────┼──────────────┼──────────────┼──────────┤\n     │ ACSProd         │ 3          │ Critical     │ High         │ 1        │\n     │ StorageMain     │ 2          │ Warning      │ Medium       │ 2        │\n     │ ACSDevAndTest   │ 1          │ Info         │ Low          │ 3        │\n     └─────────────────┴────────────┴──────────────┴──────────────┴──────────┘\n\n     Severity Breakdown:\n       ? Critical: 1 resource(s) - IMMEDIATE ACTION REQUIRED\n       ? Warning:  1 resource(s) - Plan migration soon\n       ℹ️ Info:     1 resource(s) - Low priority\n\n     Migration Effort:\n       High:   1 resource(s) - Allocate 3-4 weeks per resource\n       Medium: 1 resource(s) - Allocate 1-2 weeks per resource\n       Low:    1 resource(s) - Allocate \u003C1 week per resource\n     ```\n\n### 9) **Display Priority List**\n   - Show resources in priority order:\n     ```\n     ? Recommended Migration Order:\n\n     1. [Priority 1] ACSProd\n        Severity: Critical | Effort: High | Features: Email, Chat, Phone Numbers\n        Reason: High usage (1,250 emails, 543 chats) + Production environment\n        Next Step: Schedule migration planning immediately\n\n     2. [Priority 2] StorageMain\n        Severity: Warning | Effort: Medium | Features: Blob Storage, File Shares\n        Reason: Moderate usage (50k transactions) + Approaching retirement date\n        Next Step: Review migration guide and plan timeline\n\n     3. [Priority 3] ACSDevAndTest\n        Severity: Info | Effort: Low | Features: Email\n        Reason: Zero usage detected in last 90 days\n        Next Step: Consider decommissioning if no longer needed\n     ```\n\n### 10) **Save Impact Analysis**\n   - Update resource inventory with impact data:\n     - Add severity, effort, priority fields\n     - Add next steps recommendations\n     - Add analysis metadata (thresholds used, date analyzed)\n   - Store updated inventory in session state\n\n### 11) **Provide Summary Recommendations**\n   - Display overall guidance:\n     ```\n     ? Summary Recommendations:\n\n     Immediate Actions (Critical):\n       • 1 resource requires immediate attention\n       • Estimated total effort: High (3-4 weeks)\n       • Start with: ACSProd\n\n     Upcoming Actions (Warning):\n       • 1 resource should be migrated within 30 days\n       • Estimated total effort: Medium (1-2 weeks)\n\n     Low Priority (Info):\n       • 1 resource with low usage - review necessity\n       • Consider decommissioning unused resources\n\n     Next Steps:\n       1. Use azure-report-generate to export detailed report\n       2. Review migration guides for each impacted feature\n       3. Schedule planning meetings for Critical resources\n       4. Set up project tracking for migration efforts\n     ```\n\n## Output\n- Severity assessment per resource\n- Migration effort estimates\n- Prioritized resource list (highest priority first)\n- Recommended next steps for each resource\n- Summary statistics and recommendations\n- Updated resource inventory with impact analysis\n\n## Customization Options\n- Custom severity thresholds\n- Custom effort estimation rules\n- Business-specific priority weighting\n- Timeline urgency adjustments\n- Tag-based impact rules\n\n## Related Skills\n- Use **3-azure-resource-scan**, **4-azure-channel-detect**, or **5-azure-metrics-collect** before this skill\n- Use **7-azure-report-generate** after this skill to export results\n\n## Example Invocation\n```\nUser: \"Analyze the impact and prioritize my resources for migration\"\nAgent: [Runs 6-azure-impact-analyze skill]\nOutput:\n  ? Analyzing impact: ACSProd\n  ? Critical Severity: Email usage (1,250 messages) exceeds threshold\n  ? Migration Effort: High (3 features impacted)\n\n  ? Analyzing impact: ACSDevAndTest\n  ℹ️ Info Severity: Zero usage detected\n  ? Migration Effort: Low (0 features with usage)\n\n  === Impact Analysis Results ===\n  Critical Resources: 1\n  Warning Resources:  0\n  Info Resources:     1\n\n  ? Priority 1: ACSProd - Immediate action required\n```\n\n",{"name":5,"description":7},"main","84a5fb9afdc4334608c45af9f32a0678a65af8ac",".agent\u002Fskills\u002Fazure\u002F6-azure-impact-analyze","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Facs-resource-explorer","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-10-08 22:58:45",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add microsoft\u002Facs-resource-explorer --skill 6-azure-impact-analyze",{"tool":40,"command":41},"bunx","bunx skills add microsoft\u002Facs-resource-explorer --skill 6-azure-impact-analyze",{"tool":43,"command":44},"pnpm","pnpm dlx skills add microsoft\u002Facs-resource-explorer --skill 6-azure-impact-analyze","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Facs-resource-explorer\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fazure\u002F6-azure-impact-analyze\u002FSKILL.md",true,[48,54,60,64,68,72,76],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"README.md","REFERENCE","参考文档",2995,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fgravitino\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgravitino-docs-refine\u002FREADME.md",{"path":55,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":58,"sourceHtmlUrl":59},"scripts\u002Fcheck_links.py","SCRIPT","脚本",7566,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fgravitino\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgravitino-docs-refine\u002Fscripts\u002Fcheck_links.py",{"path":61,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":62,"sourceHtmlUrl":63},"scripts\u002Fheading_audit.py",3379,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fgravitino\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgravitino-docs-refine\u002Fscripts\u002Fheading_audit.py",{"path":65,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":66,"sourceHtmlUrl":67},"scripts\u002Fheading_spacing_audit.py",2766,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fgravitino\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgravitino-docs-refine\u002Fscripts\u002Fheading_spacing_audit.py",{"path":69,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":70,"sourceHtmlUrl":71},"scripts\u002Fintro_audit.py",3204,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fgravitino\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgravitino-docs-refine\u002Fscripts\u002Fintro_audit.py",{"path":73,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":74,"sourceHtmlUrl":75},"scripts\u002Ftitle_h2_audit.py",2969,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fgravitino\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgravitino-docs-refine\u002Fscripts\u002Ftitle_h2_audit.py",{"path":77,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":78,"sourceHtmlUrl":79},"STYLE.md",23915,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fgravitino\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgravitino-docs-refine\u002FSTYLE.md",[81,100,109,117,126,138],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":97,"publishedAt":21},"01M69BAS7GJEMMPGYEE3SNQZMG","7-azure-report-generate","Generate comprehensive reports (CSV, Markdown, JSON) for Azure resource impact assessments. Export detailed findings, statistics, and recommendations. Works with any Azure product deprecation analysis.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Facs-resource-explorer\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fazure\u002F7-azure-report-generate\u002FSKILL.md",[87,92],{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",{"categoryNo":93,"categoryName":94,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[98,99,19],"7 azure report generate","generate",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":21},"01M69BANPY8VKV0SCTWZQMYSA1","5-azure-metrics-collect","Comprehensive feature\u002Fusage detection via Azure Monitor metrics. Collects usage data over configurable lookback period (1-93 days). Works with any Azure product that emits metrics to Azure Monitor.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Facs-resource-explorer\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fazure\u002F5-azure-metrics-collect\u002FSKILL.md",[],[107,19,108],"5 azure metrics collect","monitor",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":21},"01M69BAKTCQDEW24K2A2TQ7FRV","4-azure-channel-detect","Fast, resource-based feature detection for Azure resources. Detects features\u002Fchannels by examining related child resources (domains, endpoints, configurations). Works with any Azure product where features are exposed as sub-resources.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Facs-resource-explorer\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fazure\u002F4-azure-channel-detect\u002FSKILL.md",[],[116,19],"4 azure channel detect",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":21},"01M69BAHNTGV0TCTR6PWH014DC","3-azure-resource-scan","Scan Azure subscriptions for specific resource types. Interactive prompts allow scanning any Azure product (ACS, Storage, Compute, Databases, etc). Returns resource inventory across selected subscriptions.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Facs-resource-explorer\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fazure\u002F3-azure-resource-scan\u002FSKILL.md",[],[124,19,125],"3 azure resource scan","storage",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":135,"publishedAt":21},"01M69BAG50E9T1NYQPPZB1MF10","2-azure-subscription-select","Interactive subscription selection workflow. Choose specific subscription(s) or scan all accessible subscriptions. Works with any Azure product or service.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Facs-resource-explorer\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fazure\u002F2-azure-subscription-select\u002FSKILL.md",[132],{"categoryNo":133,"categoryName":134,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000023","Skill与智能体开发",[136,19,137],"2 azure subscription select","workflow",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":21},"01M69BAEJR4EPCAM6056QQF9RY","1-azure-auth-check","Verify Azure authentication status and display connection information (tenant, account, subscription context). Works with any Azure product or service.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Facs-resource-explorer\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fazure\u002F1-azure-auth-check\u002FSKILL.md",[],[145,146,19,147],"auth","1 azure auth check","status"]