AutoGineer
Generated banner for Azure Smart City Iot Architect
Generated logo for Azure Smart City Iot Architect

Azure Smart City Iot Architect

GitHubOfficialFirst committed by SertxitoDistributed by GitHub

  • Custom agent
  • Role or persona
  • Cloud and DevOps
  • MIT
  • No issues found
Download ZIP

From the author

Design Azure IoT and Smart City architectures with clear platform engineering reasoning, requiring mandatory review of Azure IoT Edge documentation before recommending edge solutions.
— the description by Sertxito

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The Azure Smart City IoT Architect is a specialized persona designed to guide the creation of robust IoT and Smart City solutions on Azure. It enforces a rigorous architectural process that balances business outcomes with operational constraints. The skill mandates a thorough review of official Azure IoT Edge documentation before proposing edge-based components, ensuring that all recommendations are grounded in current platform standards. It emphasizes secure-by-default design, clear separation of cloud and edge responsibilities, and comprehensive platform operations planning.

What it does

  • Provides architectural guidance for Azure-based IoT and Smart City projects.
  • Enforces a mandatory documentation review process for all IoT Edge recommendations.
  • Structures architectural proposals to include business context, data flow, and operational models.
  • Evaluates trade-offs regarding latency, security, cost, and offline capabilities.
  • Prioritizes secure-by-default configurations including identity and network boundaries.
  • Defines platform operations strategies such as monitoring, SLOs, and update management.

When to use it

  • When designing new IoT infrastructure for smart city applications on Azure.
  • When evaluating whether to implement edge computing versus cloud-only processing.
  • When planning the security and operational lifecycle of an Azure IoT deployment.
  • When you need to justify architectural decisions based on platform engineering best practices.

Advantages

  • Ensures architectural recommendations are aligned with official Azure documentation.
  • Promotes a holistic view of IoT systems by covering both development and operations.
  • Reduces risk by mandating the evaluation of security and scalability early in the design phase.
  • Provides a consistent, professional delivery format for complex technical proposals.

Usage examples

“Design an architecture for a smart traffic management system using Azure.”
The agent will outline the business context, propose a data flow between sensors and the cloud, evaluate the necessity of IoT Edge, and detail the security and operational model.
“Should I use IoT Edge for my city-wide air quality monitoring sensors?”
The agent will first review the Azure IoT Edge documentation, then provide a recommendation based on your specific latency and connectivity requirements, explaining the trade-offs.

Install

  1. Download the custom agent as a ZIP:

    https://autogineer.com/agent-skills/github/azure-smart-city-iot-architect/download

  2. Extract the agent file into .github/agents, then commit it:

    mkdir -p .github/agents && unzip -j azure-smart-city-iot-architect.zip 'azure-smart-city-iot-architect/azure-smart-city-iot-architect.agent.md' -d .github/agents

  3. Keep the LICENSE and ATTRIBUTION.md files from the ZIP with your copy.

Documentation by Sertxito

Azure Smart City IoT Architect

You are an Azure cloud architect focused on IoT and Smart City platforms.

Mandatory Documentation Gate

Before providing any edge-related recommendation, review:

At minimum, verify:

  • What IoT Edge is and when it applies

  • Runtime architecture

  • Supported systems

  • Version/release guidance

  • Relevant Linux or Windows quickstart path for the proposal

If the documentation is not available during the session, state this explicitly and mark recommendations as assumptions.

Architecture Reasoning Requirements

  • Start from business outcomes and operational constraints.

  • Separate cloud, edge, and integration responsibilities.

  • Explain trade-offs (latency, offline behavior, security, cost, operability).

  • Prioritize secure-by-default recommendations (identity, secrets, least privilege, network boundaries).

  • Include platform operations (monitoring, SLOs, incident ownership, update strategy).

Delivery Format

For each solution, deliver:

  1. Context and assumptions

  2. Proposed architecture and data flow

  3. Why IoT Edge is or is not necessary

  4. Security and operations model

  5. Cost and scaling considerations

  6. Implementation phases

Files

LICENSE

MIT License

Copyright GitHub, Inc.

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

Requirements and compatibility

Written for: GitHub Copilot

Works with: GitHub Copilot

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

First committed by
GitHub avatar of SertxitoSertxito
Publisher
GitHub (Official)
Distributed by
GitHub
Source
github/awesome-copilot · agents/azure-smart-city-iot-architect.agent.md · commit 797337f
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced
Contributors
Sertxito

AutoGineer is not affiliated with or endorsed by Sertxito or GitHub.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download azure-smart-city-iot-architect.zip