- Home
- Skills
- Deletexiumu
- Agentskills Hub
- X Tracker
x-tracker_skill
- Python
2
GitHub Stars
2
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill deletexiumu/agentskills-hub --skill x-tracker- README.md3.6 KB
- SKILL.md5.4 KB
Overview
This skill tracks and archives your X (Twitter) data: following list, bookmarks, and your personal tweets. It supports periodic local JSON archiving, generating ranked daily digests, selecting rewrite candidates, profiling your writing style, and optional Notion sync. Use it to preserve timelines, create curated digests, and produce rewrite suggestions based on your own voice.
How this skill works
The skill uses X API v2 with OAuth2 scopes (tweet.read, users.read, follows.read, bookmark.read, offline.access) to fetch bookmarks, your tweets, and tweets from people you follow. It writes structured JSON into a local data directory, runs offline analyses to compute scores and date distributions, generates digest and rewrite outputs, and can push incremental updates into Notion using a configurable schema. Certain operations (following-list sync) require explicit user confirmation before being added to tracked accounts.
When to use it
- When you want to archive bookmarks or personal tweets to local JSON
- When you need a daily or periodic digest of followed accounts
- When you want rewrite candidates or content rewrites from top-performing tweets
- When you want a profile of your personal tweeting style
- When you want to sync following/bookmarks/tweets into Notion for organization
- When you want to aggregate content from people you follow for curation
Best practices
- Do not run follow-list sync without explicit confirmation; new follows require manual approval before tracking
- Run daily syncs for bookmarks and tweets, and schedule digest generation from local data to avoid extra API calls
- Check date_distribution before bulk rewriting; confirm if today’s tweets are a minority to avoid stale rewrites
- Skip or manually archive link-only tweets (is_link_only) before rewriting—capture page content first
- Keep config.json out of source control and back up local JSON archives regularly
- Use incremental Notion sync to avoid duplicate pushes and validate Notion schema before first sync
Example use cases
- Generate a curated daily digest (Top 20) from bookmarks and followed tweets for a newsletter
- Archive all bookmarks and personal tweets into local JSON for long-term storage and search
- Produce a batch of rewrite candidates in the user’s voice for cross-posting as threads or newsletter drafts
- Analyze historical tweets to create a style profile for consistent voice in future posts
- Sync selected following/bookmarks into a Notion database to manage sources and content ideas
FAQ
Primary archives are written to local JSON in the project data directory. Notion sync is optional and only occurs when you run the Notion sync command with configured credentials.
How does following-list syncing work?
Following list sync is gated: do not run it automatically. New follows must be reviewed and confirmed before being added to the tracked set to prevent unsolicited tracking.