技能 wxpusher-integration
📦

wxpusher-integration

v1.0.4 內容修訂 r2 安全 🌐 網路存取🔑 環境變數📁 檔案系統存取⚙️ 外部命令

Integrate WxPusher Notifications

Notification integrations can mishandle recipients, credentials, retries, and delivery results. This skill guides WxPusher implementation and troubleshooting using project conventions, documented API behavior, and mock tests.

支援: Claude Codex Code(CC)
Maintain this Skill? Claim it 🥉 78 銅級

使用我的智慧代理安裝

將此請求複製給你的智慧代理,其中包含權威 Skill 頁面和清單。

智能體請求
Review the Skillstore skill "wxpusher-integration" from https://skillstore.io/skills/hunxuankai-wxpusher-integration.md and its manifest at https://skillstore.io/api/skills/hunxuankai-wxpusher-integration/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

你的智慧代理仍應顯示其計畫,並依安全政策請求必要確認。

測試它

正在使用「wxpusher-integration」。 Add WxPusher failure notifications to a scheduled task without sending a live test.

預期結果:

  • Implementation scope: a small notification adapter and a task failure trigger.
  • Configuration: application token and recipient variables documented with placeholders.
  • Validation scope: mock success, business failure, timeout, and missing configuration cases.
  • Live push status: no real notification is sent during development validation.

正在使用「wxpusher-integration」。 Explain why an accepted WxPusher message may not appear in WeChat.

預期結果:

  • API acceptance creates a sending task; it does not confirm delivery or reading.
  • Inspect individual recipient results, then verify ClawBot binding, enablement, activation, and channel limits.
  • Do not resend repeatedly or switch recipients to bypass delivery restrictions.

安全審計

安全
v2 • 2026/10/18 開啟版本化報告

All 24 static findings are false positives involving documented endpoints, placeholder configuration, Markdown syntax, installation paths, and readable Chinese text. No evidence found of prompt injection, credential exfiltration, concealed execution, or unauthorized messaging. The skill requires scoped authorization for live pushes, prefers POST, and documents credential redaction and service limitations.

8
已掃描檔案
998
分析行數
0
複核項目
0
已忽略的誤報
最近一次完成的靜態與語意稽核未偵測到已確認的安全發現。這並不能證明該 Skill 沒有副作用。
審計單位: codex 檢視審計紀錄 →
分享與引用此報告

分享版本化評估報告、中性徽章、嵌入卡片與引用。Skillstore 只報告證據,不判斷該 Skill 是否安全。

開啟版本化報告
安全評估

複製報告連結

https://skillstore.io/skills/hunxuankai-wxpusher-integration/audits/2?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown 徽章

[![Skillstore security assessment](https://skillstore.io/badges/skills/hunxuankai-wxpusher-integration/security.svg)](https://skillstore.io/skills/hunxuankai-wxpusher-integration?utm_source=security_passport_badge)

HTML 徽章

<a href="https://skillstore.io/skills/hunxuankai-wxpusher-integration?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/hunxuankai-wxpusher-integration/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

嵌入卡片

<iframe src="https://skillstore.io/embed/skills/hunxuankai-wxpusher-integration.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
學術引用 (APA · BibTeX · CFF)

APA 引用

hunxuankai. (2026). wxpusher-integration security audit report (audit version 2) [Author version 1.0.4]. Skillstore. https://skillstore.io/skills/hunxuankai-wxpusher-integration/audits/2

BibTeX 引用

@techreport{hunxuankai-hunxuankai-wxpusher-integration-2026, author = {hunxuankai}, title = {wxpusher-integration security audit report (audit version 2)}, institution = {Skillstore}, year = {2026}, number = {2}, url = {https://skillstore.io/skills/hunxuankai-wxpusher-integration/audits/2}, note = {Author version 1.0.4} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "wxpusher-integration security audit report (audit version 2)" version: "1.0.4" type: report authors: - name: "hunxuankai" date-released: "2026-10-18" url: "https://skillstore.io/skills/hunxuankai-wxpusher-integration/audits/2" identifiers: - type: other value: "skillstore:hunxuankai-wxpusher-integration:audit:2" description: "Skillstore immutable audit report identifier"

Skillstore 評分

評分依據 證據置信度: 中
45
架構
100
可維護性
87
內容
65
社群
91
規範符合度

你可以打造什麼

Report scheduled task failures

Add WxPusher failure alerts to an existing script with minimal configuration, bounded retries, and mock validation.

Integrate backend event notifications

Extend an existing notification service with recipient routing, partial-failure handling, and duplicate prevention.

Diagnose deployment alert delivery

Review protected CI secrets, response codes, subscriber settings, and channel restrictions without automatically sending live messages.

試試這些提示

Understand WxPusher setup
I have selected WxPusher for a personal script. Explain standard POST versus SPT, required configuration, and recipient prerequisites without sending messages.
Add task notifications
Add WxPusher failure notifications to this Python task using existing project conventions. Use placeholder configuration and mock tests; do not send live messages.
Investigate missing WeChat notifications
WxPusher accepts my messages, but WeChat receives nothing. Review redacted responses, recipient results, ClawBot binding, activation, and limits without live pushes.
Design resilient queue delivery
Integrate WxPusher into our existing queue worker with per-target validation, bounded retries, deduplication, redacted logs, and mock failure tests. Preserve primary business outcomes.

最佳實務

  • Reuse project configuration, HTTP clients, and notification interfaces; keep credentials in approved secret storage.
  • Prefer JSON POST, redact logs, and check both top-level and individual recipient business results.
  • Validate with mocks first; send live messages only within explicit authorization for recipients, purpose, and frequency.

避免

  • Treating HTTP 200 or task creation as proof that every recipient received or read the notification.
  • Committing credentials, logging full authenticated URLs, or copying personal data into notification bodies.
  • Retrying indefinitely, defaulting to broadcast when recipients are missing, or assuming an SPT can be revoked by rescanning.

常見問題

Can I use this skill with Claude, Codex, and Claude Code?
Yes. The core workflow is documentation-based and uses available project tools rather than a required host-specific integration.
Does the skill include a ready-to-run notification client?
No. It provides instructions and references for implementing WxPusher through your existing language, HTTP client, configuration, and testing tools.
What configuration do standard pushes require?
Standard pushes require an appToken, message content, and UID or Topic targets. SPT uses a separate token-based mode.
Will development tests send real notifications?
No, not by default. Development uses mocks; live pushes require explicit authorization covering the intended recipients, purpose, and frequency.
Can WxPusher send to any WeChat friend or group?
No. The documented ClawBot channel requires user binding and activation, supports text notifications, and has channel-specific limits.
How should I handle a leaked SPT?
Stop sharing it and clean controlled copies. Public references do not verify revocation; contact WxPusher and do not assume rescanning invalidates it.

開發者詳細資訊

作者

hunxuankai

授權

MIT

作者版本

v1.0.4

Skillstore 修訂

r2

引用

87cebd6f2460da36107e4bd50cab89d51c0b33db

維護新鮮度

2026/10/18

使用量

2 次下載 · 1 次瀏覽

查看全部