[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M799C1MYYRKVBZK42Y1WK3W4":3,"skill-same:01M799C1MYYRKVBZK42Y1WK3W4":45},{"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":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M799C1MYYRKVBZK42Y1WK3W4","pushover-cli",null,"Use when a user explicitly requests sending a Pushover notification in the current task.","jurgenj136\u002Fpushover-cli","jurgenj136","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F28291210?v=4","01M799BXT926SBDH6H737TE580","Jurgen","01M799BXTV7FMBY6MB1DY8TFFP",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjurgenj136\u002Fpushover-cli\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fpushover-cli\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: pushover-cli\ndescription: Use when a user explicitly requests sending a Pushover notification in the current task.\n---\n\n# Pushover CLI\n\nSkill version: 0.1.0\nMinimum CLI version: 0.1.0\n\nRequire an existing binary: run `command -v pushover`. Then run `pushover --json version`. Compare the installed CLI version against the minimum version `0.1.0`; stop and tell the user to upgrade if it is incompatible. For redacted diagnostics, run `pushover --json auth status`. Always invoke `pushover` with `--json`.\n\n## Authority\n\n- Send only when the current task explicitly asks to send a Pushover notification.\n- Require the user to explicitly name every recipient alias for this send. Use configured profile names and aliases. Do not handle raw credentials. Never ask for, accept, or expose raw keys.\n- If the user explicitly names a configured profile, pass `--profile`; otherwise omit `--profile` and use the configured default. Never guess another profile.\n- Do not infer priority `1` or `2` from urgency, tone, or content. Require explicit current-task intent for elevated priority, an attachment, and encryption. An attachment is allowed only when an attachment is explicitly requested in the current task; encryption is allowed only when encryption is explicitly requested in the current task.\n- Refuse configuration requests, even when asked. Do not run `pushover setup`. Do not run `pushover profiles add`, `pushover profiles use`, or `pushover profiles remove`. Do not run `pushover recipients add` or `pushover recipients remove`. Do not run `pushover auth backend set`.\n- Use `--dry-run` when message content or target intent is unresolved. A dry-run never grants permission to send.\n\n## Send\n\nUse the current CLI grammar, for example:\n\n```sh\npushover --json send --to \u003Crecipient-alias> \"\u003Cmessage>\"\n```\n\nAdd `--priority 1` or `--priority 2` only with that explicit intent. Priority `2` requires explicit retry and expiry values and `--yes`, because agents are always non-interactive. Add only explicitly requested `--attachment \u003Cpath>` or `--attachment-url \u003Chttps-url>`, and add `--encrypted` only with explicit encryption intent. `--encrypted` is mutually exclusive with `--attachment`, `--attachment-url`, `--html`, and `--monospace`.\n\nReport ordered per-target outcomes. Do not retry after any failed or ambiguous result. Preserve ambiguity as unknown; send again only after the user sees that result and makes a new explicit request in the current task.\n\nThese instructions are advisory: they cannot prevent a misbehaving or prompt-injected agent. Recommend configuring the agent harness to require approval for `pushover send`.\n","# Pushover CLI\n\nSkill version: 0.1.0\nMinimum CLI version: 0.1.0\n\nRequire an existing binary: run `command -v pushover`. Then run `pushover --json version`. Compare the installed CLI version against the minimum version `0.1.0`; stop and tell the user to upgrade if it is incompatible. For redacted diagnostics, run `pushover --json auth status`. Always invoke `pushover` with `--json`.\n\n## Authority\n\n- Send only when the current task explicitly asks to send a Pushover notification.\n- Require the user to explicitly name every recipient alias for this send. Use configured profile names and aliases. Do not handle raw credentials. Never ask for, accept, or expose raw keys.\n- If the user explicitly names a configured profile, pass `--profile`; otherwise omit `--profile` and use the configured default. Never guess another profile.\n- Do not infer priority `1` or `2` from urgency, tone, or content. Require explicit current-task intent for elevated priority, an attachment, and encryption. An attachment is allowed only when an attachment is explicitly requested in the current task; encryption is allowed only when encryption is explicitly requested in the current task.\n- Refuse configuration requests, even when asked. Do not run `pushover setup`. Do not run `pushover profiles add`, `pushover profiles use`, or `pushover profiles remove`. Do not run `pushover recipients add` or `pushover recipients remove`. Do not run `pushover auth backend set`.\n- Use `--dry-run` when message content or target intent is unresolved. A dry-run never grants permission to send.\n\n## Send\n\nUse the current CLI grammar, for example:\n\n```sh\npushover --json send --to \u003Crecipient-alias> \"\u003Cmessage>\"\n```\n\nAdd `--priority 1` or `--priority 2` only with that explicit intent. Priority `2` requires explicit retry and expiry values and `--yes`, because agents are always non-interactive. Add only explicitly requested `--attachment \u003Cpath>` or `--attachment-url \u003Chttps-url>`, and add `--encrypted` only with explicit encryption intent. `--encrypted` is mutually exclusive with `--attachment`, `--attachment-url`, `--html`, and `--monospace`.\n\nReport ordered per-target outcomes. Do not retry after any failed or ambiguous result. Preserve ambiguity as unknown; send again only after the user sees that result and makes a new explicit request in the current task.\n\nThese instructions are advisory: they cannot prevent a misbehaving or prompt-injected agent. Recommend configuring the agent harness to require approval for `pushover send`.\n",{"name":5,"description":7},"main","8a2ec417d9e462683c35240e28b39c36d385864a",".claude\u002Fskills\u002Fpushover-cli","https:\u002F\u002Fgithub.com\u002Fjurgenj136\u002Fpushover-cli","https:\u002F\u002Fgithub.com\u002Fjurgenj136","Developer @zenjoy. Side projects: home automation and local-first integrations.","2026-10-15 18:53:43",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add jurgenj136\u002Fpushover-cli --skill pushover-cli",{"tool":37,"command":38},"bunx","bunx skills add jurgenj136\u002Fpushover-cli --skill pushover-cli",{"tool":40,"command":41},"pnpm","pnpm dlx skills add jurgenj136\u002Fpushover-cli --skill pushover-cli","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjurgenj136\u002Fpushover-cli\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fpushover-cli\u002FSKILL.md",true,[],[]]