{"kind":"Skill","metadata":{"namespace":"community","name":"azure-smart-city-iot-solution-builder","version":"0.1.0"},"spec":{"description":"Design and plan end-to-end Azure IoT and Smart City solutions: requirements, architecture, security, operations, cost, and a phased delivery plan with concrete implementation artifacts.","files":{"SKILL.md":"---\nname: azure-smart-city-iot-solution-builder\ndescription: 'Design and plan end-to-end Azure IoT and Smart City solutions: requirements, architecture, security, operations, cost, and a phased delivery plan with concrete implementation artifacts.'\n---\n\n# Azure Smart City IoT Solution Builder\n\nUse this skill to rebuild and standardize a complete workflow for Azure IoT and Smart City solutions.\n\n## When to use it\n\nUse this skill when the user asks for things like:\n\n- \"I want to build an IoT solution on Azure\"\n- \"Smart City architecture for traffic, lighting, or waste\"\n- \"How do I connect devices, analytics, and alerts?\"\n- \"I need a roadmap and backlog for an urban platform\"\n\n## Objectives\n\n- Convert a high-level idea into a deployable architecture.\n- Reuse existing Azure-focused skills whenever possible.\n- Produce concrete artifacts the team can implement.\n\n## Workflow\n\n### 0) Mandatory documentation review (before any architecture)\n\nBefore proposing architecture or technology decisions that involve edge computing, review Azure IoT Edge documentation first:\n\n- https://learn.microsoft.com/azure/iot-edge/\n\nMinimum pages to review:\n\n- What is Azure IoT Edge\n- Runtime architecture\n- Supported systems\n- Version history/release notes\n- Relevant Linux/Windows quickstarts for the scenario\n\nIf documentation cannot be consulted, state this explicitly and continue with clearly marked assumptions.\n\n### 1) Scope and constraints\n\nCollect and confirm:\n\n- City domain: mobility, parking, air quality, water, energy, public safety, waste, etc.\n- Scale: number of devices, telemetry frequency, retention, regions.\n- Latency and availability objectives.\n- Regulatory and privacy constraints.\n- Existing systems to integrate (SCADA, GIS, ERP, ticketing, APIs).\n\n### 2) Capability map\n\nSplit the platform into layers:\n\n- Device and edge: onboarding, identity, firmware, OTA, edge processing.\n- Ingestion and messaging: command and control, event routing, buffering.\n- Data and analytics: hot path vs cold path, dashboards, historical analysis.\n- Operations: observability, incident flow, SLOs.\n- Governance: RBAC, secrets, policies, network isolation.\n\n### 3) Azure service selection (reference)\n\n- Device connectivity: Azure IoT Hub, Azure IoT Operations, IoT Edge.\n- Event streaming: Event Hubs, Service Bus, Event Grid.\n- Storage: Blob Storage, Data Lake, Cosmos DB, SQL.\n- Analytics: Azure Data Explorer, Stream Analytics, Fabric/Synapse.\n- APIs and applications: API Management, App Service, Container Apps, Functions.\n- Monitoring: Azure Monitor, Application Insights, Log Analytics.\n- Security: Key Vault, Defender for IoT, Private Endpoints, Managed Identity.\n\n### 4) Non-functional design\n\nDefine and document:\n\n- Reliability model (zones/regions, retries, dead-letter handling, replay).\n- Security controls (zero trust, encryption, secret rotation, least privilege).\n- Cost controls (retention tiers, rightsizing, autoscaling, workload scheduling).\n- Data lifecycle (raw, curated, aggregated, archived).\n\n### 5) Delivery plan\n\nCreate a phased execution:\n\n- Phase 1: Pilot district or single use case.\n- Phase 2: Multi-domain integration.\n- Phase 3: City-scale rollout and optimization.\n\nFor each phase, include:\n\n- Exit criteria\n- Dependencies\n- Risks and mitigations\n- KPI set\n\n## Reuse other skills first\n\nThere are two sources of skills:\n\n- Runtime-provided skills (external to this repository): only available when the Copilot host environment exposes them.\n- Local repository skills (this repository): available as local files under `skills/`.\n\n### Runtime-provided Azure skills (optional)\n\nIf they are available in the execution environment, delegate to these specialized skills for deeper guidance:\n\n- `azure-kubernetes`\n- `azure-messaging`\n- `azure-observability`\n- `azure-storage`\n- `azure-rbac`\n- `azure-cost`\n- `azure-validate`\n- `azure-deploy`\n\n### Local repository alternatives (use in this repo)\n\nWhen runtime skills are not available, prioritize existing local skills in this repository:\n\n- `azure-architecture-autopilot` for architecture generation and refinement.\n- `azure-resource-visualizer` for resource relationship diagrams.\n- `azure-role-selector` for role selection guidance.\n- `az-cost-optimize` and `azure-pricing` for cost and pricing analysis.\n- `azure-deployment-preflight` for pre-deployment checks.\n- `appinsights-instrumentation` for telemetry instrumentation patterns.\n\nIf no specialized skill is available, continue with this skill and keep assumptions explicit.\n\n## Required output artifacts\n\nAlways provide these outputs:\n\n1. Smart City solution summary (scope, assumptions, constraints).\n2. Reference architecture (components and data flow).\n3. Security and governance checklist.\n4. Cost and scaling strategy.\n5. Phased implementation backlog (epics and milestones).\n\n## Output template\n\nUse this response structure:\n\n1. Context and objectives\n2. Proposed architecture\n3. Technology decisions and trade-offs\n4. Security, operations, and cost controls\n5. Phased implementation plan\n6. Risks and open questions\n\n## Guidelines\n\n- Do not jump to deployment before validating prerequisites.\n- Do not recommend single-region production for critical city workloads.\n- Do not omit operational ownership (who handles incidents, SLAs, change windows).\n- Clearly separate assumptions from confirmed facts.\n","references/smart-city-solution-template.md":"# Smart City IoT Solution Template\n\nUse this template to standardize outputs for each new smart city scenario.\n\n## 1. Use case summary\n\n- Domain:\n- Stakeholders:\n- Problem statement:\n- Success metrics:\n\n## 2. Device and data profile\n\n- Device types and count:\n- Telemetry schema:\n- Ingestion rate:\n- Command/control requirements:\n- Retention policy:\n\n## 3. Reference architecture\n\n- Edge and field layer:\n- Ingestion layer:\n- Processing layer:\n- Storage layer:\n- API and integration layer:\n- Monitoring and security layer:\n\n## 4. NFR checklist\n\n- Availability target:\n- Latency target:\n- Security controls:\n- Data privacy constraints:\n- DR strategy:\n- Cost target:\n\n## 5. Phased roadmap\n\n### Phase 1 - Pilot\n\n- Scope:\n- Deliverables:\n- Exit criteria:\n\n### Phase 2 - Scale\n\n- Scope:\n- Deliverables:\n- Exit criteria:\n\n### Phase 3 - Optimize\n\n- Scope:\n- Deliverables:\n- Exit criteria:\n\n## 6. Initial backlog baseline\n\n- Epic: Device onboarding and identity\n- Epic: Telemetry ingestion and routing\n- Epic: Real-time alerting and incident workflow\n- Epic: Historical analytics and reporting\n- Epic: Security and compliance hardening\n- Epic: Governance and cost optimization\n\n## 7. Risks\n\n- Vendor/device interoperability gaps\n- Network reliability in field locations\n- Data quality issues and schema drift\n- Over-retention that increases costs\n- Ambiguity in operational ownership\n"},"import":{"commit_sha":"541b7819d8c3545c6df122491af4fa1eae415779","imported_at":"2026-05-18T20:07:09Z","license_text":"MIT License\n\nCopyright GitHub, Inc.\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE.","owner":"github","repo":"github/awesome-copilot","source_url":"https://github.com/github/awesome-copilot/tree/541b7819d8c3545c6df122491af4fa1eae415779/skills/azure-smart-city-iot-solution-builder"}},"content_hash":[110,190,93,27,26,200,166,254,228,121,246,27,225,236,222,23,205,47,88,150,93,199,151,123,99,193,209,177,121,25,113,42],"trust_level":"unsigned","yanked":false}