Habilidades wxpusher-integration

📦

wxpusher-integration

Name: wxpusher-integration
Author: hunxuankai

v1.0.4 Revisión del contenido r2 Seguro 🌐 Acceso a red🔑 Variables de entorno📁 Acceso al sistema de archivos⚙️ Comandos externos

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.

Compatible con: Claude Codex Code(CC)

🥉 78 Bronce

Maintain this Skill? Claim it 🥉 78 Bronce

Instalar con mi Agente

Copia esta solicitud en tu Agente. Incluye la página canónica del Skill y el manifiesto.

Solicitud de agente

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.

Tu Agente debe seguir mostrando su plan y solicitar cualquier confirmación exigida por la política de seguridad.

Recursos legibles por agentes

Usa estos enlaces cuando un agente de IA, crawler o script necesite contexto limpio en vez de leer la página completa.

Detalle Markdown GET /skills/hunxuankai-wxpusher-integration.md Manifest firmado GET /api/skills/hunxuankai-wxpusher-integration/manifest Lockfile firmado GET /api/skills/hunxuankai-wxpusher-integration/lockfile

Pruébalo

Usando "wxpusher-integration". Add WxPusher failure notifications to a scheduled task without sending a live test.

Resultado esperado:

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.

Usando "wxpusher-integration". Explain why an accepted WxPusher message may not appear in WeChat.

Resultado esperado:

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.

Auditoría de seguridad

Seguro

v2 • 18/10/2026 Abrir el informe versionado

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.

Archivos escaneados

998

Líneas analizadas

Elementos de revisión

Falsos positivos ignorados

Factores de riesgo

🌐 Acceso a red (10)

references/api.md:48 references/api.md:66 references/api.md:130 references/api.md:139 references/api.md:153 references/api.md:177 references/api.md:198 references/api.md:222 references/api.md:244 references/api.md:251

🔑 Variables de entorno (1)

references/configuration.md:34

📁 Acceso al sistema de archivos (1)

references/maintenance.md:77

⚙️ Comandos externos (2)

SKILL.md:52 SKILL.md:81

La auditoría estática y semántica completada más reciente no detectó hallazgos de seguridad confirmados. Esto no demuestra que el skill no tenga efectos secundarios.

Auditado por: codex Ver historial de auditorías →

Compartir y citar este informe

Comparte el informe de evaluación versionado, la insignia neutral, la tarjeta insertable y las citas. Skillstore presenta evidencias sin decidir si este Skill es seguro.

Abrir el informe versionado

Copiar enlace del informe

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

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

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

Tarjeta para insertar

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

Citas académicas (APA · BibTeX · CFF)

Cita 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

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

Puntuación de Skillstore

Por qué esta puntuación Confianza de la evidencia: Medio

Arquitectura

100

Mantenibilidad

Contenido

Comunidad

Cumplimiento de la especificación

Lo que puedes crear

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.

Prueba estos prompts

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.

Mejores prácticas

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.

Evitar

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.

Preguntas frecuentes

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.