[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77KX980MFX96PCCBPF8APNG":3,"skill-same:01M77KX980MFX96PCCBPF8APNG":52},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M77KX980MFX96PCCBPF8APNG","azure-smart-city-iot-solution-builder",null,"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.","Reihantt6\u002Fsns-myagent","Reihantt6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F219822095?v=4","01M77KK94PV8B7C2D9XWXNS8DJ","Mohamad Reihan tegar prasetya","01M77KK958QFMTHYXGXFV7KZ79",2,"MIT","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fazure-smart-city-iot-solution-builder\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\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:\u002F\u002Flearn.microsoft.com\u002Fazure\u002Fiot-edge\u002F\n\nMinimum pages to review:\n\n- What is Azure IoT Edge\n- Runtime architecture\n- Supported systems\n- Version history\u002Frelease notes\n- Relevant Linux\u002FWindows 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\u002FSynapse.\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\u002Fregions, 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\u002F`.\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 `references\u002Fsmart-city-solution-template.md` to standardize outputs for each scenario, with 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","# 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:\u002F\u002Flearn.microsoft.com\u002Fazure\u002Fiot-edge\u002F\n\nMinimum pages to review:\n\n- What is Azure IoT Edge\n- Runtime architecture\n- Supported systems\n- Version history\u002Frelease notes\n- Relevant Linux\u002FWindows 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\u002FSynapse.\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\u002Fregions, 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\u002F`.\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 `references\u002Fsmart-city-solution-template.md` to standardize outputs for each scenario, with 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",{"name":5,"description":7},"main","58843b159d7a4050d6b785a98b908cce505c0b92",".agents\u002Fskills\u002Fazure-smart-city-iot-solution-builder",0,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent","https:\u002F\u002Fgithub.com\u002FReihantt6","reihsns.web.id","2026-08-19 20:08:18",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Reihantt6\u002Fsns-myagent --skill azure-smart-city-iot-solution-builder",{"tool":38,"command":39},"bunx","bunx skills add Reihantt6\u002Fsns-myagent --skill azure-smart-city-iot-solution-builder",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Reihantt6\u002Fsns-myagent --skill azure-smart-city-iot-solution-builder","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fazure-smart-city-iot-solution-builder\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fsmart-city-solution-template.md","REFERENCE","参考文档",1376,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fazure-smart-city-iot-solution-builder\u002Freferences\u002Fsmart-city-solution-template.md",[53,60,67,74,81,88],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M77XDCYZ407XYMF2T4P6F7VT","youtube-transcript","Extract transcripts from YouTube videos. Use when the user asks for a transcript, subtitles, or captions of a YouTube video and provides a YouTube URL (youtube.com\u002Fwatch?v=, youtu.be\u002F, or similar). Supports output with or without timestamps.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-transcript\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M77XD7PBC98J6MXGJJ2TJ8DX","youtube-thumbnail-design","YouTube thumbnail design with specific dimensions, contrast rules, and mobile preview optimization. Covers safe zones, text placement, face expression psychology, and A\u002FB testing. Use for: YouTube thumbnails, video cover images, click-through optimization. Triggers: youtube thumbnail, thumbnail design, video thumbnail, click through rate, ctr optimization, youtube cover, video cover image, thumbnail maker, thumbnail tips, youtube design, video preview image","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-thumbnail-design\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M77XD2541C8HXJ6RHYZP4NGJ","youtube-short-maker","Make YouTube Shorts that hold attention with Pexo — vertical 9:16, fast-paced, hook in the first 3 seconds. Describe your topic and Pexo writes the script, generates the shots, picks the models, and assembles a finished Short with music and captions. Use for YouTube Shorts: \"youtube short\", \"make a youtube short\", \"shorts video\", \"short-form video\". NOT for long-form or landscape video.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-short-maker\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M77XCXKVSYK7KTZ3PQBVVGFD","xcode-project-setup","Safely modifies Xcode projects (.pbxproj) to add Swift Packages and link files. Use this skill whenever an iOS project needs dependencies installed (e.g. Firebase, Alamofire).","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fxcode-project-setup\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M77XCR1DV8ZQK2NHWKVY4EWX","x402","Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — \"just use it\" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing touches your codebase) or \"build it in\" (install the SDK and write the key + code into your project). Walks through wallet setup, funding, .env, and a ~$1 test run. Use when the user asks about x402, pay-per-use, USDC payments, or wants Browser Use Cloud without an API key. For the free-tier signup (reverse-CAPTCHA → API key), use `browser-use cloud signup` or the `cloud` skill instead.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx402\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M77XCMD3R3ZBZQQSW6E0793B","x-twitter-scraper","Build GitHub Copilot workflows with Xquik X API SDKs, REST endpoints, hosted Apify Actor runs, MCP tools, TweetClaw OpenClaw plugin installs, signed webhooks, tweet search, user lookup, follower exports, media actions, and agent automation.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx-twitter-scraper\u002FSKILL.md",[],[]]