# Integrate WxPusher Notifications

Notification integrations can expose secrets, mishandle delivery results, or disrupt primary workflows. This skill guides WxPusher implementation with secure configuration, explicit routing, bounded retries, and mock tests.

## Install

```bash
npx skillstore add hunxuankai/wxpusher-integration
```

## Metadata

- Status: approved
- Slug: hunxuankai-wxpusher-integration
- Version: 1.0.3
- Author version: 1.0.3
- Skillstore revision: r1
- Version status: valid
- Tree hash: 895ebade60a27052adb6dcdb9ac61855c0addfd2e0a39afa15408c1bb6ea2229
- Author: hunxuankai
- GitHub username: hunxuankai
- License: MIT
- Repository: https://github.com/hunxuankai/wxpusher-integration/tree/62d3591b9db27a757aa5c3ed9203944b169326c4/skills/wxpusher-integration
- Ref: e406bf64b5db6e514879399e87b346fa7ff7c2fb
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: network, env\_access, filesystem, external\_commands
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/hunxuankai-wxpusher-integration
- Manifest: https://skillstore.pages.dev/api/skills/hunxuankai-wxpusher-integration/manifest

## Capabilities

- Guide standard POST and SPT integrations using existing project HTTP clients and notification boundaries.
- Define UID, Topic, and SPT routing with configuration validation and recipient limits.
- Specify top-level and per-target business-response checks, including partial failures.
- Plan timeouts, bounded retries, deduplication, and notification failure isolation.
- Design mock tests for configuration errors, response failures, rate limits, and content size limits.
- Provide troubleshooting, credential-handling, callback, and API maintenance guidance.

## Use Cases

- Add Backend Event Notifications: Connect application events to a WxPusher adapter while protecting secrets and keeping notification failures separate from primary operations.
- Report Deployment and Monitoring Results: Add controlled CI/CD or monitoring notifications with protected credentials, bounded retries, and explicit failure policies.
- Notify Personal Script Completion: Use an SPT POST integration for personal task results, with placeholder configuration and mock verification before authorized live sends.

## Prompt Templates

### Plan a First Integration

```
Inspect this project and plan a WxPusher task-completion notification. Use placeholder configuration and identify the smallest implementation and mock test changes.
```

### Implement Standard Notifications

```
Add WxPusher standard POST notifications through our existing HTTP client. Validate UID configuration, check target results, and add mock tests without live sends.
```

### Diagnose Partial Failures

```
Investigate these redacted WxPusher responses. Explain partial failures, inspect retry behavior, and add regression tests without exposing secrets or sending live messages.
```

### Design Reliable Queue Delivery

```
Integrate WxPusher into our event queue with deduplication, bounded retries, protected secrets, explicit failure handling, and mock tests. Preserve existing business semantics.
```

## Limitations

- Provides documentation and implementation guidance, not a bundled executable client or notification service.
- Live notifications require valid credentials, configured recipients, network access, and explicit authorization.
- API acceptance does not guarantee delivery or reading; quotas and client behavior can change.
- The references identify no verified public SPT revocation method or Topic CRUD API.

## Best Practices

- Prefer JSON POST, approved secret storage, minimal message content, and redacted logs.
- Use mock HTTP tests by default and keep live sends within explicitly authorized recipients, purposes, and frequencies.
- Validate every target result and enforce timeouts, bounded retries, and deduplication where repeated sends matter.

## Anti Patterns

- Commit tokens, recipient details, or real notification bodies in examples, fixtures, logs, or screenshots.
- Treat HTTP 200 or task acceptance as proof that every recipient received or read the notification.
- Send unauthorized test messages, retry indefinitely, or silently broadcast when recipient configuration is missing.

## Security Audit

- Audited at: 2026-10-06T18:01:12.155\+00:00
- Summary: All 24 static findings are false positives in context: documented endpoints, placeholder configuration, installation metadata, Markdown backticks, and readable bilingual text. No evidence found of prompt injection, unauthorized credential collection, or concealed execution. The documentation requires authorized live sends, secret protection, URL redaction, and mock development tests.

## Stats

- Views: 0
- Downloads: 1
- Favorites: 1
- Popularity score: 0