[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6E3J97B8WAVVASV6250F94D":3,"skill-same:01M6E3J97B8WAVVASV6250F94D":90},{"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":26,"publishedAt":53,"linkOnly":54,"markdownContent":55,"markdownBody":56,"frontMatter":57,"refName":66,"commitSha":67,"skillDirectory":68,"forksCount":69,"repositoryHtmlUrl":70,"repositoryHomepageUrl":71,"ownerHtmlUrl":72,"ownerBlogUrl":73,"ownerDescription":74,"updatedAt":75,"install":76,"resources":89},"01M6E3J97B8WAVVASV6250F94D","volt-power",null,"Power management audit — analyze sleep modes, wake sources, power state machines, radio duty cycles, and battery life estimates. Use when asked to \"audit power usage\", \"optimize battery life\", \"review power management\", \"why is my battery draining\", \"power budget analysis\", or \"sleep mode review\".","tonone-ai\u002Ftonone","tonone-ai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F252718527?v=4","01M6E0753HQVTQWJCQCV4AHAAS","tonone.ai","01M6E075828PMH1WMX0VEB5SV8",77,"MIT","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fskills\u002Fvolt-power\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000040","财务",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52],"volt","volt power","power","when","review","wake","mode","websearch","sleep","sources","state machines","power management","life","optimize","use","edit","write","read","analyze","Bash","why","analysis","Budget","audit","code","hello","2026-11-10 10:12:30",false,"---\nname: volt-power\ndescription: Power management audit — analyze sleep modes, wake sources, power state machines, radio duty cycles, and battery life estimates. Use when asked to \"audit power usage\", \"optimize battery life\", \"review power management\", \"why is my battery draining\", \"power budget analysis\", or \"sleep mode review\".\nallowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion\nversion: 0.6.4\nauthor: tonone-ai \u003Chello@tonone.ai>\nlicense: MIT\ncompatibility: Designed for Claude Code\ntags: [engineering, embedded, iot, power]\n---\n\n\u003C!-- GENERATED from SKILL.md.tmpl by scripts\u002Fgen-skill-docs.py — edit the .tmpl or skills\u002F_sections\u002F*.md, not this file -->\n\n# Power Management Audit\n\nYou are Volt — the embedded and IoT engineer on the Engineering Team. Audit power before you optimize anything.\n\n## Steps\n\n### Step 0: Detect Environment\n\nScan for power management code:\n\n```bash\n# Power management indicators\nfind . -name \"*.c\" -o -name \"*.cpp\" -o -name \"*.h\" -o -name \"*.rs\" 2>\u002Fdev\u002Fnull | \\\n  xargs grep -l \"sleep\\|power\\|wakeup\\|deepsleep\\|light_sleep\\|standby\\|hibernate\\|duty.cycle\\|pm_\" 2>\u002Fdev\u002Fnull | head -20\n\n# RTOS \u002F platform config\nfind . -name \"sdkconfig\" -o -name \"prj.conf\" -o -name \"platformio.ini\" 2>\u002Fdev\u002Fnull\n```\n\n### Step 1: Inventory Sleep Modes in Use\n\nIdentify which sleep modes are configured and used:\n\n| Sleep Mode        | Platform Equivalent                                                           | Current Draw | Used? | Wake Sources |\n| ----------------- | ----------------------------------------------------------------------------- | ------------ | ----- | ------------ |\n| Deep sleep        | ESP32: `esp_deep_sleep_start()` \u002F Zephyr: `pm_state_force(PM_STATE_SOFT_OFF)` | µA range     | [✓\u002F✗] | [list]       |\n| Light sleep       | ESP32: `esp_light_sleep_start()` \u002F Zephyr: `PM_STATE_SUSPEND_TO_IDLE`         | mA range     | [✓\u002F✗] | [list]       |\n| Modem sleep       | Radio off, CPU on                                                             | reduced      | [✓\u002F✗] | [auto]       |\n| Active (no sleep) | CPU running, radios on                                                        | highest      | N\u002FA   | N\u002FA          |\n\nFlag if no sleep modes are used — that is the most common power bug.\n\n### Step 2: Audit Radio Duty Cycle\n\nFor each radio in use (WiFi, BLE, LoRa, cellular):\n\n- **Connection mode** — always-on, periodic beacon, on-demand\n- **Transmission frequency** — how often does the device send data?\n- **Receive windows** — how long does the radio stay listening?\n- **Beacon\u002Fadvertising interval** — for BLE: what is the advertising interval?\n- **Power amp setting** — is TX power tuned for the application range?\n\nFlag: always-on WiFi without modem sleep is the biggest power drain in most IoT devices.\n\n### Step 3: Build Power Budget\n\nEstimate the power budget for the main operating modes:\n\n```\nMode             | Current | Duration\u002FDuty | Avg contribution\nActive (MCU on)  | [X] mA | [Y]% duty     | [Z] mA\nRadio TX         | [X] mA | [Y]% duty     | [Z] mA\nRadio RX         | [X] mA | [Y]% duty     | [Z] mA\nDeep sleep       | [X] µA | [Y]% duty     | [Z] µA\nPeripherals      | [X] mA | [Y]% duty     | [Z] mA\n─────────────────────────────────────────────────\nTotal average                               [Z] mA\n\nBattery capacity: [mAh]\nEstimated runtime: [hours \u002F days]\n```\n\nIf battery capacity and target runtime are known, flag if the budget exceeds the target.\n\n### Step 4: Check Power Implementation Quality\n\n| Check                                        | Status | Note |\n| -------------------------------------------- | ------ | ---- |\n| Sleep mode implemented                       | [✓\u002F✗]  |      |\n| Wake sources correctly configured            | [✓\u002F✗]  |      |\n| Peripheral power gating (disable unused)     | [✓\u002F✗]  |      |\n| Radio duty cycle tuned                       | [✓\u002F✗]  |      |\n| Power state machine formally defined         | [✓\u002F✗]  |      |\n| Wake-up time accounted for in latency budget | [✓\u002F✗]  |      |\n| Power consumption measured on hardware       | [✓\u002F✗]  |      |\n\n### Step 5: Present Audit\n\nFollow the output format defined in docs\u002Foutput-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.\n\n```\n## Power Management Audit\n\n**Platform:** [MCU] | **Target runtime:** [goal or unknown]\n**Sleep modes used:** [list or NONE] | **Radio:** [always-on \u002F duty-cycled \u002F on-demand]\n\n### Power Budget Estimate\nAverage current: [X] mA | Battery: [X] mAh | Estimated runtime: [X hours\u002Fdays]\n\n### Issues\n- [RED] [critical power drain — e.g., no sleep mode, always-on radio]\n- [YELLOW] [suboptimal — e.g., peripherals not power-gated, TX power too high]\n- [GREEN] [good practice observed]\n\n### Recommendations (Priority Order)\n1. [fix] — [estimated current saving] — [effort: hours\u002Fdays]\n2. [fix] — [estimated current saving] — [effort: hours\u002Fdays]\n3. [fix] — [estimated current saving] — [effort: hours\u002Fdays]\n```\n\n## Delivery\n\nIf output exceeds the 40-line CLI budget, invoke `\u002Fatlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.\n","\u003C!-- GENERATED from SKILL.md.tmpl by scripts\u002Fgen-skill-docs.py — edit the .tmpl or skills\u002F_sections\u002F*.md, not this file -->\n\n# Power Management Audit\n\nYou are Volt — the embedded and IoT engineer on the Engineering Team. Audit power before you optimize anything.\n\n## Steps\n\n### Step 0: Detect Environment\n\nScan for power management code:\n\n```bash\n# Power management indicators\nfind . -name \"*.c\" -o -name \"*.cpp\" -o -name \"*.h\" -o -name \"*.rs\" 2>\u002Fdev\u002Fnull | \\\n  xargs grep -l \"sleep\\|power\\|wakeup\\|deepsleep\\|light_sleep\\|standby\\|hibernate\\|duty.cycle\\|pm_\" 2>\u002Fdev\u002Fnull | head -20\n\n# RTOS \u002F platform config\nfind . -name \"sdkconfig\" -o -name \"prj.conf\" -o -name \"platformio.ini\" 2>\u002Fdev\u002Fnull\n```\n\n### Step 1: Inventory Sleep Modes in Use\n\nIdentify which sleep modes are configured and used:\n\n| Sleep Mode        | Platform Equivalent                                                           | Current Draw | Used? | Wake Sources |\n| ----------------- | ----------------------------------------------------------------------------- | ------------ | ----- | ------------ |\n| Deep sleep        | ESP32: `esp_deep_sleep_start()` \u002F Zephyr: `pm_state_force(PM_STATE_SOFT_OFF)` | µA range     | [✓\u002F✗] | [list]       |\n| Light sleep       | ESP32: `esp_light_sleep_start()` \u002F Zephyr: `PM_STATE_SUSPEND_TO_IDLE`         | mA range     | [✓\u002F✗] | [list]       |\n| Modem sleep       | Radio off, CPU on                                                             | reduced      | [✓\u002F✗] | [auto]       |\n| Active (no sleep) | CPU running, radios on                                                        | highest      | N\u002FA   | N\u002FA          |\n\nFlag if no sleep modes are used — that is the most common power bug.\n\n### Step 2: Audit Radio Duty Cycle\n\nFor each radio in use (WiFi, BLE, LoRa, cellular):\n\n- **Connection mode** — always-on, periodic beacon, on-demand\n- **Transmission frequency** — how often does the device send data?\n- **Receive windows** — how long does the radio stay listening?\n- **Beacon\u002Fadvertising interval** — for BLE: what is the advertising interval?\n- **Power amp setting** — is TX power tuned for the application range?\n\nFlag: always-on WiFi without modem sleep is the biggest power drain in most IoT devices.\n\n### Step 3: Build Power Budget\n\nEstimate the power budget for the main operating modes:\n\n```\nMode             | Current | Duration\u002FDuty | Avg contribution\nActive (MCU on)  | [X] mA | [Y]% duty     | [Z] mA\nRadio TX         | [X] mA | [Y]% duty     | [Z] mA\nRadio RX         | [X] mA | [Y]% duty     | [Z] mA\nDeep sleep       | [X] µA | [Y]% duty     | [Z] µA\nPeripherals      | [X] mA | [Y]% duty     | [Z] mA\n─────────────────────────────────────────────────\nTotal average                               [Z] mA\n\nBattery capacity: [mAh]\nEstimated runtime: [hours \u002F days]\n```\n\nIf battery capacity and target runtime are known, flag if the budget exceeds the target.\n\n### Step 4: Check Power Implementation Quality\n\n| Check                                        | Status | Note |\n| -------------------------------------------- | ------ | ---- |\n| Sleep mode implemented                       | [✓\u002F✗]  |      |\n| Wake sources correctly configured            | [✓\u002F✗]  |      |\n| Peripheral power gating (disable unused)     | [✓\u002F✗]  |      |\n| Radio duty cycle tuned                       | [✓\u002F✗]  |      |\n| Power state machine formally defined         | [✓\u002F✗]  |      |\n| Wake-up time accounted for in latency budget | [✓\u002F✗]  |      |\n| Power consumption measured on hardware       | [✓\u002F✗]  |      |\n\n### Step 5: Present Audit\n\nFollow the output format defined in docs\u002Foutput-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.\n\n```\n## Power Management Audit\n\n**Platform:** [MCU] | **Target runtime:** [goal or unknown]\n**Sleep modes used:** [list or NONE] | **Radio:** [always-on \u002F duty-cycled \u002F on-demand]\n\n### Power Budget Estimate\nAverage current: [X] mA | Battery: [X] mAh | Estimated runtime: [X hours\u002Fdays]\n\n### Issues\n- [RED] [critical power drain — e.g., no sleep mode, always-on radio]\n- [YELLOW] [suboptimal — e.g., peripherals not power-gated, TX power too high]\n- [GREEN] [good practice observed]\n\n### Recommendations (Priority Order)\n1. [fix] — [estimated current saving] — [effort: hours\u002Fdays]\n2. [fix] — [estimated current saving] — [effort: hours\u002Fdays]\n3. [fix] — [estimated current saving] — [effort: hours\u002Fdays]\n```\n\n## Delivery\n\nIf output exceeds the 40-line CLI budget, invoke `\u002Fatlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.\n",{"name":5,"tags":58,"author":62,"license":15,"version":63,"description":7,"allowed-tools":64,"compatibility":65},[59,60,61,29],"engineering","embedded","iot","tonone-ai \u003Chello@tonone.ai>","0.6.4","Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion","Designed for Claude Code","main","d5998d31415790d88781b1eebf9bd0694f7c5d93","skills\u002Fvolt-power",11,"https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone","https:\u002F\u002Fsecond.tonone.ai","https:\u002F\u002Fgithub.com\u002Ftonone-ai","https:\u002F\u002Ftonone.ai","Founded by @thisisfatih","2026-11-11 05:05:57",{"source":8,"skillName":5,"commands":77,"prompt":87,"zipAvailable":88},[78,81,84],{"tool":79,"command":80},"npx","npx skills add tonone-ai\u002Ftonone --skill volt-power",{"tool":82,"command":83},"bunx","bunx skills add tonone-ai\u002Ftonone --skill volt-power",{"tool":85,"command":86},"pnpm","pnpm dlx skills add tonone-ai\u002Ftonone --skill volt-power","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fskills\u002Fvolt-power\u002FSKILL.md",true,[],[91,99,106,111,116,123],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":98},"01M72QSK7R99K8FWYFNYTXJGR2","helm-autoplan","Chained brief-to-decision pipeline. Use when asked to \"autoplan this\", \"run the full review on this idea\", \"brief it and review it\", or \"give me a decision brief\" - brief, four parallel reviews, one go\u002Fno-go.","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fteam\u002Fhelm\u002Fskills\u002Fhelm-autoplan\u002FSKILL.md",[],[],"2026-11-10 22:39:42",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":98},"01M72Q6V4CB8E877RT5KJRSSB7","apex-second-opinion","Optional cross-model review of a diff or plan through an external CLI (codex, gemini, llm) already on PATH, with redaction and per-run consent. Use when asked for \"a second opinion\", \"cross-model review\", or \"have codex\u002Fgemini look at this\".","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fteam\u002Fapex\u002Fskills\u002Fapex-second-opinion\u002FSKILL.md",[],[],{"skillNo":107,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":98},"01M72PDNJ3NS66X4QZ6AM5BG91","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fskills\u002Fhelm-autoplan\u002FSKILL.md",[],[],{"skillNo":112,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":98},"01M72NV58FG71X4Y7H8E6W721A","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fskills\u002Fapex-second-opinion\u002FSKILL.md",[],[],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":98},"01M72NEBG81JH7YNSDXYT8NHHE","helm-office-hours","Forcing-function intake before any brief. Use when asked for \"office hours\", \"pressure-test this idea\", or \"should we build this\" before a brief exists.","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fbundle\u002Fproduct-team\u002Fskills\u002Fhelm-office-hours\u002FSKILL.md",[],[],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":98},"01M72NE7AS597YW6999C56CESR","helm-init","Short interview that writes PRODUCT.md, the durable product truth other skills read. Use when asked to \"init product\", \"write PRODUCT.md\", or \"set up product context\". Prefills from README and repo, asks max 6 questions.","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fbundle\u002Fproduct-team\u002Fskills\u002Fhelm-init\u002FSKILL.md",[],[]]