← Back to Skills Marketplace
Ticket Monitor Ichinosuke
by
Kazuma Mukai
· GitHub ↗
· v1.0.4
875
Downloads
0
Stars
1
Active Installs
5
Versions
Install in OpenClaw
/install ticket-monitor-ichinosuke
Description
Monitors 春風亭一之輔's official site for new Tokyo performance tickets and sends notifications to a specified Discord webhook.
Usage Guidance
What to check before installing:
- Metadata mismatch: the registry metadata declared no required env vars but SKILL.md and the script require DISCORD_WEBHOOK_URL — confirm this and update metadata before installing.
- Do NOT put your Discord webhook secret into a global OpenClaw .env unless you accept that other skills/processes could access it. Prefer storing the webhook in a skill-specific .env mounted only into the skill folder, use a secrets manager, or pass it at runtime if the platform supports per-skill secrets.
- Review scripts/install.sh: it runs pip install and attempts --break-system-packages first. If you're running in a production container, prefer installing dependencies into a virtualenv, image build step, or Dockerfile to avoid changing host/system packages.
- Verify the webhook channel permissions: create a dedicated webhook with minimal permissions and a dedicated channel for notifications to limit impact if the webhook leaks.
- Confirm the scraper behavior is acceptable (rate limits, robots.txt, target URLs) and that the skill will not run at a frequency that could trigger rate limits or blocking.
- Inspect and control file write location: the script writes data/seen_tickets.json under the skill directory. Ensure directory permissions are appropriate and the data directory is not world-readable if that matters.
- If you need lower blast radius, consider running this skill in an isolated container where the webhook env is supplied only to that container, or modify the skill to accept the webhook as an explicit argument rather than requiring global env changes.
Given these points, the package appears to implement the stated functionality, but the deployment guidance increases secret exposure and the metadata inconsistency should be resolved — treat the package as suspicious until you confirm safe deployment practices.
Capability Analysis
Type: OpenClaw Skill
Name: ticket-monitor-ichinosuke
Version: 1.0.4
The skill 'ticket-monitor-ichinosuke' is designed to scrape a specific website for ticket information, filter for Tokyo events, and send notifications to a user-provided Discord webhook. All observed actions, including web scraping (`scripts/ticket_monitor.py`), local file storage (`data/seen_tickets.json`), and Discord communication, align with its stated purpose. The `SKILL.md` instructions are clear and do not contain any prompt injection attempts with malicious intent. The `scripts/install.sh` uses standard `pip install` commands without downloading or executing remote payloads. There is no evidence of data exfiltration to unauthorized endpoints, backdoor installation, or other malicious activities.
Capability Assessment
Purpose & Capability
Name/description (monitor Ichinosuke site and notify Discord) align with the included Python scraper and a notify_discord function. However, registry metadata at the top of the package claimed 'Required env vars: none' while the SKILL.md frontmatter and the script require DISCORD_WEBHOOK_URL — a clear metadata mismatch that should be fixed.
Instruction Scope
SKILL.md instructs operators to edit OpenClaw's top-level docker-compose .env (global OpenClaw config) to add DISCORD_WEBHOOK_URL and restart containers. That expands the secret's scope to the entire OpenClaw process (all skills) rather than keeping it limited to this skill or a skill-specific config. Aside from that, the runtime instructions and script only perform scraping of the target site and POSTs to the provided Discord webhook; they do not read unrelated credentials or system secrets.
Install Mechanism
There is no remote code download — the package is instruction+script based and includes scripts/install.sh which runs pip install requests beautifulsoup4 python-dotenv. The install script uses the flag --break-system-packages as the first pip argument (then falls back), which on some systems (Debian/Ubuntu with system Python packaged) can be risky or indicate it will alter system-managed packages. This is not unusual for a Python script but worth noting.
Credentials
Only one secret is used (DISCORD_WEBHOOK_URL), which is proportional to the function. However the package documentation explicitly tells operators to place that webhook into the global OpenClaw .env, which increases exposure: the webhook becomes readable/usable by other skills and processes that read that environment. Also the top-level registry metadata omitted this required env var, creating confusion.
Persistence & Privilege
The skill does not set always:true and only writes a local seen_tickets.json under the skill's data directory, which is appropriate. The concern is the recommended deployment step to modify OpenClaw's global .env — that effectively grants the skill's webhook value broader presence across the agent runtime and increases blast radius if the secret is compromised. The skill does not modify other skills or system-wide agent settings itself, but the installation guidance asks the operator to do so.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install ticket-monitor-ichinosuke - After installation, invoke the skill by name or use
/ticket-monitor-ichinosuke - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.4
Version 1.0.5
- Updated installation and environment variable setup instructions for VPS/Docker environments in the documentation.
- Improved clarity of the configuration steps for adding the Discord Webhook URL and restarting the container.
- No functional changes to the code; documentation update only.
v1.0.3
- Updated skill to version 1.0.4.
- Changed setup to require DISCORD_WEBHOOK_URL as an environment variable, instead of saving via config file.
- SKILL.md improved: added a clear note about using .env for webhook configuration; removed instructions about saving config in JSON.
- Minor updates to metadata formatting and content for clarity.
v1.0.2
- Setup process improved: Discord Webhook URL is now saved permanently in data/config.json instead of needing environment variable export.
- Instructions updated: Simply tell the bot your Webhook URL via chat for easy setup.
- YAML metadata adjusted to reflect new configuration handling and updated description.
- No core monitoring or notification logic changes; usage remains the same.
v1.0.1
- Add version field (1.0.1) to SKILL.md metadata section.
- No functional or behavioral changes. Documentation/metadata update only.
v1.0.0
Initial release of ticket-monitor-ichinosuke:
- Monitors 春風亭一之輔's official website for new Tokyo event tickets.
- Notifies a designated Discord channel via Webhook when new events are detected.
- Detects and only notifies about events not previously reported.
- Requires Python 3 and the packages: requests, beautifulsoup4, python-dotenv.
- Saves seen ticket info locally to avoid duplicate notifications.
Metadata
Frequently Asked Questions
What is Ticket Monitor Ichinosuke?
Monitors 春風亭一之輔's official site for new Tokyo performance tickets and sends notifications to a specified Discord webhook. It is an AI Agent Skill for Claude Code / OpenClaw, with 875 downloads so far.
How do I install Ticket Monitor Ichinosuke?
Run "/install ticket-monitor-ichinosuke" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Ticket Monitor Ichinosuke free?
Yes, Ticket Monitor Ichinosuke is completely free (open-source). You can download, install and use it at no cost.
Which platforms does Ticket Monitor Ichinosuke support?
Ticket Monitor Ichinosuke is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Ticket Monitor Ichinosuke?
It is built and maintained by Kazuma Mukai (@texka001); the current version is v1.0.4.
More Skills