사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/terrylica/cc-skills --skill emergency-priority2-receipt시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
emergency-priority2-receipt
Self-Evolving Skill: This skill improves through use. If instructions are wrong, parameters drifted, or a workaround was needed — fix this file immediately, don't defer. Only update for real, reproducible issues.
Priority-2 emergency notification with receipt polling, via the TS core pushover_core.ts emergency.
env -u HTTPS_PROXY -u HTTP_PROXY bun "$(cc-plugin-root pushover-commander)/skills/_lib/pushover_core.ts" emergency \
--title "Title" --message "what happened + the one action needed" \
[--retry 30] [--expire 300] [--sound piano] [--attach report.png] [--app main|test] [--no-wait]Behavior (verified on a physical device 2026-05-30)
- priority 2 requires
retry(≥ 30 s) andexpire(≤ 10800 s) — Pushover returns HTTP 400 without them. The core supplies defaults (30 / 300) automatically. - The response returns a
receipt; the core polls/1/receipts/{receipt}.jsonevery 5 s and prints{acknowledged, acknowledged_at, expired}when you ack (verified ack at t+35 s) or it expires. --no-waitskips the receipt poll: the core prints{status, request, receipt}and exits 0 as soon as Pushover accepted the message. Use it whenever the caller runs the core under a timeout shorter than--expire(web-forge's login gate does): otherwise the timeout kills the poll and an alert that was delivered looks like a failure.sound=pianois a custom sound on this account;pianobaris the built-in fallback — usecustom-sounds resolve piano pianobar.- Attach a
render-incident-report-imagePNG for full detail; keep--message≤ 1024.
Post-Execution Reflection
After this skill completes, check before closing:
- Did the priority-2 alert repeat until acknowledged? If it stopped early or never fired, fix the retry/expire handling.
- Did the receipt poll detect the ack or expiry? If polling hung or missed the ack, fix the poll loop.
Only update if the issue is real and reproducible — not speculative.

