Mmcp.market

azure-smart-city-iot-solution-builder skill

by github·github/awesome-copilot·39k stars·MIT

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.

A100/100content scan

Is the azure-smart-city-iot-solution-builder skill safe?

Clean: nothing in its files matched our rules. We read 2 files in the folder on 2026-09-28.

No findings.

Install the azure-smart-city-iot-solution-builder skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description.

git clone --depth 1 https://github.com/github/awesome-copilot.git /tmp/awesome-copilot
mkdir -p ~/.claude/skills
cp -r /tmp/awesome-copilot/skills/azure-smart-city-iot-solution-builder ~/.claude/skills/azure-smart-city-iot-solution-builder
available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

Azure Smart City IoT Solution Builder

Use this skill to rebuild and standardize a complete workflow for Azure IoT and Smart City solutions.

When to use it

Use this skill when the user asks for things like:

  • "I want to build an IoT solution on Azure"
  • "Smart City architecture for traffic, lighting, or waste"
  • "How do I connect devices, analytics, and alerts?"
  • "I need a roadmap and backlog for an urban platform"

Objectives

  • Convert a high-level idea into a deployable architecture.
  • Reuse existing Azure-focused skills whenever possible.
  • Produce concrete artifacts the team can implement.

Workflow

0) Mandatory documentation review (before any architecture)

Before proposing architecture or technology decisions that involve edge computing, review Azure IoT Edge documentation first:

  • https://learn.microsoft.com/azure/iot-edge/

Minimum pages to review:

  • What is Azure IoT Edge
  • Runtime architecture
  • Supported systems
  • Version history/release notes
  • Relevant Linux/Windows quickstarts for the scenario

If documentation cannot be consulted, state this explicitly and continue with clearly marked assumptions.

1) Scope and constraints

Collect and confirm:

  • City domain: mobility, parking, air quality, water, energy, public safety, waste, etc.
  • Scale: number of devices, telemetry frequency, retention, regions.
  • Latency and availability objectives.
  • Regulatory and privacy constraints.
  • Existing systems to integrate (SCADA, GIS, ERP, ticketing, APIs).

2) Capability map

Split the platform into layers:

  • Device and edge: onboarding, identity, firmware, OTA, edge processing.
  • Ingestion and messaging: command and control, event routing, buffering.
  • Data and analytics: hot path vs cold path, dashboards, historical analysis.
  • Operations: observability, incident flow, SLOs.
  • Governance: RBAC, secrets, policies, network isolation.

3) Azure service selection (reference)

  • Device connectivity: Azure IoT Hub, Azure IoT Operations, IoT Edge.
  • Event streaming: Event Hubs, Service Bus, Event Grid.
  • Storage: Blob Storage, Data Lake, Cosmos DB, SQL.
  • Analytics: Azure Data Explorer, Stream Analytics, Fabric/Synapse.
  • APIs and applications: API Management, App Service, Container Apps, Functions.
  • Monitoring: Azure Monitor, Application Insights, Log Analytics.
  • Security: Key Vault, Defender for IoT, Private Endpoints, Managed Identity.

4) Non-functional design

Define and document:

  • Reliability model (zones/regions, retries, dead-letter handling, replay).
  • Security controls (zero trust, encryption, secret rotation, least privilege).
  • Cost controls (retention tiers, rightsizing, autoscaling, workload scheduling).
  • Data lifecycle (raw, curated, aggregated, archived).

5) Delivery plan

Create a phased execution:

  • Phase 1: Pilot district or single use case.
  • Phase 2: Multi-domain integration.
  • Phase 3: City-scale rollout and optimization.

For each phase, include:

  • Exit criteria
  • Dependencies
  • Risks and mitigations
  • KPI set

Reuse other skills first

There are two sources of skills:

  • Runtime-provided skills (external to this repository): only available when the Copilot host environment exposes them.
  • Local repository skills (this repository): available as local files under skills/.

Runtime-provided Azure skills (optional)

If they are available in the execution environment, delegate to these specialized skills for deeper guidance:

  • azure-kubernetes
  • azure-messaging
  • azure-observability
  • azure-storage
  • azure-rbac
  • azure-cost
  • azure-validate
  • azure-deploy

Local repository alternatives (use in this repo)

When runtime skills are not available, prioritize existing local skills in this repository:

  • azure-architecture-autopilot for architecture generation and refinement.
  • azure-resource-visualizer for resource relationship diagrams.
  • azure-role-selector for role selection guidance.
  • az-cost-optimize and azure-pricing for cost and pricing analysis.
  • azure-deployment-preflight for pre-deployment checks.
  • appinsights-instrumentation for telemetry instrumentation patterns.

If no specialized skill is available, continue with this skill and keep assumptions explicit.

Required output artifacts

Always provide these outputs:

  1. Smart City solution summary (scope, assumptions, constraints).
  2. Reference architecture (components and data flow).
  3. Security and governance checklist.
  4. Cost and scaling strategy.
  5. Phased implementation backlog (epics and milestones).

