المهارات wxpusher-integration
📦

wxpusher-integration

v1.0.5 مراجعة المحتوى r3 آمن 🌐 الوصول إلى الشبكة🔑 متغيرات البيئة📁 الوصول إلى نظام الملفات⚙️ الأوامر الخارجية

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.

يدعم: Claude Codex Code(CC)
Maintain this Skill? Claim it 🥉 79 برونزي

التثبيت باستخدام Agent لدي

انسخ هذا الطلب إلى Agent لديك. يتضمن صفحة Skill المعتمدة وملف manifest.

طلب الوكيل
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.

يجب أن يواصل Agent عرض خطته وطلب أي تأكيد تفرضه سياسة الأمان.

موارد مهيّأة لـ Agents

استخدم هذه الروابط عندما يحتاج AI Agent أو crawler أو script إلى سياق نظيف بدلًا من قراءة الصفحة كاملة.

اختبرها

جارٍ استخدام "wxpusher-integration". Add failure notifications to a Python task using my existing SPT configuration, without sending real messages.

النتيجة المتوقعة:

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

جارٍ استخدام "wxpusher-integration". WxPusher returns HTTP 200, but WeChat shows no notification. What should I check?

النتيجة المتوقعة:

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

التدقيق الأمني

آمن

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
الملفات التي تم فحصها
1,095
الأسطر التي تم تحليلها
0
عناصر المراجعة
0
تم تجاهل الإيجابيات الكاذبة
لم يكتشف أحدث تدقيق ثابت ودلالي مكتمل أي نتائج أمنية مؤكدة. ولا يثبت ذلك أن المهارة خالية من الآثار الجانبية.
شارك واستشهد بهذا التقرير

شارك تقرير التقييم المرتبط بالإصدار والشارة المحايدة وبطاقة التضمين والاستشهادات. تعرض Skillstore الأدلة من دون أن تقرر ما إذا كانت هذه المهارة آمنة.

فتح التقرير المرتبط بالإصدار
تقييم الأمان

نسخ رابط التقرير

https://skillstore.io/skills/hunxuankai-wxpusher-integration/audits/3?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 3) [Author version 1.0.5]. Skillstore. https://skillstore.io/skills/hunxuankai-wxpusher-integration/audits/3

اقتباس BibTeX

@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

سبب هذا التقييم موثوقية الأدلة: متوسط
45
الهندسة المعمارية
100
قابلية الصيانة
87
المحتوى
71
المجتمع
91
الامتثال للمواصفات

ما الذي يمكنك بناؤه

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.

جرّب هذه الموجّهات

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.

أفضل الممارسات

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

تجنب

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

الأسئلة المتكررة

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.

تفاصيل المطور

المؤلف

hunxuankai

الترخيص

MIT

إصدار المؤلف

v1.0.5

مراجعة Skillstore

r3

مرجع

de2a04c2b8769fc82e0b7593308c8db7f82ca4f6

حداثة الصيانة

١٢‏/١١‏/٢٠٢٦

الاستخدام

9 تنزيلات · 1 مشاهدات

بنية الملفات

المزيد من hunxuankai

عرض الكل
عرض الكل