[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69BANPY8VKV0SCTWZQMYSA1":3,"skill-same:01M69BANPY8VKV0SCTWZQMYSA1":55},{"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":22,"linkOnly":23,"markdownContent":24,"markdownBody":25,"frontMatter":26,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M69BANPY8VKV0SCTWZQMYSA1","5-azure-metrics-collect",null,"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.","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\u002F5-azure-metrics-collect\u002FSKILL.md",[],[19,20,21],"azure","5 azure metrics collect","monitor","2026-11-10 10:12:30",false,"---\nname: 5-azure-metrics-collect\ndescription: 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.\n---\n\n## When to use this skill\nUse this skill for complete feature detection based on actual usage metrics (slower but comprehensive).\n\nExamples:\n  - \"Collect usage metrics for my ACS resources\"\n  - \"Analyze Storage Account usage over the last 90 days\"\n  - \"Get complete feature detection with metrics\"\n  - \"How much are these resources being used?\"\n\n## Preconditions\n- Azure authentication completed (use **1-azure-auth-check** skill)\n- Subscription(s) selected (use **2-azure-subscription-select** skill)\n- Resources discovered (use **3-azure-resource-scan** skill)\n- User has **Monitoring Reader** access to resources\n\n> **Note:** This is a COMPREHENSIVE detection method. It takes longer (~3-5 minutes per subscription) but provides complete usage-based detection.\n\n## Workflow\n\n### 1) **Load Resource Inventory**\n   - Retrieve resource list from session state (saved by **3-azure-resource-scan**)\n   - Confirm resources exist to analyze\n   - If no resources: Exit with message \"No resources to analyze\"\n\n### 2) **Configure Metrics Collection**\n\n   **Interactive Mode:**\n   - Ask user: \"How far back should we check for usage? (1-93 days)\"\n   - Display recommendation: \"? Recommended: 90 days for comprehensive analysis\"\n   - Prompt for lookback period\n   - Validate: Must be between 1-93 days (Azure Monitor retention limit)\n\n   **Non-Interactive Mode:**\n   - Accept parameter: `--lookback-days 90`\n   - Default: 90 days if not specified\n\n### 3) **Determine Metrics to Collect**\n\n   **Interactive Mode:**\n   - Ask user: \"Which features\u002Fchannels do you want to analyze?\"\n   - Present options based on resource type\n\n   **Predefined Metric Configurations (Examples):**\n\n   **Azure Communication Services:**\n   ```\n   Email:\n     - ApiRequests\n     - DeliveryStatusUpdate\n     - UserEngagement\n\n   SMS:\n     - APIRequestSMS\n\n   Chat:\n     - APIRequestChat\n\n   CallAutomation:\n     - APIRequestCallAutomation\n     - APIRequestCallRecording\n     - AcsCallAutomationCallbackEvent\n\n   Job Router:\n     - ApiRequestRouter\n\n   AdvanceMessaging:\n     - APIRequestsAdvancedMessaging\n\n   Rooms:\n     - ApiRequestRooms\n   ```\n\n   **Storage Accounts:**\n   ```\n   Blob Storage:\n     - BlobCapacity\n     - BlobCount\n     - Transactions (filter: API = blob)\n\n   File Shares:\n     - FileCapacity\n     - FileCount\n     - Transactions (filter: API = file)\n\n   Queue Storage:\n     - QueueCapacity\n     - QueueCount\n     - QueueMessageCount\n   ```\n\n   **Custom Metrics:**\n   - Allow user to specify custom metric names\n   - Validate metric availability for resource type\n\n### 4) **Calculate Time Range**\n   - Set end time: Current date\u002Ftime\n   - Set start time: Current date\u002Ftime minus lookback days\n   - Display: \"? Analyzing usage from [Start Date] to [End Date] ([N] days)\"\n\n### 5) **For Each Resource in Inventory**\n   - Display: \"? Collecting metrics: [Resource Name]\"\n   - Set Azure context to resource's subscription\n   - Initialize metrics results:\n     ```\n     {\n       ResourceId: \"...\",\n       ResourceName: \"...\",\n       LookbackPeriodDays: N,\n       FeatureUsage: {},\n       DetectionMethod: \"Azure Monitor Metrics\",\n       Complete: true\n     }\n     ```\n\n### 6) **For Each Feature\u002FChannel**\n   - Display progress: \"  ⏳ Checking [Feature Name] metrics...\"\n   - Initialize usage counter = 0\n\n   **For each metric in feature's metric list:**\n   - Query Azure Monitor via the Azure CLI:\n     ```bash\n     az monitor metrics list \\\n       --resource \u003Cresource-id> \\\n       --metric \u003Cmetric-name> \\\n       --start-time \u003Cstart-time-UTC> \\\n       --end-time \u003Cend-time-UTC> \\\n       --interval PT1H \\\n       --aggregation Total \\\n       --output json\n     ```\n\n   - If metrics returned with data:\n     - Sum all values by iterating `value[0].timeseries[].data[].total` and summing all non-null entries\n     - Add to feature usage counter\n\n   - If metrics unavailable:\n     - Log: \"Metric not available (may not be applicable)\"\n     - Continue to next metric\n\n### 7) **Update Feature Detection Results**\n   - If total usage > 0:\n     - Mark feature as DETECTED\n     - Store usage count\n     - Display: \"  ✅ [Feature Name]: [Usage Count] (messages\u002Fcalls\u002Foperations)\"\n\n   - If total usage = 0:\n     - Mark feature as NOT DETECTED (zero usage)\n     - Display: \"  ⚪ [Feature Name]: 0 usage in last [N] days\"\n\n### 8) **Display Resource Usage Summary**\n   - For each resource, show comprehensive breakdown:\n     ```\n     ? Usage Summary: ACSProd (Last 90 days)\n     ┌─────────────────┬──────────────┬────────────────┐\n     │ Feature         │ Usage Count  │ Status         │\n     ├─────────────────┼──────────────┼────────────────┤\n     │ Email           │ 1,250        │ ✅ Detected     │\n     │ SMS             │ 0            │ ⚪ Zero usage   │\n     │ Chat            │ 543          │ ✅ Detected     │\n     │ Phone Numbers   │ 15           │ ✅ Detected     │\n    │ CallAutomation  │ 0            │ ⚪ Zero usage   │\n    │ Job Router      │ 15           │ ✅ Detected     │\n    │ Advance Msg     │ 0            │ ⚪ Zero usage   │\n    │ Rooms           │ 0            │ ⚪ Zero usage   │\n     └─────────────────┴──────────────┴────────────────┘\n\n    Total Features with Usage: 3 out of N\n     ```\n\n### 9) **Provide Lookback Period Guidance**\n   - If lookback \u003C 93 days:\n     - Display: \"? Want more historical data? Re-run with lookback set to 93 days (maximum)\"\n\n   - If lookback = 93 days:\n     - Display: \"ℹ️ 93 days is the maximum Azure Monitor retention period for 1-hour granularity\"\n\n### 10) **Save Metrics Results**\n   - Update resource inventory with metrics data:\n     - Add `FeatureUsage` object (feature → usage count)\n     - Add `LookbackPeriodDays` field\n     - Add `DetectionComplete` flag = true\n     - Add `TotalFeaturesDetected` count\n   - Store updated inventory in session state\n\n### 11) **Display Collection Summary**\n   - Show aggregate statistics:\n     ```\n     === Metrics Collection Complete ===\n     Resources Analyzed: 5\n     Lookback Period: 90 days\n     Total Features Detected: 12\n\n     Next Steps:\n     ? Use azure-impact-analyze to calculate severity and migration effort\n     ```\n\n## Output\n- Complete feature usage data per resource\n- Usage counts for each feature\u002Fchannel\n- Lookback period used\n- Features detected vs. zero usage\n- Updated resource inventory with comprehensive metrics\n\n## Performance Characteristics\n- **Speed:** ~3-5 minutes per subscription (slower than **4-azure-channel-detect**)\n- **Completeness:** 100% feature detection (includes usage-based features)\n- **Data Volume:** Queries up to 93 days of hourly metrics per resource\n\n## Error Handling\n- Metric not available: Log silently, continue (metric may not apply)\n- API throttling: Implement retry logic with exponential backoff\n- Permission errors: Display clear error, skip resource\n\n## Cost Considerations\n- Azure Monitor API calls are metered\n- High resource counts may incur costs\n- Recommend batching or limiting scope for large environments\n\n## Related Skills\n- Use **1-azure-auth-check**, **2-azure-subscription-select**, **3-azure-resource-scan** before this skill\n- Use **4-azure-channel-detect** before this skill (optional - for fast pre-check)\n- Use **6-azure-impact-analyze** after this skill to assess severity and effort\n\n## Example Invocation\n```\nUser: \"Collect full usage metrics for my ACS resources over 90 days\"\nAgent: [Runs 5-azure-metrics-collect skill]\nOutput:\n  ? Analyzing usage from 2025-11-08 to 2026-02-06 (90 days)\n\n  ? Collecting metrics: ACSProd\n    ✅ Email: 1,250 messages\n    ⚪ SMS: 0 messages\n    ✅ Chat: 543 messages\n    ⚪ Calling: 0 calls\n    ✅ Phone Numbers: 15 operations\n\n  ? Collecting metrics: ACSDevAndTest\n    ⚪ Email: 0 messages (zero usage in last 90 days)\n    ⚪ SMS: 0 messages (zero usage in last 90 days)\n    ...\n\n  === Metrics Collection Complete ===\n  Resources Analyzed: 2\n  Features with Usage: 3 out of 5\n```\n\n","## When to use this skill\nUse this skill for complete feature detection based on actual usage metrics (slower but comprehensive).\n\nExamples:\n  - \"Collect usage metrics for my ACS resources\"\n  - \"Analyze Storage Account usage over the last 90 days\"\n  - \"Get complete feature detection with metrics\"\n  - \"How much are these resources being used?\"\n\n## Preconditions\n- Azure authentication completed (use **1-azure-auth-check** skill)\n- Subscription(s) selected (use **2-azure-subscription-select** skill)\n- Resources discovered (use **3-azure-resource-scan** skill)\n- User has **Monitoring Reader** access to resources\n\n> **Note:** This is a COMPREHENSIVE detection method. It takes longer (~3-5 minutes per subscription) but provides complete usage-based detection.\n\n## Workflow\n\n### 1) **Load Resource Inventory**\n   - Retrieve resource list from session state (saved by **3-azure-resource-scan**)\n   - Confirm resources exist to analyze\n   - If no resources: Exit with message \"No resources to analyze\"\n\n### 2) **Configure Metrics Collection**\n\n   **Interactive Mode:**\n   - Ask user: \"How far back should we check for usage? (1-93 days)\"\n   - Display recommendation: \"? Recommended: 90 days for comprehensive analysis\"\n   - Prompt for lookback period\n   - Validate: Must be between 1-93 days (Azure Monitor retention limit)\n\n   **Non-Interactive Mode:**\n   - Accept parameter: `--lookback-days 90`\n   - Default: 90 days if not specified\n\n### 3) **Determine Metrics to Collect**\n\n   **Interactive Mode:**\n   - Ask user: \"Which features\u002Fchannels do you want to analyze?\"\n   - Present options based on resource type\n\n   **Predefined Metric Configurations (Examples):**\n\n   **Azure Communication Services:**\n   ```\n   Email:\n     - ApiRequests\n     - DeliveryStatusUpdate\n     - UserEngagement\n\n   SMS:\n     - APIRequestSMS\n\n   Chat:\n     - APIRequestChat\n\n   CallAutomation:\n     - APIRequestCallAutomation\n     - APIRequestCallRecording\n     - AcsCallAutomationCallbackEvent\n\n   Job Router:\n     - ApiRequestRouter\n\n   AdvanceMessaging:\n     - APIRequestsAdvancedMessaging\n\n   Rooms:\n     - ApiRequestRooms\n   ```\n\n   **Storage Accounts:**\n   ```\n   Blob Storage:\n     - BlobCapacity\n     - BlobCount\n     - Transactions (filter: API = blob)\n\n   File Shares:\n     - FileCapacity\n     - FileCount\n     - Transactions (filter: API = file)\n\n   Queue Storage:\n     - QueueCapacity\n     - QueueCount\n     - QueueMessageCount\n   ```\n\n   **Custom Metrics:**\n   - Allow user to specify custom metric names\n   - Validate metric availability for resource type\n\n### 4) **Calculate Time Range**\n   - Set end time: Current date\u002Ftime\n   - Set start time: Current date\u002Ftime minus lookback days\n   - Display: \"? Analyzing usage from [Start Date] to [End Date] ([N] days)\"\n\n### 5) **For Each Resource in Inventory**\n   - Display: \"? Collecting metrics: [Resource Name]\"\n   - Set Azure context to resource's subscription\n   - Initialize metrics results:\n     ```\n     {\n       ResourceId: \"...\",\n       ResourceName: \"...\",\n       LookbackPeriodDays: N,\n       FeatureUsage: {},\n       DetectionMethod: \"Azure Monitor Metrics\",\n       Complete: true\n     }\n     ```\n\n### 6) **For Each Feature\u002FChannel**\n   - Display progress: \"  ⏳ Checking [Feature Name] metrics...\"\n   - Initialize usage counter = 0\n\n   **For each metric in feature's metric list:**\n   - Query Azure Monitor via the Azure CLI:\n     ```bash\n     az monitor metrics list \\\n       --resource \u003Cresource-id> \\\n       --metric \u003Cmetric-name> \\\n       --start-time \u003Cstart-time-UTC> \\\n       --end-time \u003Cend-time-UTC> \\\n       --interval PT1H \\\n       --aggregation Total \\\n       --output json\n     ```\n\n   - If metrics returned with data:\n     - Sum all values by iterating `value[0].timeseries[].data[].total` and summing all non-null entries\n     - Add to feature usage counter\n\n   - If metrics unavailable:\n     - Log: \"Metric not available (may not be applicable)\"\n     - Continue to next metric\n\n### 7) **Update Feature Detection Results**\n   - If total usage > 0:\n     - Mark feature as DETECTED\n     - Store usage count\n     - Display: \"  ✅ [Feature Name]: [Usage Count] (messages\u002Fcalls\u002Foperations)\"\n\n   - If total usage = 0:\n     - Mark feature as NOT DETECTED (zero usage)\n     - Display: \"  ⚪ [Feature Name]: 0 usage in last [N] days\"\n\n### 8) **Display Resource Usage Summary**\n   - For each resource, show comprehensive breakdown:\n     ```\n     ? Usage Summary: ACSProd (Last 90 days)\n     ┌─────────────────┬──────────────┬────────────────┐\n     │ Feature         │ Usage Count  │ Status         │\n     ├─────────────────┼──────────────┼────────────────┤\n     │ Email           │ 1,250        │ ✅ Detected     │\n     │ SMS             │ 0            │ ⚪ Zero usage   │\n     │ Chat            │ 543          │ ✅ Detected     │\n     │ Phone Numbers   │ 15           │ ✅ Detected     │\n    │ CallAutomation  │ 0            │ ⚪ Zero usage   │\n    │ Job Router      │ 15           │ ✅ Detected     │\n    │ Advance Msg     │ 0            │ ⚪ Zero usage   │\n    │ Rooms           │ 0            │ ⚪ Zero usage   │\n     └─────────────────┴──────────────┴────────────────┘\n\n    Total Features with Usage: 3 out of N\n     ```\n\n### 9) **Provide Lookback Period Guidance**\n   - If lookback \u003C 93 days:\n     - Display: \"? Want more historical data? Re-run with lookback set to 93 days (maximum)\"\n\n   - If lookback = 93 days:\n     - Display: \"ℹ️ 93 days is the maximum Azure Monitor retention period for 1-hour granularity\"\n\n### 10) **Save Metrics Results**\n   - Update resource inventory with metrics data:\n     - Add `FeatureUsage` object (feature → usage count)\n     - Add `LookbackPeriodDays` field\n     - Add `DetectionComplete` flag = true\n     - Add `TotalFeaturesDetected` count\n   - Store updated inventory in session state\n\n### 11) **Display Collection Summary**\n   - Show aggregate statistics:\n     ```\n     === Metrics Collection Complete ===\n     Resources Analyzed: 5\n     Lookback Period: 90 days\n     Total Features Detected: 12\n\n     Next Steps:\n     ? Use azure-impact-analyze to calculate severity and migration effort\n     ```\n\n## Output\n- Complete feature usage data per resource\n- Usage counts for each feature\u002Fchannel\n- Lookback period used\n- Features detected vs. zero usage\n- Updated resource inventory with comprehensive metrics\n\n## Performance Characteristics\n- **Speed:** ~3-5 minutes per subscription (slower than **4-azure-channel-detect**)\n- **Completeness:** 100% feature detection (includes usage-based features)\n- **Data Volume:** Queries up to 93 days of hourly metrics per resource\n\n## Error Handling\n- Metric not available: Log silently, continue (metric may not apply)\n- API throttling: Implement retry logic with exponential backoff\n- Permission errors: Display clear error, skip resource\n\n## Cost Considerations\n- Azure Monitor API calls are metered\n- High resource counts may incur costs\n- Recommend batching or limiting scope for large environments\n\n## Related Skills\n- Use **1-azure-auth-check**, **2-azure-subscription-select**, **3-azure-resource-scan** before this skill\n- Use **4-azure-channel-detect** before this skill (optional - for fast pre-check)\n- Use **6-azure-impact-analyze** after this skill to assess severity and effort\n\n## Example Invocation\n```\nUser: \"Collect full usage metrics for my ACS resources over 90 days\"\nAgent: [Runs 5-azure-metrics-collect skill]\nOutput:\n  ? Analyzing usage from 2025-11-08 to 2026-02-06 (90 days)\n\n  ? Collecting metrics: ACSProd\n    ✅ Email: 1,250 messages\n    ⚪ SMS: 0 messages\n    ✅ Chat: 543 messages\n    ⚪ Calling: 0 calls\n    ✅ Phone Numbers: 15 operations\n\n  ? Collecting metrics: ACSDevAndTest\n    ⚪ Email: 0 messages (zero usage in last 90 days)\n    ⚪ SMS: 0 messages (zero usage in last 90 days)\n    ...\n\n  === Metrics Collection Complete ===\n  Resources Analyzed: 2\n  Features with Usage: 3 out of 5\n```\n\n",{"name":5,"description":7},"main","84a5fb9afdc4334608c45af9f32a0678a65af8ac",".agent\u002Fskills\u002Fazure\u002F5-azure-metrics-collect","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":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add microsoft\u002Facs-resource-explorer --skill 5-azure-metrics-collect",{"tool":41,"command":42},"bunx","bunx skills add microsoft\u002Facs-resource-explorer --skill 5-azure-metrics-collect",{"tool":44,"command":45},"pnpm","pnpm dlx skills add microsoft\u002Facs-resource-explorer --skill 5-azure-metrics-collect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Facs-resource-explorer\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fazure\u002F5-azure-metrics-collect\u002FSKILL.md",true,[49],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"README.md","REFERENCE","参考文档",2599,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fgravitino\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgravitino-design-doc\u002FREADME.md",[56,75,83,91,100,112],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":72,"publishedAt":22},"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",[62,67],{"categoryNo":63,"categoryName":64,"taxonomyType":65,"taxonomyTypeDesc":66},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",{"categoryNo":68,"categoryName":69,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[73,74,19],"7 azure report generate","generate",{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":22},"01M69BAQJEXSKJH6ERZH3E9E4N","6-azure-impact-analyze","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.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Facs-resource-explorer\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fazure\u002F6-azure-impact-analyze\u002FSKILL.md",[],[82,19],"6 azure impact analyze",{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":22},"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",[],[90,19],"4 azure channel detect",{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":22},"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",[],[19,98,99],"3 azure resource scan","storage",{"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":109,"publishedAt":22},"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",[106],{"categoryNo":107,"categoryName":108,"taxonomyType":65,"taxonomyTypeDesc":66},"01JBSEEDCAT000000000000023","Skill与智能体开发",[110,19,111],"2 azure subscription select","workflow",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":22},"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",[],[119,120,19,121],"auth","1 azure auth check","status"]