← ClaudeAtlas

awewarmlisted

Use when helping users manage awewarm warm-up schedules — checking status, changing fixed times, switching fixed/interval modes, verifying plan windows, or installing the background scheduler. 中文触发词:保温、保活、订阅窗口、warm-up、awewarm、固定时间、调度模式、5小时窗口。
wehuman01/awewarm · ★ 7 · AI & Automation · score 70
Install: claude install-skill wehuman01/awewarm
# awewarm This skill covers **managing** awewarm's warm-up schedules: status, fixed times, modes, window verification, and the scheduler install. ## Quota Rules (read this first) Every activation sends one REAL request against the user's coding-plan quota: - **Never run** `awewarm run` or `awewarm run <id>` unless the user explicitly asks for a request to be sent. They prompt for confirmation by default; `--force` skips the prompt (for scripting). - `awewarm tick` is the background scheduler's own command (hidden). It is not for interactive use. - `awewarm init` and `awewarm config add` are interactive (they prompt for choices and API keys, and send one test request per added connection). The user runs them in their own terminal. ## Command Safety | Category | Commands | |---|---| | Read-only — run freely | `awewarm status [<id>] [--remote|--local] [--json]`, `awewarm discover`, `awewarm config set <id>` (no flags = show settings), `awewarm config path`, `awewarm self-update --check` | | Local changes — run on request | `awewarm config set <id> --times/--days/--mode/--on/--off/--anchor/--next/--move-slot/--window/--wake/--no-wake/--inherit-schedule`, `awewarm config proxy [<url>|none]` (egress proxy for awewarm's own requests and the CLI subprocesses it starts), `awewarm config remove <id>` (confirm first — deletes the stored API key), `awewarm remote push [<id>]`, `awewarm scheduler install [--wake]`, `awewarm scheduler uninstall`, `awewarm self-update` | | Delegation