Skills wxpusher-integration
📦

wxpusher-integration

v1.0.5 Content revision r3 Safe 🌐 Network access🔑 Env variables📁 Filesystem access⚙️ External commands

Integrate WxPusher Notifications

Notification integrations can fail through incorrect routing, exposed credentials, or incomplete response checks. This skill guides WxPusher integration with protected configuration, explicit failure handling, and mocked tests.

Supports: Claude Codex Code(CC)
Maintain this Skill? Claim it 🥉 79 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
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.

Your Agent should still show its plan and request any confirmation required by the security policy.

Test it

Using "wxpusher-integration". Add failure notifications to a Python task using my existing SPT configuration, without sending real messages.

Expected outcome:

  • Proposed integration: use the existing SPT environment variable and the JSON POST simple-push endpoint.
  • Failure policy: isolate notification errors and apply bounded retries only to transient failures.
  • Validation plan: mock successful responses, business failures, missing configuration, and timeouts.
  • Live-send status: no real message is required for this development workflow.

Using "wxpusher-integration". WxPusher returns HTTP 200, but WeChat shows no notification. What should I check?

Expected outcome:

  • Check the top-level and per-target business codes before treating the request as accepted.
  • If accepted, check the intended recipient and ClawBot binding, enablement, activation, and channel allowance.
  • Do not use discontinued status-query responses as a reason to resend.
  • An accepted request does not confirm that the user received or read the notification.

Security Audit

Safe
v3 • 11/12/2026 Open versioned report

All 30 static findings are false positives: documented service endpoints, placeholders, protective configuration guidance, Markdown formatting, and readable Chinese text. No evidence found of prompt injection, credential exfiltration, concealed execution, or unauthorized messaging. Intended integrations still require protected credentials, redacted URLs, and authorization for real sends.

8
Files scanned
1,095
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

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

Markdown badge

[![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 badge

<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>

Embed card

<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>
Academic citations (APA · BibTeX · CFF)

APA citation

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

BibTeX citation

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

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 3)" version: "1.0.5" type: report authors: - name: "hunxuankai" date-released: "2026-11-12" url: "https://skillstore.io/skills/hunxuankai-wxpusher-integration/audits/3" identifiers: - type: other value: "skillstore:hunxuankai-wxpusher-integration:audit:3" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium
45
Architecture
100
Maintainability
87
Content
71
Community
91
Spec Compliance

What You Can Build

Notify on scheduled task failures

Connect a personal script to an existing SPT configuration with protected secrets, timeouts, and mocked failure tests.

Add backend event notifications

Build a WxPusher adapter behind an existing notification interface with UID or Topic routing and explicit failure isolation.

Report deployment outcomes

Add a controlled CI/CD notification step using protected environment secrets and a clear policy for notification failures.

Try These Prompts

Understand WxPusher options
Explain UID, Topic, and SPT notifications in WxPusher. Compare their configuration needs and WeChat receiving limits. Do not send messages.
Integrate a personal script
Add WxPusher failure notifications to my Python task using its existing SPT environment variable. Use JSON POST, bounded retries, and mocked tests only.
Diagnose missing notifications
Investigate WxPusher requests that return HTTP 200 without visible notifications. Check redacted business results, recipient configuration, and ClawBot activation. Do not send test messages.
Build a resilient adapter
Integrate WxPusher behind our notification gateway. Reuse project configuration, isolate failures, validate per-target results, and test retries, deduplication, limits, and redaction with mocks.

Best Practices

  • Reuse project secret storage and HTTP clients; keep credentials, recipient data, and sensitive content out of logs.
  • Default to mocked tests and perform real sends only within explicit authorization for purpose, recipients, and frequency.
  • Validate business results and content limits; use bounded retries and deduplication where repeated notifications would cause harm.

Avoid

  • Treating HTTP 200 or a created sending task as proof that a user received or read a notification.
  • Committing tokens, logging authenticated URLs, or copying full request bodies into notification messages.
  • Retrying authentication failures indefinitely, bypassing channel limits, or changing recipients without authorization.

Frequently Asked Questions

When should I use this skill?
Use it when WxPusher is explicitly requested or already selected. A generic request for WeChat notifications does not select WxPusher automatically.
Does this skill include a ready-made client?
No. It provides workflow instructions and reference documentation for integration through your project's existing tools and libraries.
Can development proceed without real credentials?
Yes. Use named environment variables, placeholders, and mocked HTTP responses. Real notifications require configured credentials, recipients, and authorization.
Can it send to any WeChat friend or group?
No. The references describe notifications to configured recipients through supported channels. WeChat ClawBot requires binding and activation and has channel limits.
How does SPT differ from standard notifications?
SPT uses a separate push token instead of appToken with UID or Topic routing. The skill defaults to JSON POST for SPT.
Can a leaked SPT be reset like an appToken?
The references do not verify a public SPT reset or revocation method. Stop spreading the token and contact WxPusher for confirmed recovery options.

Developer Details

Author

hunxuankai

License

MIT

Author version

v1.0.5

Skillstore revision

r3

Ref

de2a04c2b8769fc82e0b7593308c8db7f82ca4f6

Maintenance freshness

11/12/2026

Usage

9 downloads · 1 views

More from hunxuankai

View all
View all