Ticket Monitor Ichinosuke
PassAudited by ClawScan on May 1, 2026.
Overview
This skill appears to perform the stated ticket-monitoring and Discord notification task, with understandable notes around the webhook credential, dependency installation, and optional scheduled execution.
Before installing, create a dedicated Discord webhook for this monitor, keep the webhook URL private, install dependencies in an isolated environment if possible, and only configure cron if you want ongoing automatic checks. Expect the skill to contact the official ticket site, post new matching ticket information to Discord, and store a local list of already-seen ticket IDs.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Anyone who can run the skill with that webhook configured can cause ticket notifications to be posted to the linked Discord channel.
The skill uses a Discord webhook credential from the environment to post notification messages. This matches the stated purpose, but the webhook can send messages to the configured Discord destination.
DISCORD_WEBHOOK_URL = os.getenv("DISCORD_WEBHOOK_URL") ... response = requests.post(DISCORD_WEBHOOK_URL, json=data)Use a dedicated Discord webhook with the minimum needed channel access, keep the URL secret, and rotate it if it is exposed.
Installing the skill could change the Python environment used by OpenClaw or the host/container, depending on where the command is run.
The install helper installs unpinned Python packages and may alter the active/system Python environment. The packages are expected for scraping and webhook use, but the installation method is broader than a locked, isolated environment.
pip install requests beautifulsoup4 python-dotenv --break-system-packages || pip install requests beautifulsoup4 python-dotenv
Prefer installing in a container or virtual environment, pin dependency versions if possible, and review the environment before using --break-system-packages.
If configured, the skill may run daily and send Discord notifications without a fresh chat command each time.
The documentation suggests optional cron-based recurring execution. That is consistent with a monitoring skill, but it means the script can continue posting notifications on a schedule until the user disables it.
0 9 * * * docker exec <container_id> python3 /app/skills/ticket-monitor/scripts/ticket_monitor.py
Only add the cron job if recurring monitoring is desired, document the schedule, and remove or disable it when notifications are no longer needed.