x-kol-scan

Probe Twitter builders and fetch only new posts via statusesCount diffs.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/RealLoveBeatsHateFeelMe/Katelyn-openclaw --skill x-kol-scan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: x-kol-scan
Source: https://github.com/RealLoveBeatsHateFeelMe/Katelyn-openclaw/tree/main/workspace-katelyn/skills/x-kol-scan
Command: npx skills add https://github.com/RealLoveBeatsHateFeelMe/Katelyn-openclaw --skill x-kol-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Probes Twitter builders to detect new posts by comparing statusesCount diffs and fetches only the delta, dramatically reducing API usage.

Core Features & Use Cases

  • Two-pass scanning: probe 1 to detect changes, fetch 2 to retrieve the exact new posts.
  • Per-builder state tracking: stores last_seen_tweet_id, last_statuses_count, and last_probed_at to maintain continuity.
  • Cost-aware filtering: filters by age, type, counts, and deduplicates with existing posts to minimize wasted requests.

Quick Start

Configure the x-kol-scan skill and run the two-pass scan to detect and fetch only new tweets for each builder.

Frequently Asked Questions about x-kol-scan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reduce Twitter API calls when monitoring multiple accounts for new posts?

Reduce Twitter API calls by using a two-pass diff scan that compares statusesCount changes per builder first, then fetches only the exact new delta tweets instead of pulling full timelines repeatedly. State tracking maintains continuity across probes.

What is two-pass scanning for Twitter data collection and how does it work?

Two-pass scanning is a data collection method where pass one probes builder profiles to detect statusesCount diffs, and pass two fetches only the newly detected posts. This stateful approach tracks last_seen_tweet_id and last_probed_at to ensure efficient delta retrieval.

Can I track new tweets for a large list of builders without hitting API rate limits?

Track new tweets for up to 38 builders efficiently by applying cost-aware filtering. The scan enforces diff-based fetch limits, age and type filters, and deduplicates against existing posts, ensuring you only spend API calls on actual new content.

How do I set up stateful Twitter monitoring to fetch only new tweets?

Set up stateful Twitter monitoring by configuring the scan to maintain per-builder state variables like last_seen_tweet_id and last_statuses_count. This allows the system to calculate the exact tweet delta and execute targeted fetches rather than redundant timeline pulls.

Does diff-based scanning work with existing scoring modules for Twitter data?

Diff-based scanning integrates directly with scoring modules by providing filtered, deduplicated new tweets. The two-pass workflow ensures only relevant, newly detected posts are passed downstream, optimizing both API usage and scoring performance.

What are the limitations of using statusesCount diffs for Twitter data collection?

Using statusesCount diffs limits data collection to detecting volume changes, meaning deleted tweets or profile updates are not captured. This approach focuses strictly on identifying new posts to minimize API costs rather than tracking full timeline modifications.