skills/torale/SKILL.md
Monitor the web for conditions using AI-powered grounded search and get notified when they're met
npx skillsauth add prassanna-ravishankar/torale toraleInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Monitor the web for specific conditions using AI-powered grounded search. Torale watches for things so you don't have to. When a condition is met, it sends a webhook notification.
TORALE_API_KEY environment variable to your API keyBase URL: https://api.torale.ai/api/v1
All requests require the header: Authorization: Bearer {TORALE_API_KEY}
When a user wants to watch for something on the web, create a task:
POST /tasks
Content-Type: application/json
{
"name": "<short descriptive name>",
"search_query": "<what to search for>",
"condition_description": "<specific condition that triggers notification>",
"notifications": [
{
"type": "webhook",
"url": "<webhook URL to receive notifications>",
"headers": {"Authorization": "Bearer <webhook auth token if needed>"}
}
],
"context": {
"source": "claude-code",
"original_prompt": "<the user's original request>",
"action": "<what the user wants done when condition is met>"
}
}
Response includes id (task UUID).
The context.action field is delivered back in the webhook payload when the condition triggers, so include what the user wants you to do (e.g. "draft a tweet", "send a summary to Slack").
Webhook URLs must use HTTPS. If your endpoint is local, expose it via Tailscale or a reverse proxy with TLS.
GET /tasks
Returns all tasks for the authenticated user.
GET /tasks/{task_id}
Returns task details including last execution result.
PATCH /tasks/{task_id}
Content-Type: application/json
{"state": "paused"}
PATCH /tasks/{task_id}
Content-Type: application/json
{"state": "active"}
DELETE /tasks/{task_id}
When Torale detects the condition is met, it POSTs to the configured webhook URL:
{
"event_type": "task.condition_met",
"data": {
"task": {
"id": "uuid",
"name": "Task Name",
"search_query": "what was searched",
"condition_description": "what triggered"
},
"execution": {
"notification": "Human-readable summary of what was found"
},
"result": {
"answer": "Detailed evidence and analysis",
"grounding_sources": [{"url": "...", "title": "..."}]
},
"context": {
"source": "claude-code",
"original_prompt": "...",
"action": "what the user wanted done"
}
}
}
When you receive this webhook, read data.context.action to know what the user wants, and use data.execution.notification and data.result as your source material.
User: "Let me know when Apple announces iPhone 17"
User: "Watch for when Next.js 15 is released and summarize the changelog"
User: "Monitor competitor pricing for Acme Widget and alert me if they drop below $50"
development
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
development
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.
development
Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.
development
End-to-end Parallels smoke, upgrade, and rerun workflow for OpenClaw across macOS, Windows, and Linux guests. Use when Codex needs to run, rerun, debug, or interpret VM-based install, onboarding, gateway smoke tests, latest-release-to-main upgrade checks, fresh snapshot retests, or optional Discord roundtrip verification under Parallels.