Output template

Use references/smart-city-solution-template.md to standardize outputs for each scenario, with this response structure:

  1. Context and objectives
  2. Proposed architecture
  3. Technology decisions and trade-offs
  4. Security, operations, and cost controls
  5. Phased implementation plan
  6. Risks and open questions

Guidelines

  • Do not jump to deployment before validating prerequisites.
  • Do not recommend single-region production for critical city workloads.
  • Do not omit operational ownership (who handles incidents, SLAs, change windows).
  • Clearly separate assumptions from confirmed facts.

More skills from github/awesome-copilot

  • Aacquire-codebase-knowledgeUse this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.
  • Aacreadiness-assessRun the AgentRC readiness assessment on the current repository and produce a static HTML dashboard at reports/index.html. Wraps `npx github:microsoft/agentrc readiness` and hands off rendering to the @ai-readiness-reporter custom agent. Supports policies (--policy) for org-specific scoring. Use when asked to assess, audit, or score the AI readiness of a repo.
  • Aacreadiness-generate-instructionsGenerate tailored AI agent instruction files via AgentRC instructions command. Produces .github/copilot-instructions.md (default, recommended for Copilot in VS Code) plus optional per-area .instructions.md files with applyTo globs for monorepos. Use after running /acreadiness-assess to close gaps in the AI Tooling pillar.
  • Aacreadiness-policyHelp the user pick, write, or apply an AgentRC policy. Policies customise readiness scoring by disabling irrelevant checks, overriding impact/level, setting pass-rate thresholds, or chaining org baselines with team overrides. Use when the user asks about strict mode, AI-only scoring, custom weights, CI gating, or wants org-wide standardisation.
  • Aad-campaign-analyzerUse this skill when the user shares ad campaign performance data and asks what to cut, scale, or test. Trigger for prompts like "analyze my ad campaigns", "where am I wasting ad spend", "reallocate my ad budget", "which ads are actually working", or "ROAS analysis". Do not trigger for campaign planning or creative generation without performance data.
  • Aadd-educational-commentsAdd educational comments to the file specified, or prompt asking for file to comment if one is not provided.
  • Aadobe-illustrator-scriptingWrite, debug, and optimize Adobe Illustrator automation scripts using ExtendScript (JavaScript/JSX). Use when creating or modifying scripts that manipulate documents, layers, paths, text frames, colors, symbols, artboards, or any Illustrator DOM objects. Covers the complete JavaScript object model, coordinate system, measurement units, export workflows, and scripting best practices.
  • Aagent-architectureDesign AI agent architectures through requirements discovery, or audit and diagnose architectural flaws in existing agents. Architecture only; excludes implementation and general code review.
  • Aagent-governancePatterns and techniques for adding governance, safety, and trust controls to AI agent systems. Use this skill when: - Building AI agents that call external tools (APIs, databases, file systems) - Implementing policy-based access controls for agent tool usage - Adding semantic intent classification to detect dangerous prompts - Creating trust scoring systems for multi-agent workflows - Building audit trails for agent actions and decisions - Enforcing rate limits, content filters, or tool restrictions on agents - Working with any agent framework (PydanticAI, CrewAI, OpenAI Agents, LangChain, AutoGen)
  • Aagent-owasp-complianceCheck any AI agent codebase against the OWASP Agentic Security Initiative (ASI) Top 10 risks. Use this skill when: - Evaluating an agent system's security posture before production deployment - Running a compliance check against OWASP ASI 2026 standards - Mapping existing security controls to the 10 agentic risks - Generating a compliance report for security review or audit - Comparing agent framework security features against the standard - Any request like "is my agent OWASP compliant?", "check ASI compliance", or "agentic security audit"
  • Aagent-skill-stackFind, evaluate, and assemble the smallest compatible set of AI Agent Skills for an end-to-end natural-language goal. Use when a user wants Skills for a multi-step workflow, asks which Skills fit a project, needs an installed-Skill audit or conflict check, has low Skill recall, wants indirect helpers such as humanizers or compliance checks, or wants a project-specific Skill Stack with controlled installation. Search local Skills, registries, GitHub, and OpenCLI; compare adoption, verified fit, safety, and overlap. Do not use for locating one known or common Skill; use the generic find-skills workflow.
  • Aagent-supply-chainVerify supply chain integrity for AI agent plugins, tools, and dependencies. Use this skill when: - Generating SHA-256 integrity manifests for agent plugins or tool packages - Verifying that installed plugins match their published manifests - Detecting tampered, modified, or untracked files in agent tool directories - Auditing dependency pinning and version policies for agent components - Building provenance chains for agent plugin promotion (dev → staging → production) - Any request like "verify plugin integrity", "generate manifest", "check supply chain", or "sign this plugin"

All agent skills → · MCP servers