twitter-analysis
Twitter/X data query. Provides general endpoints (auto data-source) and ReadX direct endpoints for deep tweet analysis, conversation threads, quote tweets, retweeters, relationship checks, and more.
What this skill does
# Twitter Analysis — Social Data **Base URL**: `https://crab-skill.opsat.io` All endpoints are `POST`. Body is JSON. Requires Crab signature headers. --- ## 1. General Endpoints (auto data-source selection) | Endpoint | Description | Required Fields | |----------|-------------|-----------------| | `/api/twitter/user` | User profile | `username` | | `/api/twitter/tweets` | User tweets (no replies/retweets) | `username` | | `/api/twitter/replies` | User tweets + replies | `username` | | `/api/twitter/search` | Search tweets with filters | at least one filter | | `/api/twitter/kol-followers` | KOL followers (6551 only) | `username` | | `/api/twitter/deleted-tweets` | Deleted tweet history (6551 only) | `username` | | `/api/twitter/follower-events` | Follow/unfollow events | `username` | ### Common Optional Fields | Field | Endpoints | Description | |-------|-----------|-------------| | `maxResults` | tweets, replies, search, deleted-tweets, follower-events | Number of results (default 20) | | `product` | tweets, replies, search | `Latest` / `Top` (default `Latest` for tweets/replies, `Top` for search) | ### Search Filters (`/api/twitter/search`) | Field | Description | |-------|-------------| | `keywords` | Search keywords | | `fromUser` | Filter by author | | `toUser` | Filter by reply target | | `mentionUser` | Mentioned user | | `hashtag` | Hashtag | | `excludeReplies` | Exclude replies | | `excludeRetweets` | Exclude retweets | | `minLikes` | Minimum likes | | `minRetweets` | Minimum retweets | | `minReplies` | Minimum replies | | `sinceDate` | Start date (YYYY-MM-DD) | | `untilDate` | End date (YYYY-MM-DD) | | `lang` | Language code | ### Follower Events Filter | Field | Description | |-------|-------------| | `isFollow` | `true` = new follows, `false` = unfollows (default `true`) | --- ## 2. ReadX Direct Endpoints ReadX endpoints provide deep tweet-level analysis capabilities. ### Tweet Detail & Content | Endpoint | Description | Required Fields | |----------|-------------|-----------------| | `/api/readx/tweet-detail` | Tweet detail (minimal) | `tweet_id` | | `/api/readx/tweet-detail-v2` | Tweet detail (recommended, includes views/source) | `tweet_id` | | `/api/readx/tweet-detail-v3` | Tweet detail (includes view_count) | `tweet_id` | | `/api/readx/tweet-article` | Long-form article attached to tweet | `tweet_id` | | `/api/readx/tweet-results-by-ids` | Batch fetch multiple tweets | `tweet_ids` (comma-separated) | ### Conversation & Replies | Endpoint | Description | Required Fields | |----------|-------------|-----------------| | `/api/readx/tweet-detail-conversation` | Tweet + reply thread (single page) | `tweet_id` | | `/api/readx/tweet-detail-conversation-v2` | Tweet + full reply thread (paginated) | `tweet_id`, optional `cursor` | ### Engagement & Spread | Endpoint | Description | Required Fields | |----------|-------------|-----------------| | `/api/readx/tweet-quotes` | Who quoted this tweet | `tweet_id`, optional `cursor` | | `/api/readx/tweet-retweeters` | Who retweeted this tweet | `tweet_id`, optional `cursor` | | `/api/readx/tweet-favoriters` | Who liked this tweet | `tweet_id`, optional `cursor` | ### User Relationships | Endpoint | Description | Required Fields | |----------|-------------|-----------------| | `/api/readx/followers-light` | Follower list (light fields) | `username`, optional `count` | | `/api/readx/following-light` | Following list (light fields) | `username`, optional `count` | | `/api/readx/user-verified-followers` | Verified followers (blue check) | `user_id` (rest_id), optional `cursor` | | `/api/readx/friendships-show` | Relationship between two users | `source_screen_name`, `target_screen_name` | ### Advanced Search | Endpoint | Description | Required Fields | |----------|-------------|-----------------| | `/api/readx/search2` | Twitter advanced search syntax | `q` (full query string) | Optional fields for search2: `count` (default 20), `type` (`Top`/`Latest`, default `Top`), `cursor`, `safe_search` **search2 query examples:** - `bitcoin from:elonmusk min_faves:100` - `"project name" -filter:replies min_faves:50` - `@username OR #hashtag since:2025-01-01` --- ## When to Use Which | Goal | Use | |------|-----| | Basic user info | `/api/twitter/user` | | User's recent posts | `/api/twitter/tweets` | | Search for mentions/discussions | `/api/twitter/search` or `/api/readx/search2` (advanced) | | KOL following the project | `/api/twitter/kol-followers` | | Read tweet replies/comments | `/api/readx/tweet-detail-conversation-v2` | | Who quoted a tweet (KOL amplification) | `/api/readx/tweet-quotes` | | Who retweeted (spread network) | `/api/readx/tweet-retweeters` | | Who the project follows back | `/api/readx/following-light` | | Verified/notable followers | `/api/readx/user-verified-followers` | | Check if two people follow each other | `/api/readx/friendships-show` | | Deleted tweets | `/api/twitter/deleted-tweets` | | Follow/unfollow events | `/api/twitter/follower-events` | --- ## Fallback Behavior | Scenario | Behavior | |---------------------------|----------------------------------| | All data sources fail | Return an error | | Primary source fails | Automatically fall back to backup source | | ReadX not configured | Skip ReadX endpoints, use general endpoints only |
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.