菜单
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.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/oyi77/1ai-skills --skill kalodata-monitor命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Android and mobile application security testing — emulators, rooting, traffic interception, dynamic instrumentation. Use when testing mobile apps for vulnerabilities, reversing APKs, or bypassing security controls on Android.
Self-reflection + Self-criticism + Auto-learning from corrections + Self-organizing memory. Agent evaluates its own work, catches mistakes, and improves permanently. Use when working with self improving.
Plan and execute a comprehensive red team engagement covering reconnaissance through post-exploitation using MITRE ATT&CK-aligned TTPs to evaluate an organization's detection and response capabilities. Use when working with conducting full scope red team engagement.
基于 SOC 职业分类
正在显示 SKILL.md
| 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. |
| domain | integrations |
| author | oyi77 |
| license | Apache-2.0 |
| subdomain | integrations |
| tags | ["api","integrations","kalodata","monitor","slack","third-party","webhook"] |
| metadata | {"model":"sonnet"} |
| version | 1.0.0 |
Scheduled research automation with intelligent new product detection and Slack alerts.
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.
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
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.
import { createMonitor, loadMonitorConfig, createProfile } from './index.js';
const config = loadMonitorConfig('./.kalodata-monitor');
const monitor = createMonitor(config);
const profile = createProfile({
id: 'beauty-trending',
name: 'Beauty Trending',
category: 'Beauty',
goal: 'trending',
schedule: 'daily',
slackWebhook: 'https://hooks.slack.com/services/xxx',
});
monitor.saveProfile(profile);
const result = await monitor.runProfile('beauty-trending');
console.log(`Found ${result.newProducts.length} new products`);
# Set credentials
export 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
Each profile defines what to monitor and when:
interface MonitorProfile {
id: string;
name: string;
category: string; // Product category name or ID
goal: string; // Research goal (trending, emerging, etc.)
schedule: 'hourly' | 'daily' | 'weekly';
alerts: AlertCondition;
topProducts?: number; // Default: 20
slackWebhook?: string;
enabled?: boolean;
}
Configure when to trigger notifications:
interface AlertCondition {
revenueMin?: number; // Absolute revenue threshold
revenueGrowthMultiplier?: number; // Multiplier vs previous run
opportunityScoreMin?: number; // Minimum opportunity score (0-100)
revenueCrosses?: number; // Alert when crossing this revenue
}
Automatically compares current run with previous run to identify:
Rich Slack messages with:
Stores in .kalodata-monitor/ directory:
config.json - All profile configurations{profile-id}.json - Previous run snapshots for comparison{
"enabled": true,
"autoRun": false,
"timeout": 30000,
"retries": 3
}
Set environment variables as needed for authentication and endpoints.
KALODATA_SESSION=your_session_cookie
KALODATA_CF_CLEARANCE=your_cf_clearance_token
Create monitors via CLI or programmatically:
| Parameter | Description | Required |
|---|---|---|
| id | Unique identifier | Yes |
| name | Display name | Yes |
| category | Product category | Yes |
| goal | Research goal | Yes |
| schedule | hourly/daily/weekly | Yes |
| slackWebhook | Slack webhook URL | No |
| Command | Description |
|---|---|
list | List all monitor profiles |
add <name> <category> <goal> <schedule> [webhook] | Add new profile |
run [profile-id] | Run profile or all profiles |
scheduled | Run profiles due for their schedule |
remove <profile-id> | Remove a profile |
enable <profile-id> | Enable a profile |
disable <profile-id> | Disable a profile |
config | Show full configuration |
# Basic usage
invoke <skill-name> with appropriate parameters
# Advanced usage with options
invoke <skill-name> --option value --verbose
node index.js add "Daily Beauty" Beauty trending daily $SLACK_WEBHOOK
node index.js add "Weekly Emerging" Beauty emerging weekly
node index.js add "Hourly High-Opp" Electronics trending hourly
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 run
newProducts: ProductSnapshot[], // NEW since last run
crossedThreshold: ProductSnapshot[], // Products crossing thresholds
alerts: Alert[], // Generated alerts
}
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
This skill builds on:
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
| 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. |