[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77KRXTMV5M7MVC5BFXTX3RA":3,"skill-same:01M77KRXTMV5M7MVC5BFXTX3RA":56},{"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},"01M77KRXTMV5M7MVC5BFXTX3RA","arduino-azure-iot-edge-integration",null,"Design and implement Arduino integration with Azure IoT Hub and IoT Edge, including secure provisioning, resilient telemetry, command handling, and production guardrails.","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\u002Farduino-azure-iot-edge-integration\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: arduino-azure-iot-edge-integration\ndescription: 'Design and implement Arduino integration with Azure IoT Hub and IoT Edge, including secure provisioning, resilient telemetry, command handling, and production guardrails.'\n---\n\n# Arduino Azure IoT Edge Integration\n\nUse this skill when the user needs to connect Arduino-class devices to Azure IoT, especially in edge-heavy scenarios (gateways, intermittent networks, offline buffering, and local actuation).\n\n## When to use it\n\nUse this skill for requests such as:\n\n- \"I want to connect Arduino sensors to Azure\"\n- \"How do I send MQTT telemetry to IoT Hub?\"\n- \"I need an edge gateway for field devices\"\n- \"I want cloud-to-device commands and OTA configuration updates\"\n\n## Mandatory documentation review\n\nBefore recommending an IoT Edge topology or runtime behavior, review:\n\n- https:\u002F\u002Flearn.microsoft.com\u002Fazure\u002Fiot-edge\u002F\n\nIf documentation cannot be consulted, proceed with explicit assumptions and highlight them in a dedicated section.\n\n## Official Arduino references and best practices (required)\n\nBefore proposing firmware, wiring, or communication implementation details, consult official Arduino sources first:\n\n- https:\u002F\u002Fwww.arduino.cc\u002Fen\u002FGuide\n- https:\u002F\u002Fdocs.arduino.cc\u002F\n- https:\u002F\u002Fdocs.arduino.cc\u002Flanguage-reference\u002F\n- references\u002Farduino-official-best-practices.md\n\nWhen choosing between implementation alternatives, prioritize official Arduino guidance over community snippets unless there is a clear technical reason to deviate.\n\n## Objectives\n\n- Produce a secure end-to-end reference path from the Arduino device to cloud insights.\n- Handle unstable links (store-and-forward, retries, idempotency).\n- Define an actionable device and cloud backlog.\n\n## Integration patterns\n\n### Pattern A: Arduino direct to IoT Hub\n\nUse when connectivity is stable and cloud latency is acceptable.\n\n- Protocol: MQTT over TLS.\n- Identity: per-device credentials (SAS or X.509).\n- Telemetry payload: compact JSON with timestamp, device ID, metrics, and optional quality flags.\n\n### Pattern B: Arduino to local gateway, then IoT Edge\n\nUse when links are constrained, local control is required, or batching improves cost\u002Freliability.\n\n- Arduino communicates with a local gateway (serial, BLE, local MQTT, RS-485, Modbus bridge).\n- The gateway publishes upstream through the IoT Edge runtime and routes data to IoT Hub.\n- Local modules can filter, aggregate, and trigger actions even during cloud outages.\n\n## Design flow\n\n### 1) Device contract\n\nDefine:\n\n- Sensor catalog and units.\n- Sampling frequency and expected throughput.\n- Message schema versioning strategy.\n- Desired\u002Freported device twin properties to control runtime behavior.\n\n### 2) Security baseline\n\nRequire:\n\n- Unique identity per device.\n- No hardcoded secrets in source code or firmware artifacts.\n- Credential rotation strategy.\n- Signed firmware and a controlled update process when possible.\n\n### 3) Reliability and offline behavior\n\nPlan and document:\n\n- Backoff with jitter.\n- Local queue\u002Fbuffer strategy with bounded size.\n- Duplicate suppression or downstream idempotent processing.\n- Fallback to last-known-good configuration.\n\n### 4) Cloud and edge routing\n\nDefine routes for:\n\n- Raw telemetry to cold storage.\n- Curated telemetry to hot analytics.\n- Alerts to operations channels.\n- Commands and configuration back to edge\u002Fdevice.\n\n### 5) Observability\n\nSpecify minimum operations telemetry:\n\n- Device heartbeat and firmware version.\n- Connectivity state transitions.\n- Message send success\u002Ferror counters.\n- Gateway module health and restart reasons.\n\n## Reuse other skills\n\nWhen relevant, combine with:\n\n- `azure-smart-city-iot-solution-builder` for city-wide architecture and phased rollout.\n- `azure-resource-visualizer` for relationship diagrams.\n- `appinsights-instrumentation` for app and service telemetry patterns.\n\nAlso use `references\u002Farduino-official-best-practices.md` as a quality baseline for firmware and hardware recommendations, and `references\u002Farduino-iot-checklist.md` before finalizing architecture or implementation guidance.\n\n## Required output\n\nAlways provide:\n\n1. Chosen connectivity pattern and rationale.\n2. Message contract (fields, units, sample payload).\n3. Security checklist for identity\u002Fcredentials\u002Fupdates.\n4. Reliability plan (retry, buffering, dedupe).\n5. Implementation backlog (firmware, gateway, cloud).\n\n## Output template\n\n1. Scenario and assumptions\n2. Recommended architecture\n3. Device and gateway contract\n4. Security and reliability controls\n5. Deployment plan and validation tests\n\n## Guidelines\n\n- Do not propose production deployments with shared credentials across devices.\n- Do not assume always-on connectivity in field deployments.\n- Do not omit command authorization and auditing in actuator scenarios.\n","# Arduino Azure IoT Edge Integration\n\nUse this skill when the user needs to connect Arduino-class devices to Azure IoT, especially in edge-heavy scenarios (gateways, intermittent networks, offline buffering, and local actuation).\n\n## When to use it\n\nUse this skill for requests such as:\n\n- \"I want to connect Arduino sensors to Azure\"\n- \"How do I send MQTT telemetry to IoT Hub?\"\n- \"I need an edge gateway for field devices\"\n- \"I want cloud-to-device commands and OTA configuration updates\"\n\n## Mandatory documentation review\n\nBefore recommending an IoT Edge topology or runtime behavior, review:\n\n- https:\u002F\u002Flearn.microsoft.com\u002Fazure\u002Fiot-edge\u002F\n\nIf documentation cannot be consulted, proceed with explicit assumptions and highlight them in a dedicated section.\n\n## Official Arduino references and best practices (required)\n\nBefore proposing firmware, wiring, or communication implementation details, consult official Arduino sources first:\n\n- https:\u002F\u002Fwww.arduino.cc\u002Fen\u002FGuide\n- https:\u002F\u002Fdocs.arduino.cc\u002F\n- https:\u002F\u002Fdocs.arduino.cc\u002Flanguage-reference\u002F\n- references\u002Farduino-official-best-practices.md\n\nWhen choosing between implementation alternatives, prioritize official Arduino guidance over community snippets unless there is a clear technical reason to deviate.\n\n## Objectives\n\n- Produce a secure end-to-end reference path from the Arduino device to cloud insights.\n- Handle unstable links (store-and-forward, retries, idempotency).\n- Define an actionable device and cloud backlog.\n\n## Integration patterns\n\n### Pattern A: Arduino direct to IoT Hub\n\nUse when connectivity is stable and cloud latency is acceptable.\n\n- Protocol: MQTT over TLS.\n- Identity: per-device credentials (SAS or X.509).\n- Telemetry payload: compact JSON with timestamp, device ID, metrics, and optional quality flags.\n\n### Pattern B: Arduino to local gateway, then IoT Edge\n\nUse when links are constrained, local control is required, or batching improves cost\u002Freliability.\n\n- Arduino communicates with a local gateway (serial, BLE, local MQTT, RS-485, Modbus bridge).\n- The gateway publishes upstream through the IoT Edge runtime and routes data to IoT Hub.\n- Local modules can filter, aggregate, and trigger actions even during cloud outages.\n\n## Design flow\n\n### 1) Device contract\n\nDefine:\n\n- Sensor catalog and units.\n- Sampling frequency and expected throughput.\n- Message schema versioning strategy.\n- Desired\u002Freported device twin properties to control runtime behavior.\n\n### 2) Security baseline\n\nRequire:\n\n- Unique identity per device.\n- No hardcoded secrets in source code or firmware artifacts.\n- Credential rotation strategy.\n- Signed firmware and a controlled update process when possible.\n\n### 3) Reliability and offline behavior\n\nPlan and document:\n\n- Backoff with jitter.\n- Local queue\u002Fbuffer strategy with bounded size.\n- Duplicate suppression or downstream idempotent processing.\n- Fallback to last-known-good configuration.\n\n### 4) Cloud and edge routing\n\nDefine routes for:\n\n- Raw telemetry to cold storage.\n- Curated telemetry to hot analytics.\n- Alerts to operations channels.\n- Commands and configuration back to edge\u002Fdevice.\n\n### 5) Observability\n\nSpecify minimum operations telemetry:\n\n- Device heartbeat and firmware version.\n- Connectivity state transitions.\n- Message send success\u002Ferror counters.\n- Gateway module health and restart reasons.\n\n## Reuse other skills\n\nWhen relevant, combine with:\n\n- `azure-smart-city-iot-solution-builder` for city-wide architecture and phased rollout.\n- `azure-resource-visualizer` for relationship diagrams.\n- `appinsights-instrumentation` for app and service telemetry patterns.\n\nAlso use `references\u002Farduino-official-best-practices.md` as a quality baseline for firmware and hardware recommendations, and `references\u002Farduino-iot-checklist.md` before finalizing architecture or implementation guidance.\n\n## Required output\n\nAlways provide:\n\n1. Chosen connectivity pattern and rationale.\n2. Message contract (fields, units, sample payload).\n3. Security checklist for identity\u002Fcredentials\u002Fupdates.\n4. Reliability plan (retry, buffering, dedupe).\n5. Implementation backlog (firmware, gateway, cloud).\n\n## Output template\n\n1. Scenario and assumptions\n2. Recommended architecture\n3. Device and gateway contract\n4. Security and reliability controls\n5. Deployment plan and validation tests\n\n## Guidelines\n\n- Do not propose production deployments with shared credentials across devices.\n- Do not assume always-on connectivity in field deployments.\n- Do not omit command authorization and auditing in actuator scenarios.\n",{"name":5,"description":7},"main","58843b159d7a4050d6b785a98b908cce505c0b92",".agents\u002Fskills\u002Farduino-azure-iot-edge-integration",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 arduino-azure-iot-edge-integration",{"tool":38,"command":39},"bunx","bunx skills add Reihantt6\u002Fsns-myagent --skill arduino-azure-iot-edge-integration",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Reihantt6\u002Fsns-myagent --skill arduino-azure-iot-edge-integration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Farduino-azure-iot-edge-integration\u002FSKILL.md",true,[46,52],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Farduino-iot-checklist.md","REFERENCE","参考文档",1298,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Farduino-azure-iot-edge-integration\u002Freferences\u002Farduino-iot-checklist.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Farduino-official-best-practices.md",2337,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Farduino-azure-iot-edge-integration\u002Freferences\u002Farduino-official-best-practices.md",[57,64,71,78,85,92],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"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":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"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":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"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":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"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",[],[]]