Scheduled research runs with auto-alerts for NEW viral products. Runs on configurable schedule (hourly/daily/weekly), detects new products by comparing with previous runs, alerts on revenue threshold crossings, and sends notifications via Slack webhook. Use when working with kalodata monitor.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
Instruções da origem · Visualização somente leitura
name
kalodata-monitor
description
Scheduled research runs with auto-alerts for NEW viral products. Runs on configurable schedule (hourly/daily/weekly), detects new products by comparing with previous runs, alerts on revenue threshold crossings, and sends notifications via Slack webhook. Use when working with kalodata monitor.
Scheduled research automation with intelligent new product detection and Slack alerts.
Overview
Enables scheduled research automation with intelligent new product detection and Slack alerts. Runs on configurable schedules (hourly/daily/weekly), detects new products by comparing with previous runs, alerts on revenue threshold crossings, and sends notifications via Slack webhook.
When to Use
Trigger phrases:
"kalodata monitor"
"User wants continuous monitoring of TikTok Shop product categories"
"User needs automatic detection of NEW products entering the market"
"User wants alerts when products cross revenue thresholds"
User wants continuous monitoring of TikTok Shop product categories
User needs automatic detection of NEW products entering the market
User wants alerts when products cross revenue thresholds
User prefers Slack notifications for urgent product discoveries
User needs scheduled research runs without manual intervention
The Process
Configure monitoring profile – Set up profile with category, goal, schedule, and Slack webhook
Set alert conditions – Define revenue thresholds and other alert criteria
Run or schedule monitoring – Execute profile manually or let it run on schedule
Review alerts – Check Slack for notifications and new product findings
Take action – Investigate new products and make business decisions
When NOT to Use
Task is outside your authorization scope
You need to implement controls (use implementing-* skills)
Task is about analysis, not action (use analyzing-* skills)
Task is about defense, not offense (use defensive skills)
Red Flags
Expecting real-time monitoring (this skill runs on scheduled intervals, not streaming)
Using this for one-time research tasks (use kalodata-research-automation instead)
Monitoring unrelated categories or markets (stick to TikTok Shop Indonesia)
Ignoring alert configuration (alerts without thresholds are just noise)
Verification
Monitor profile saves without errors and loads on subsequent runs
New products are correctly detected by comparing with previous run data
Slack alerts send successfully and appear in configured channel
Revenue threshold alerts trigger when products cross configured limits
Scheduled runs execute without manual intervention
Do Not Use This Skill When
User only needs one-time research (use kalodata-research-automation)
User needs real-time product tracking (this is scheduled, not real-time)
Task is unrelated to TikTok Shop Indonesia market monitoring
Quick Start
This section covers quick start for the kalodata-monitor skill.
Key operations include input validation, core processing, and output verification.
Refer to the skill overview for detailed usage instructions.
# Set credentialsexport KALODATA_SESSION=your_session
export KALODATA_CF_CLEARANCE=your_cf_clearance
# List profiles
node index.js list
# Add a new monitor
node index.js add "Beauty Trends" Beauty trending daily
# Run a specific profile
node index.js run profile-123
# Run all enabled profiles
node index.js run
Core Features
Core operation execution with comprehensive error handling
Input validation and output quality assurance
Integration with existing workflows and toolchains
The monitor uses kalodata-product-research under the hood:
const result = await monitor.runProfile(profileId);
// Result contains:
{
profileId: string,
products: ProductSnapshot[], // All products from this runnewProducts: ProductSnapshot[], // NEW since last runcrossedThreshold: ProductSnapshot[], // Products crossing thresholdsalerts: Alert[], // Generated alerts
}
Scheduling
For continuous monitoring, add to cron:
# Run every hour
0 * * * * cd /path/to/project && node index.js scheduled
# Run daily at 6 AM
0 6 * * * cd /path/to/project && node index.js scheduled
Dependencies
This skill builds on:
kalodata-product-research: Core research capabilities
kalodata-research-automation: Full research workflow
Output Format
CLI output is designed for human readability:
📋 Monitor Profiles:
✅ Beauty Trending
Category: Beauty | Goal: trending | Schedule: daily
Last run: 2/19/2026, 10:30:00 AM
🚀 Running all enabled profiles...
📊 Run Results:
New products: 5
Threshold crossings: 2
Alerts: 3
✅ Slack notification sent successfully
Process
Analyze the task requirements
Apply domain expertise
Verify output quality
Anti-Rationalization Table
Rationalization
Reality
"I will handle auth later"
Retrofitting auth is 10x harder. Build it from day one.
"APIs do not change"
APIs change. Version your integrations and handle deprecations.
"Webhooks are optional"
Without webhooks, you miss real-time events. They are essential.
