Official agent skill

Azure Smart City Iot Solution Builder

by github in github/awesome-copilot

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.

OfficialMITAuto-check passedDevOps & Cloud

Install Azure Smart City Iot Solution Builder

skills CLI
$ npx skills add github/awesome-copilot --skill azure-smart-city-iot-solution-builder -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install github/awesome-copilot azure-smart-city-iot-solution-builder --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/azure-smart-city-iot-solution-builder .claude/skills/azure-smart-city-iot-solution-builder && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
azure-smart-city-iot-solution-builder
GitHub stars
40k
Used in
1 other repo
Token cost
~1.4k tokens
SKILL.md length
631 words
Files
2 (incl. references)
Skills in repo
417
Repo updated
First seen
Licence
MIT

At a glance

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.

  • Works in 6 steps: Mandatory documentation review (before… → Scope and constraints → Capability map → …
  • Tasks that involve Security operations
  • SKILL.md covers When to use it, Objectives, Workflow and Reuse other skills first, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Azure Smart City Iot Solution Builder is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. 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.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/smart-city-solution-template.md`).

It sits in DevOps & Cloud, covering Security operations. It works with Microsoft Azure. The repository describes itself as: Community-contributed instructions, agents, skills, and configurations to help you make the most of GitHub Copilot. The licence is MIT.

When your agent uses it

  • Tasks that involve Security operations

Example prompts

  • “/azure-smart-city-iot-solution-builder”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Mandatory documentation review (before any architecture)
  2. Scope and constraints
  3. Capability map
  4. Azure service selection (reference)
  5. Non-functional design
  6. Delivery plan

What it can do on your machine

Read from SKILL.md and the folder at commit 727ff2e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • learn.microsoft.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Azure Smart City Iot Solution Builder loads about 1.4k tokens when it runs, and up to ~1.7k if it reads all its reference files. Until then it costs about 56 tokens; SKILL.md has 631 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~56
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from github/awesome-copilot at commit 727ff2e, republished under its MIT licence (© github). 631 words, ~1,359 tokens.

Download SKILL.mdSave it as .claude/skills/azure-smart-city-iot-solution-builder/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
azure-smart-city-iot-solution-builder
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.

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:

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
Show full SKILL.md (246 more words)Show less

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.

© github, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/azure-smart-city-iot-solution-builder of github/awesome-copilot.

  • SKILL.md
  • references/smart-city-solution-template.md

Open the folder on GitHubat commit 727ff2e

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in github/awesome-copilot, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Azure Smart City Iot Solution Builder next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Azure Smart City Iot Solution Builder compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Azure Smart City Iot Solution Builder this skillgithub/awesome-copilot40k1 repos~1.4kAutomated safety check: PassMIT
Conducting Cloud Incident Responsemukul975/Anthropic-Cybersecurity-Skills34k—~3kAutomated safety check: PassApache-2.0
Azure Kusto Irqlmicrosoft/GitHub-Copilot-for-Azure255—~2.6kAutomated safety check: PassMIT
Investigating GCP Incidentstrilwu/secskills156—~2.2kAutomated safety check: PassMIT
Investigating Azure Incidentstrilwu/secskills156—~5.3kAutomated safety check: PassMIT
Sentinelvinayaklatthe/microsoft-security-skills175—~2.2kAutomated safety check: PassMIT

Similar skills

  • Conducting Cloud Incident Response

    mukul975/Anthropic-Cybersecurity-Skills

    Respond to security incidents in AWS, Azure, and GCP via identity-based containment, cloud-native log analysis (CloudTrail, Azure Activity Logs, GCP Audit Logs), resource isolation, and forensic…

    34k GitHub stars~3k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed
  • Azure Kusto Irql

    microsoft/GitHub-Copilot-for-Azure

    Official

    Compose IRQL (Incident Response Query Language) queries for Kusto cybersecurity investigations.

    255 GitHub stars~2.6k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Investigate a security incident in Google Cloud — establishing what audit logging exists before trusting a gap, reconstructing activity from Cloud Audit Logs, triaging service-account and OAuth…

    156 GitHub stars~2.2k tokensUpdated 1 mo ago
    SecurityAuto-check passed
  • Investigate security incidents in Microsoft Azure (resource and subscription control plane) -- reconstruct attacker activity from the Azure Activity Log and resource/data-plane diagnostic logs…

    156 GitHub stars~5.3k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed
  • Sentinel

    vinayaklatthe/microsoft-security-skills

    Guidance for designing and operating Microsoft Sentinel, the cloud-native SIEM and SOAR delivered through the Defender portal.

    175 GitHub stars~2.2k tokensUpdated 3 mo ago
    SecurityAuto-check passed
  • Cloud Misconfig Auditor

    criptogus/agent-evolve-network

    Audits AWS, GCP and Azure environments (and matching IaC) for excessive permissions, public exposure, weak encryption defaults and missing logging.

    288 GitHub stars~965 tokensUpdated 27 days ago
    DevOps & CloudAuto-check passed

More from github/awesome-copilot

All 417 skills in this repo
  • Acquire Codebase Knowledge

    github/awesome-copilot

    Official

    Maps an unfamiliar codebase into seven evidence-backed documents in docs/codebase/, using a scan script and templates, for onboarding or architecture write-ups.

    40k GitHub starsUsed in 1 repo~2.3k tokens
    Auto-check passed
  • Azure Architecture Autopilot

    github/awesome-copilot

    Official

    Designs Azure infrastructure from a natural-language description, or diagrams an existing resource group, then refines the design through conversation and deploys it with Bicep.

    40k GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed
  • Draw.io Diagram Generator

    github/awesome-copilot

    Official

    Generates, edits and validates draw.io files with correct mxGraph XML, covering flowcharts, architecture, sequence, ER and UML class diagrams.

    40k GitHub starsUsed in 1 repo~4.9k tokens
    Auto-check passed
  • Credit Risk Data Cleaning

    github/awesome-copilot

    Official

    Cleans raw credit data and screens variables before loan modeling, dropping unstable, noisy or redundant features and writing an Excel report of every step.

    40k GitHub starsUsed in 1 repo~1.5k tokens
    Auto-check passed
  • Daily Focus Board

    github/awesome-copilot

    Official

    Builds a warm, browser-based daily focus board the user updates by talking to their agent, with Eisenhower priorities, a brain-dump box and kind not-today carryover.

    40k GitHub stars~3k tokensUpdated today
    Auto-check passed
  • Python Pypi Package Builder

    github/awesome-copilot

    Official

    End-to-end skill for building, testing, linting, versioning, and publishing a production-grade Python library to PyPI.

    40k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed

Works with

Questions about Azure Smart City Iot Solution Builder

What does Azure Smart City Iot Solution Builder do?

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. Azure Smart City Iot Solution Builder is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. 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.

When should I use Azure Smart City Iot Solution Builder?

Azure Smart City Iot Solution Builder fits situations like: tasks that involve Security operations.

How do I install Azure Smart City Iot Solution Builder in Claude Code?

Run `npx skills add github/awesome-copilot --skill azure-smart-city-iot-solution-builder -a claude-code`. Or copy the skill folder (skills/azure-smart-city-iot-solution-builder in github/awesome-copilot) into .claude/skills/azure-smart-city-iot-solution-builder in your project. Claude Code loads it when a task matches its description.

How do I install Azure Smart City Iot Solution Builder in Codex?

Run `npx skills add github/awesome-copilot --skill azure-smart-city-iot-solution-builder -a codex`. Or copy the skill folder (skills/azure-smart-city-iot-solution-builder in github/awesome-copilot) into .agents/skills/azure-smart-city-iot-solution-builder in your project. Codex loads it when a task matches its description.

Can I use Azure Smart City Iot Solution Builder in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add github/awesome-copilot --skill azure-smart-city-iot-solution-builder -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/azure-smart-city-iot-solution-builder, .gemini/skills/azure-smart-city-iot-solution-builder, .github/skills/azure-smart-city-iot-solution-builder and .opencode/skills/azure-smart-city-iot-solution-builder in your project.

What does Azure Smart City Iot Solution Builder need to run?

SKILL.md names no scripts, command-line tools or credentials: Azure Smart City Iot Solution Builder is instructions for the agent only.

Does Azure Smart City Iot Solution Builder access the network?

SKILL.md names 1 domain. As links in the text: learn.microsoft.com. This is read from the text; nothing was executed.

Is Azure Smart City Iot Solution Builder safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Azure Smart City Iot Solution Builder use?

Azure Smart City Iot Solution Builder is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Azure Smart City Iot Solution Builder use?

About 1.4k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 344 tokens, read only when the agent opens those files.

What are the alternatives to Azure Smart City Iot Solution Builder?

Skills that share tags, products or a category with Azure Smart City Iot Solution Builder: Conducting Cloud Incident Response (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), Azure Kusto Irql (microsoft/GitHub-Copilot-for-Azure, 255 stars), Investigating GCP Incidents (trilwu/secskills, 156 stars) and Investigating Azure Incidents (trilwu/secskills, 156 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Azure Smart City Iot Solution Builder?

github (a GitHub organization, an official publisher) maintains it in github/awesome-copilot, which has 39,748 GitHub stars. The repository holds 417 skills in this directory. The repository was last updated on October 7, 2026.

Source: github/awesome-copilot on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.