技能详情（站内镜像，无评论）
许可证：MIT-0
MIT-0 ·免费使用、修改和重新分发。无需归因。
版本：v0.1.0
统计：⭐ 0 · 21 · 0 current installs · 0 all-time installs
⭐ 0
安装量（当前） 0
🛡 VirusTotal ：良性 · OpenClaw ：良性
Package：armysheng/ticket-signal-watch
安全扫描（ClawHub）
- VirusTotal ：良性
- OpenClaw ：良性
OpenClaw 评估
The skill's code, instructions, and requirements are consistent with a ticket-monitoring notifier: it only needs python3, reads a targets config, fetches target URLs, keeps a local state file, and emits structured alerts.
目的
Name/description match the included files: the script fetches pages, looks for ticket-related keywords, tracks state, and emits structured results. Requiring python3 and providing example configs is proportionate.
说明范围
SKILL.md and the script stay within the stated purpose. The script fetches arbitrary URLs listed in the targets config and writes a state JSON. That behavior is expected, but be aware it will make outbound requests to any URL you place in targets (including internal endpoints if run in a networked/cloud environment). The script does not read other system files or environment variables.
安装机制
This is an instruction-only skill with no install steps; no external packages or downloads are performed. Lowest-risk install footprint.
证书
The skill declares no required credentials or env vars. Example notifier config shows webhook URLs and Authorization headers — those are user-provided values you may store in config files. Storing secrets in plain JSON files has usual operational risks; the skill itself does not require or exfiltrate credentials.
持久
always is false and the script only writes its own state JSON (and would write to any file path you configure). It does not modify other skills or system settings.
综合结论
This skill appears coherent for monitoring ticket pages. Before running: inspect and control the targets.json you feed it (don't include internal-only URLs if running in a shared/cloud agent), ensure the state and notifier paths are writable and stored where you want data retained, and avoid placing secret tokens in plain text files unless you accept that risk. Note the example notifier shows webhook headers but the script does not automatical…
安装（复制给龙虾 AI）
将下方整段复制到龙虾中文库对话中，由龙虾按 SKILL.md 完成安装。
请把本段交给龙虾中文库（龙虾 AI）执行：为本机安装 OpenClaw 技能「Ticket Signal Watch」。简介：Monitor ticket pages or backend ticket data for sale, restock, presale, or stat…。
请 fetch 以下地址读取 SKILL.md 并按文档完成安装：https://raw.githubusercontent.com/openclaw/skills/refs/heads/main/skills/armysheng/ticket-signal-watch/SKILL.md
（来源：yingzhi8.cn 技能库）SKILL.md
---
name: ticket-signal-watch
description: Monitor ticket pages or backend ticket data for sale, restock, presale, or status-change signals; emit structured alerts that can be pushed to OpenClaw channels, webhooks, or other notification backends. Use when users want reliable ticket notifications rather than automated checkout.
metadata: {"openclaw":{"requires":{"bins":["python3"]},"emoji":"🎫"}}
---
# Ticket Signal Watch
This skill is for reliable ticket notifications, not automated checkout.
Use it when:
- a user wants to monitor ticket sale or restock signals
- a backend already has ticket data and needs a push-ready event format
- you want OpenClaw to check official pages, search pages, or other text sources for ticket signals
## Files
- Skill root: `{baseDir}`
- Script: `{baseDir}/scripts/watch_ticket_pages.py`
- Target example: `{baseDir}/config/targets.example.json`
- Notifier example: `{baseDir}/config/notifiers.example.json`
- Default state path: `{baseDir}/state/state.json`
## Operating model
Treat the workflow as three layers:
1. `collector`
- fetch page text or consume backend data
2. `signal engine`
- decide whether the change is meaningful
3. `notifier`
- push the resulting event to OpenClaw channels, webhooks, or another downstream system
The ideal production setup is:
- use backend data if available
- fall back to page checks only when needed
- keep collection and notification decoupled
## Recommended usage
Run the script with a target config and a writable state file:
```bash
python3 "{baseDir}/scripts/watch_ticket_pages.py"
--config "{baseDir}/config/targets.example.json"
--state "{baseDir}/state/state.json"
--json
```
If `alerts` is empty, do not send a notification.
If `alerts` is non-empty, forward the structured result to:
- an OpenClaw channel
- a webhook
- a file/queue processor
## Output expectations
The script should produce:
- `results`: per-target check results
- `alerts`: only meaningful changes worth notifying
- `summary`: short human-readable summary
Each alert should contain enough information to route downstream:
- `name`
- `platform`
- `url`
- `signal_hits`
- `signal_level`
- `alert_reasons`
## Configuration guidance
Prefer official detail pages over generic search pages.
Use:
- `require_all` for identity words that must be present
- `match_any` for actionable signal words
- `signal_keywords.high` for the strongest signals
Examples of strong signals:
- `立即购买`
- `立即预订`
- `可选座`
- `有票`
- `开售`
- `预售中`
- `补票`
- `回流`
- `加场`
## Guardrails
- Do not treat generic page changes as sale signals.
- Search pages are weaker than detail pages.
- Add cooldown, dedupe, and jitter before high-frequency polling.
- If a platform starts returning anti-bot pages or challenge pages, mark that explicitly instead of claiming success.
- This skill is for notification workflows; do not imply that it can safely complete checkout automatically.