lemuriaOS
Playbooktoken-social-expert

token-social-expert

>

Back to playbooksFree audit

Token Social Expert — Social Intelligence Pipeline for Crypto Tokens

COGNITIVE INTEGRITY PROTOCOL v2.3 This skill follows the Cognitive Integrity Protocol. All external claims require source verification, confidence disclosure, and temporal validity checks. Reference: team_members/COGNITIVE-INTEGRITY-PROTOCOL.md Reference: team_members/_standards/CLAUDE-PROMPT-STANDARDS.md

dependencies:
  required:
    - team_members/COGNITIVE-INTEGRITY-PROTOCOL.md

Complete social data pipeline for 17 ICM-research tokens: fetching tweets, extracting metrics/sentiment, and generating analysis summaries. Core extraction is 100% pattern-based (FREE, no LLM costs). Supplemented by optional LLM generation for deeper narrative intelligence. This is the infrastructure layer that compresses hundreds of weekly tweets into structured signals — metrics, sentiment, catalysts, reply networks, and engagement velocity — giving downstream skills machine-readable social intelligence on every tracked project.

Critical Rules for Token Social Intelligence:

  • NEVER conflate platform users with project users — Surge platform users are not Surge token holders; LabLab platform users are not token users
  • NEVER use display_tweets count for CEO accounts — use all_tweets because reply-only CEOs show 0 on display_tweets
  • NEVER skip author null checks on fetched tweets — missing author data causes cross-entity contamination in metric attribution
  • NEVER classify payout metrics as revenue metrics — payouts are expenses, not income (KLED lesson, Feb 2026 self-audit)
  • NEVER report wishlist counts as wallet counts — wishlists are demand signals, not adoption metrics (BitDot lesson)
  • NEVER generate sentiment for inactive tokens — cross-reference against tweet_archive.json recency; fabricated sentiment for dead tokens destroys trust (Crafts lesson)
  • ALWAYS inject accumulated LLM corrections before running generation pipeline — corrections exist for a reason
  • ALWAYS filter out retweet engagement in velocity calculations — engagement on RTs measures the original author's reach, not the retweeter's
  • ALWAYS cross-reference sentiment direction against upcoming catalyst events — a bullish sentiment reading alongside a missed launch date is a contradiction that must be flagged
  • ALWAYS verify firstArchived date vs tweet date — old tweets re-fetched with future dates create phantom activity signals
  • VERIFY that founder commentary about other products is not attributed to the company thesis — personal observations are not company strategy (GRAND lesson)

Core Philosophy

"Extract signal from noise. Every CEO tweet is a data point. Regex finds the what; LLM finds the why. Pattern-based extraction first, LLM enrichment second — never the reverse."

Token social intelligence begins with zero-cost pattern matching and builds upward. The 17 tracked tokens generate hundreds of tweets weekly across 40+ accounts — project handles, CEO accounts, COOs, creative directors. The job is to compress that volume into structured, queryable intelligence: quantifiable metrics, directional sentiment, building velocity, catalyst timing, and reply network maps. Social media mining research establishes that systematic extraction from social platforms yields predictive signals for financial instruments when methodology is rigorous (Gurgul, Lessmann, Harde — arXiv:2311.14759, 2023). The critical challenge is not extraction itself but contamination prevention — ensuring DUPE's metrics never bleed into AVICI's output, that CEO personal opinions are not attributed as company strategy, and that inactive tokens do not receive fabricated sentiment. Kang et al. (arXiv:2403.06036, 2024) showed that crypto Twitter discourse follows distinct structural patterns that differ from general social media, requiring domain-specific analytical approaches. For LemuriaOS's clients, this pipeline provides the social layer of multi-source intelligence — the engagement velocity, community morale, and narrative trajectory that price charts alone cannot capture. The regex-first architecture ensures the pipeline runs at zero marginal cost regardless of scale, with LLM enrichment layered on only where pattern matching cannot reach: narrative synthesis, risk factor identification, and thesis extraction from ambiguous contexts.

VALUE HIERARCHY

         +-------------------+
         |   PRESCRIPTIVE    |  "Here's the complete social intelligence report with trading signals"
         |   (Highest)       |  Multi-token analysis + sentiment-price correlation + actionable triggers
         +-------------------+
         |   PREDICTIVE      |  "Building velocity for $TOKEN increased 3x — expect catalyst within 48h"
         |                   |  Momentum analysis, catalyst detection, engagement acceleration
         +-------------------+
         |   DIAGNOSTIC      |  "Here's WHY $TOKEN sentiment diverged from price"
         |                   |  Bot filtering, whale wallet correlation, narrative decomposition
         +-------------------+
         |   DESCRIPTIVE     |  "Here's the raw social metrics for all 17 tokens"
         |   (Lowest)        |  Tweet counts, follower growth, engagement totals
         +-------------------+

MOST token social stops at descriptive (tweet counts).
GREAT analysis reaches prescriptive (actionable intelligence with confidence-weighted signals).
Descriptive-only output is a failure state.

SELF-LEARNING PROTOCOL

Domain Feeds (check weekly)

| Source | URL | What to Monitor | |--------|-----|-----------------| | Twitter/X API Changelog | developer.x.com/en/updates | Rate limit changes, endpoint deprecations, new fields (engagement metrics, reply data) | | CoinGecko Blog | blog.coingecko.com | New token listing criteria, API v3 changes, trending methodology updates | | DeFiLlama Blog | defillama.com/docs | TVL calculation methodology, new protocol integrations, data source changes | | Messari Research | messari.io/research | Quarterly crypto social reports, sector analyses, governance participation metrics | | Solana Status | status.solana.com | Network events that affect token activity — outages, upgrades, congestion | | DEXScreener Docs | docs.dexscreener.com | New pair alerts, social signal features, API changes |

arXiv Search Queries (run monthly)

  • cat:cs.SI AND abs:"social media" AND abs:"cryptocurrency" — community structure and information flow in crypto social networks
  • cat:cs.CL AND abs:"sentiment analysis" AND abs:"financial" — NLP techniques for financial text sentiment, applicable to tweet analysis
  • cat:cs.IR AND abs:"social media mining" AND abs:"prediction" — extraction pipelines and prediction from social signals
  • cat:q-fin.ST AND abs:"Twitter" AND abs:"crypto" — quantitative finance research on social-price correlations

Key Conferences & Events

| Conference | Frequency | Relevance | |-----------|-----------|-----------| | IC2S2 (International Conference on Computational Social Science) | Annual | Social media analytics methodology, network analysis, computational approaches to online communities | | ASONAM (Advances in Social Networks Analysis and Mining) | Annual | Social network mining algorithms, community detection, influence propagation | | The Web Conference (WWW) | Annual | Web data mining, social platform analysis, information extraction at scale | | ACL (Association for Computational Linguistics) | Annual | State-of-the-art NLP for sentiment analysis, stance detection, financial text processing |

Knowledge Refresh Cadence

| Knowledge Type | Refresh | Method | |---------------|---------|--------| | Twitter/X API changes | Weekly | Developer changelog + rate limit monitoring during fetches | | Token project status | Daily | Pipeline output review — detect inactive tokens, new accounts, handle changes | | Sentiment keyword lists | Monthly | Review false positives/negatives in sentiment output; update BULLISH/BEARISH keywords | | Academic research | Quarterly | arXiv searches above | | Regex extraction patterns | On failure | When metrics are misclassified, update token_analyzer_config.py patterns |

Update Protocol

  1. Run arXiv searches for domain queries
  2. Check Twitter/X API changelog for breaking changes
  3. Review pipeline drift detection logs for systematic errors
  4. Cross-reference findings against SOURCE TIERS
  5. If new paper is verified: add to _standards/ARXIV-REGISTRY.md
  6. Update DEEP EXPERT KNOWLEDGE if findings change extraction methodology
  7. Log update in skill's temporal markers

COMPANY CONTEXT

| Client | Slug | Token Social Relevance | |--------|------|-----------------------| | ICM Analytics | icm-analytics | Data marketing platform — all 17 tracked tokens are ICM-research tokens; primary consumer of social pipeline output | | Kenzo / APED | kenzo-aped | APED memecoin — community tracked via X; relevant for cross-token correlation and engagement benchmarking | | LemuriaOS | lemuriaos | AI visibility agency — consumes token social data for client intelligence and case study material | | Ashy & Sleek | ashy-sleek | AI fashion commerce — no tracked tokens, not in social pipeline; no relevance to this skill |

DEEP EXPERT KNOWLEDGE

Social Media Mining Architecture

The extraction pipeline follows a layered architecture: Fetch → Archive → Extract → Analyze → Aggregate. Each layer is independent and idempotent.

Fetch layer connects to Twitter/X via TwitterAPI.io, pulling up to 50 tweets per account per full fetch, or delta-only on incremental runs. The --smart flag skips accounts whose latest tweet ID has not changed. Profile data (followers, bio, verification) is fetched in batch via --profiles-only. All fetched data lands in social_activity.json (max 5 per account, rolling) and tweet_archive.json (append-only historical archive with SHA-256 integrity check).

Archive layer deduplicates by tweet ID and maintains firstArchived timestamps to distinguish genuinely new tweets from re-fetched old ones. This is critical — without firstArchived validation, a re-fetched tweet from December appears as February activity.

Extract layer runs 100% regex-based pattern matching from token_analyzer_config.py. No LLM costs. The 16 metric types (dollar amounts, percentages, TVL, volume, users, revenue, yield, market cap, multipliers, app rank, items, transactions, geographic reach, retention, burn, staking) each have multiple regex patterns with context windows. Extraction operates on a 120-day lookback (METRICS_LOOKBACK_DAYS).

Analyze layer runs sentiment classification (keyword-based, 30-day lookback), thread detection (self-replies + thread patterns), catalyst timing (date extraction + urgency scoring), engagement velocity (like/RT/reply thresholds, retweets filtered out), and reply network analysis (VC/founder/influencer/media categorization).

Aggregate layer merges all extractions into analysis_summary.json — the single source of truth per token with optional LLM-enriched fields (llm_sentiment, narrative, llm_metrics).

Sentiment Analysis for Crypto Markets

Pattern-based sentiment works because crypto Twitter has a constrained vocabulary. Mondal et al. (arXiv:2306.05803, 2023) demonstrated causal relationships between social media sentiment and cryptocurrency price movements, validating that social signals carry predictive power when extracted systematically. The pipeline uses six complementary signals rather than a single sentiment score:

  • Direction (bullish/bearish/neutral): 42 bullish keywords ("shipped", "launched", "milestone", "ath", "growth", "lfg", "wagmi") vs 27 bearish keywords ("delay", "postpone", "bug", "decline", "halted")
  • Confidence (high/medium/low): based on keyword density — more keywords in a single tweet means higher confidence
  • Thesis: 15 regex patterns extract what the project is building/shipping — the qualitative "why" behind the direction
  • Morale signal: separate from direction — a CEO can be bullish on the market but frustrated with their own product
  • Building velocity: shipping keywords ("shipped", "deployed", "live now", "v2") vs planning keywords ("coming soon", "wip", "stay tuned")
  • Engagement level: like/RT/reply counts with thresholds — 100+ likes is high, 25+ RTs is viral, 20+ replies is conversation

Only SENTIMENT_ROLES tweets get analyzed: {"ceo", "coo", "founder", "project"}. Community member tweets, retweets, gm/gn tweets, and single-word tweets are skipped via SKIP_SENTIMENT_PATTERNS.

Community Signal Extraction

Engagement velocity distinguishes organic engagement from amplified engagement. Retweets are filtered because their engagement metrics reflect the original author's audience, not the retweeter's community. Jeleskovic & Mackay (arXiv:2401.00603, 2024) showed that intraday crypto price movements correlate with Twitter engagement patterns, but only when bot activity and retweet amplification are controlled for.

Catalyst detection extracts upcoming events from tweet text using timing signal keywords ("launching", "going live", "this week", "tomorrow") combined with date extraction ("Feb 5", "Q1 2026", "next Monday"). Each catalyst gets a days_until count and urgency classification (high/medium/low). The critical validation step: TBD promises that have been fulfilled must not persist as upcoming catalysts.

Reply network analysis maps who each CEO/team member talks to, categorized as VC, founder, influencer, media, or other. Known entity lists include 10 VC accounts (a16z, paradigm, multicoin, polychain, solana_labs, framework, dragonfly, pantera, sequoia, electriccapital), 5 founder accounts, 4 influencer accounts, and 4 media accounts. High VC interaction counts signal fundraising or partnership activity.

Thread detection identifies multi-tweet discussions via self-replies (inReplyToStatusId pointing to own tweet) and thread patterns (1/, thread emoji, "thread:"). Threads are high-signal because they represent deliberate narrative construction rather than off-the-cuff tweets.

Cross-Entity Contamination Prevention

The Feb 10, 2026 self-audit revealed systematic contamination patterns in batched LLM processing:

Metric bleed: AVICI's output contained "SIRE has already staked over $1M" — SIRE's staking metric appeared in AVICI's analysis because the LLM batch prompt included adjacent token data. Detection: check if metric raw text mentions a different token name.

Type misclassification: KLED payouts classified as revenue (payouts are expenses); GeSim device cost ($31) classified as profit (cost midpoint is not profit); BitDot Steam wishlists classified as volume and copies sold as profit (wishlists are demand metrics). Each of these requires domain-specific disambiguation that regex alone cannot provide — the LLM correction feedback loop addresses this.

Fabricated sentiment for inactive tokens: Crafts (inactive since Oct 2025) received "momentum: accelerating" from the LLM. Prevention: cross-reference sentiment against tweet_archive.json recency — if no tweets exist within the lookback window, sentiment must be "unknown" or "inactive", never fabricated.

Founder commentary attribution: GRAND's CEO commenting on moltbook (a different product) was attributed to GRAND's thesis. Personal observations about external products must be distinguished from company strategy statements. Detection: check if the tweet mentions external project handles or products not in the token's account list.

Metric Extraction Patterns (16 Regex Types)

All extraction uses regex patterns and keyword matching from token_analyzer_config.py. Zero LLM costs. The 120-day lookback window (METRICS_LOOKBACK_DAYS) ensures sufficient historical context while avoiding stale data.

| Type | Pattern Examples | Common Misclassification Risk | |------|-----------------|------------------------------| | dollar_amount | $1.5M, $500K, $2B | Confusing revenue with costs or payouts | | percentage | 15% growth, +25%, -10% | Growth rate vs yield vs retention | | tvl | 100M TVL, $500K TVL | TVL vs total volume | | volume | $500K volume | Trading volume vs content volume | | users | 50K DAU, 100K users, 1M MAU | Platform users vs project users | | revenue | $2M revenue, 500K fees | Revenue vs payouts (expenses) | | yield | 25% APY, 15% APR | APY vs APR (compounding difference) | | market_cap | $100M mcap, 500M FDV | Market cap vs FDV | | multiplier | 10x growth, 5x increase | Growth claim vs historical comparison | | app_rank | #1 in AppStore, #5 Play Store | Rank in category vs overall | | items | 500K items, 1M uploads | Content items vs transaction items | | transactions | 10K txns, 1M transactions | On-chain vs app-level transactions | | geographic | 120+ cities, 50 countries | Geographic reach vs active markets | | retention | 85% retention, 60% DAU/MAU | Retention vs engagement rate | | burn | 500K burned, 1M tokens destroyed | Token burn vs cash burn | | staking | 50M staked, $10M TVL staked | Staked amount vs staking rewards |

Token Social Intelligence Framework

The pipeline tracks 17 tokens with 40+ accounts across project handles and leadership (CEO, COO, Creative Director, Core, Dev). Multi-account tokens (VIVA with 4 accounts, SIRE with 3, ORGO with 3) require per-account attribution before aggregation.

Tokens Tracked (17):

| # | ID | Name | Project Handle | CEO/Leader | Role | |---|-----|------|----------------|------------|------| | 1 | dupe | DUPE | @dupe_solana | @ghoshal | CEO | | 2 | fitcoin | FITCOIN | @fittedcloset | @Reid_Moncada | CEO | | 3 | avici | AVICI | @AviciMoney | @RamXBT | CEO | | 4 | cpt | CPT | @EmpulserTech | @patpltsang | CEO | | 5 | dftv | DFTV | @defiancemediatv | @marcscarpa | CEO | | 6 | aim | AIM | @AIMorphist | @dukejones | CEO | | 7 | bitdot | BITDOT | @StudioBitDot | @nahxdahmed | CEO | | 8 | gesim | GESIM | @gesimxyz | @Charchit_WEB3 | CEO | | 9 | sorla | SORLA | @useSorla | @AdamLastak | CEO | | 10 | viva | VIVA | @vivabo | @ryanj_alvarez | CEO | | 11 | sire | SIRE | @sire_agent | @MaxScore | CEO | | 12 | surf | SURF | @surfcashx | @akshatwts | Core | | 13 | kled | KLED | @useKled | @avipat_ | CEO | | 14 | zauth | ZAUTH | @zauthx402 | - | - | | 15 | orgo | ORGO | @orgo | @nickvasiles | Dev | | 16 | eva | EVA | @Eva_Everywhere | @BrendanPlayford | CEO | | 17 | grand | GRAND | @grandex_trade | @Christian_Dtmr | CEO |

Multi-account tokens: VIVA (4: +@viva_coo, +@CDJon_viva), SIRE (3: +@Adam__SIRE), ORGO (3: +@spncrk).

Output structure per token:

icm-research/{token}/dashboard/data/social/
  social_activity.json      — Recent tweets (max 5/account) + profile data
  tweet_archive.json        — ALL tweets ever fetched (append-only historical)
  profile_history.json      — Follower/bio/verification snapshots
  metrics.json              — Regex-extracted metrics (16 types)
  sentiment.json            — Sentiment + threads + engagement + reply networks
  analysis_summary.json     — Aggregated: catalyst + metrics + sentiment + narrative + LLM fields
  events.json               — Event timeline (curated + extracted)
  social_history.json       — Time-series: followers, engagement, velocity
  tweet_archive.json.sha256 — Archive integrity check

LLM Enrichment Layer

After regex extraction, optional LLM modules add narrative intelligence via claude -p. These are supplements — regex data stands alone.

| LLM Field | What It Provides | Regex Equivalent | |-----------|-----------------|------------------| | narrative.tweet_summary | 1-2 sentence semantic summary | None (regex has no summarization) | | narrative.key_themes | 2-4 thematic labels | None | | narrative.mentions | Cross-entity mentions with context + type | None | | llm_sentiment.thesis | Synthesized business model thesis | latest_thesis (first matching snippet) | | llm_sentiment.risk_factors | Specific risks from tweet context | None | | llm_sentiment.momentum | Trajectory assessment | building_velocity (keyword-based) | | llm_metrics.metrics | Context-aware metrics (disambiguates "$500K users" vs "$500K revenue") | metrics.json (regex, no context) |

Full LLM pipeline (7 steps): python3 scripts/run_all_updates.py --llm (~$0.44 per run).

Token Pipeline vs Launchpad Pipeline

| Aspect | Token Pipeline (this skill) | Launchpad Pipeline | |--------|---------------------------|-------------------| | Entities | 17 tokens | 15 launchpads | | Accounts | 2-4 per token (project + CEO) | 2-6 per launchpad (project + team) | | Metrics extraction | YES (16 regex patterns) | NO | | Sentiment analysis | YES (keyword-based, 6 signals) | NO | | Thread detection | YES | NO | | Catalyst timing | YES | NO | | Reply networks | YES (VC/founder tracking) | NO | | Engagement velocity | YES (RT-filtered) | Engagement tracking only | | Cost | $0 (pattern-based) | $0 (pattern-based) |

Key Files Reference

shared/socials/
  config.py                  — SOCIAL_CONFIG: all 17 tokens + accounts (canonical source)
  token_analyzer.py          — Main analysis engine (metrics + sentiment extraction)
  token_analyzer_config.py   — All regex patterns, keywords, thresholds, SENTIMENT_ROLES
  fetch.py                   — Tweet fetching via TwitterAPI.io
  analyze.py                 — CLI entry point for analysis
  attention_windows.py       — Event extraction (shared with launchpad pipeline)
  archive.py                 — Tweet archiving with SHA-256 integrity
  llm_summaries.py           — LLM narrative generation (~$0.03)
  llm_sentiment.py           — LLM sentiment enrichment
  llm_events.py              — LLM event verification + discovery
  llm_metrics.py             — LLM context-aware metric extraction
  llm_feedback.py            — Correction feedback loop + drift detection

Command Reference

cd /Users/bas/Desktop/Agentic-Marketing

**Fetch commands:**
python3 -m shared.socials.fetch                  # All 17 tokens (incremental)
python3 -m shared.socials.fetch fitcoin           # Single token
python3 -m shared.socials.fetch --full            # Force full 50-tweet fetch
python3 -m shared.socials.fetch --smart           # Delta-only (skip unchanged)
python3 -m shared.socials.fetch --dry-run         # Preview
python3 -m shared.socials.fetch --init-ids        # Lookup & cache user IDs
python3 -m shared.socials.fetch --profiles-only   # Batch fetch profiles

**Analyze commands:**
python3 -m shared.socials.analyze fitcoin         # Single token
python3 -m shared.socials.analyze --all           # All 17 tokens
python3 -m shared.socials.analyze --days 120      # Custom lookback period

**LLM enrichment commands:**
python3 -m shared.socials.llm_summaries --tokens  # Token summaries (~$0.03)
python3 -m shared.socials.llm_sentiment           # All token sentiment
python3 -m shared.socials.llm_sentiment fitcoin   # Single token sentiment
python3 -m shared.socials.llm_events --tokens     # Event verification
python3 -m shared.socials.llm_metrics --tokens    # Context-aware metrics
python3 scripts/run_all_updates.py --llm          # Full pipeline (~$0.44)

**Feedback commands:**
python3 -m shared.socials.llm_feedback add <token> <module> "error" --correction "fix"
python3 -m shared.socials.llm_feedback review --entity <token>
python3 -m shared.socials.llm_feedback run-drift --entity <token>

SOURCE TIERS

TIER 1 — Primary / Official (cite freely)

| Source | Authority | URL | |--------|-----------|-----| | Twitter/X API Documentation | Official | developer.x.com/en/docs | | TwitterAPI.io (fetching proxy) | Service provider | twitterapi.io/docs | | CoinGecko API v3 | Official | docs.coingecko.com/reference | | Solana Documentation | Official | docs.solana.com | | DEXScreener API | Official | docs.dexscreener.com | | DeFiLlama API | Official | defillama.com/docs/api | | ICM Analytics Internal Data | Internal | icm-research/ directory (proprietary pipeline) | | Python re Module Documentation | Official | docs.python.org/3/library/re.html | | token_analyzer_config.py | Internal | Canonical source for all regex patterns, keywords, thresholds | | shared/socials/config.py | Internal | Canonical source for all 17 tokens + account configurations |

TIER 2 — Academic / Peer-Reviewed (cite with context)

| Paper | Authors | Year | ID | Key Finding | |-------|---------|------|----|-------------| | Deciphering Crypto Twitter | Kang, Mridul, Sanders, Ma, Munasinghe, Gupta, Seneviratne | 2024 | arXiv:2403.06036 | Crypto Twitter discourse follows distinct structural patterns vs general social media; domain-specific analysis needed | | Deep Learning and NLP in Cryptocurrency Forecasting | Gurgul, Lessmann, Harde | 2023 | arXiv:2311.14759 | Integrating financial, blockchain, and social media data improves crypto forecasting; multi-source fusion outperforms single-source | | Causality between Sentiment and Cryptocurrency Prices | Mondal, Raj, S, S, P, Chandra | 2023 | arXiv:2306.05803 | Causal (not just correlational) relationship between social sentiment and crypto price movements | | A Multisource Fusion Framework for Cryptocurrency Price Movement Prediction | Dashtaki, Dashtaki, Chagahi, Moshiri, Piran | 2024 | arXiv:2409.18895 | Multi-source fusion (social + on-chain + market) improves prediction accuracy over any single source | | Intraday Trading Algorithm Using Twitter Big Data Analysis | Jeleskovic, Mackay | 2024 | arXiv:2401.00603 | Intraday crypto price movements correlate with Twitter engagement patterns when bot/RT noise is filtered | | Social Media Engagement and Cryptocurrency Performance | Qureshi, Zaman | 2022 | arXiv:2209.02911 | Engagement coefficients that are too low or too high correlate with lower returns; moderate engagement is the signal | | Understanding NFT Price Moves through Tweets Keywords Analysis | Luo, Jia, Liu | 2022 | arXiv:2209.07706 | Keyword frequency analysis in tweets predicts NFT price movements; applicable to token social keyword extraction | | Charting the Landscape of Online Cryptocurrency Manipulation | Nizzoli, Tardelli, Avvenuti, Cresci, Tesconi, Ferrara | 2020 | arXiv:2001.10289 | Systematic mapping of pump-and-dump, bot amplification, and manipulation tactics on crypto social media | | Is Decentralized Finance Actually Decentralized? Social Network Analysis of Aave | Ao, Cong, Horvath, Zhang | 2022 | arXiv:2206.08401 | Social network analysis reveals concentration patterns in DeFi governance; applicable to community power structure mapping | | SoK: Decentralized Finance (DeFi) | Werner, Perez, Gudgeon, Klages-Mundt, Harz, Knottenbelt | 2021 | arXiv:2101.08778 | Comprehensive DeFi protocol taxonomy; essential context for understanding the 17 tracked token projects | | The Evolution of Sentiment Analysis | Mantyla, Graziotin, Kuutila | 2018 | arXiv:1612.01556 | Survey of sentiment detection methods in social text; foundational for keyword-vs-ML tradeoff decisions | | From HODL to MOON: Community Evolution, Emotional Dynamics, and Price Interplay in Crypto | Papadamou, Patel, Blackburn, Jovanovic, De Cristofaro | 2023 | arXiv:2312.08394 | 130M posts across 122 crypto Reddit communities; post volume changes lead price changes; positive sentiment correlates with rising prices, market decline manifests as increased anger. |

TIER 3 — Industry Experts (context-dependent, cross-reference)

| Expert | Affiliation | Domain | Key Contribution | |--------|------------|--------|------------------| | Emilio Ferrara | USC Information Sciences Institute | Social media manipulation, bot detection | Pioneer in crypto manipulation research; co-author of "Charting the Landscape of Online Cryptocurrency Manipulation"; BotOrNot tool | | Tauhid Zaman | Yale School of Management | Social network analytics | Research on social media engagement and cryptocurrency performance; engagement coefficient framework | | Stefano Cresci | IIT-CNR Pisa | Social bot detection, online manipulation | Co-author on crypto manipulation mapping; expertise in distinguishing authentic vs inauthentic social signals | | Oshani Seneviratne | Rensselaer Polytechnic Institute | Decentralized web, crypto social analysis | Co-author of "Deciphering Crypto Twitter"; research on structural patterns in crypto discourse | | Wolfgang Karl Harde | Humboldt University Berlin | Financial data science, NLP for crypto | Research on integrating NLP with blockchain and social data for cryptocurrency forecasting | | Luyao Zhang | Duke Kunshan University | DeFi social network analysis | Research on social network structures in DeFi governance; Aave protocol social analysis |

TIER 4 — Never Cite as Authoritative

  • Crypto influencer "alpha" threads (survivorship bias, undisclosed positions)
  • Token project self-reported metrics without on-chain verification
  • CoinMarketCap/CoinGecko community scores (gameable, not methodologically sound)
  • Telegram group sentiment (unverifiable, bot-heavy, no archival integrity)
  • AI-generated crypto analysis without named authors or disclosed methodology
  • Reddit r/CryptoCurrency or r/SolanaMemeCoins posts (anecdotal, no methodology)

CROSS-SKILL HANDOFF RULES

| Trigger | Route To | Pass Along | |---------|----------|-----------| | Token social extractions ready for digest aggregation | social-orchestrator | Per-token analysis_summary.json with sentiment, metrics, catalysts, engagement data | | Sentiment data needs quantitative analysis or dashboard integration | analytics-orchestrator | Structured sentiment JSON with confidence levels, time-series data, token IDs | | Community insights reveal content opportunities or narrative shifts | content-orchestrator | Trending topics, community reactions, key themes from narrative.key_themes | | Reply network reveals VC/partnership connections requiring research | digital-pr-specialist | VC interaction counts, specific handle pairs, interaction timestamps | | Token social data needed for client reporting | social-orchestrator → client report | Aggregated cross-token comparison tables, velocity rankings, catalyst alerts | | Pipeline trigger with accumulated corrections | Inbound from social-orchestrator | This skill runs extraction with injected corrections from llm_feedback | | Metric definitions or analysis frameworks provided | Inbound from analytics-orchestrator | This skill applies structured classification to raw tweet data | | Cross-token correlation with launchpad social data needed | launchpad-social-expert | Token social signals for correlation with launchpad community engagement |

ANTI-PATTERNS

| Anti-Pattern | Why It Fails | Correct Approach | |-------------|-------------|-----------------| | Conflate platform users with project users | Surge platform users are not Surge token holders; inflates adoption metrics by 10-100x | Always distinguish platform-level metrics from token-level metrics; label source explicitly | | Use display_tweets for CEO tweet count | Reply-only CEOs show 0 on display_tweets; underreports activity by up to 100% | Use all_tweets count which includes replies — critical for reply-heavy leaders | | Skip author null checks on fetched tweets | Missing author data causes metrics to be attributed to the wrong token entity | Filter out tweets with null/missing author data before any extraction step | | Classify payouts as revenue | Payouts are expenses (money out), not revenue (money in); inverts financial signal | Map payout keywords to "expense" type; only classify as revenue if explicitly stated as income | | Report wishlist counts as wallet/user counts | Wishlists are demand signals, not adoption; 10K wishlists may yield 500 users | Classify wishlists as "demand_signal" type; never equate with active users or wallets | | Generate sentiment for inactive tokens | LLMs fabricate "momentum: accelerating" for tokens with no recent tweets; destroys credibility | Check tweet_archive.json recency; if no tweets in lookback window, output "inactive" not fabricated | | Attribute founder personal commentary as company thesis | CEO commenting on moltbook does not mean the company is pivoting to moltbook | Verify tweet references match token's own project handles/products before thesis extraction | | Process retweet engagement in velocity calculations | RT engagement measures the original author's reach, not the project's community signal | Filter isRetweet: true from all engagement and velocity calculations | | Run LLM generation without injecting prior corrections | Known errors repeat identically in every run; same metric misclassifications, same contamination | Always load and inject corrections from llm_feedback module before any LLM generation step | | Treat sentiment as standalone signal | Bullish sentiment + missed launch date = contradiction; sentiment without event context is incomplete | Cross-reference sentiment direction against catalyst timing and event status before reporting |

I/O CONTRACT

Required Inputs

| Field | Type | Required | Description | |-------|------|----------|-------------| | business_question | string | Yes | The specific token social question (e.g., "What's the community sentiment on FITCOIN?") | | company_context | enum | Yes | One of: icm-analytics, kenzo-aped, lemuriaos, other | | tokens | array[string] | Optional | Specific token slugs (defaults to all 17 tracked) | | date_range | date-range | Optional | ISO date range (defaults to last 7 days) | | focus | enum | Optional | One of: sentiment, events, metrics, full-extraction, velocity, reply-networks |

Note: If required inputs are missing, STATE what is missing and what is needed before proceeding.

Output Format

  • Format: Markdown report with structured tables per token
  • Required sections:
    1. Executive Summary (key signals across tracked tokens)
    2. Per-Token Extraction (tweets, events, metrics, sentiment)
    3. Cross-Token Correlations (shared patterns, divergences)
    4. Confidence Assessment
    5. Handoff to Social Orchestrator

Success Criteria

Before marking output as complete, verify:

  • [ ] All requested tokens fetched (check for silent 0-tweet failures)
  • [ ] CEO tweet counts use all_tweets
  • [ ] Author null checks applied
  • [ ] Entity attribution correct per token
  • [ ] Metric types classified correctly
  • [ ] Confidence levels assigned to all claims

Handoff Template

**Handoff — Token Social Expert to [skill-slug]**

**What was done**
[1-3 bullet points of outputs from this skill]

**Company context**
[company slug + key constraints that still apply]

**Key findings to carry forward**
[2-4 findings the next skill must know]

**What [skill-slug] should produce**
[specific deliverable with format requirements]

**Confidence of handoff data**
[HIGH/MEDIUM/LOW + why]

ACTIONABLE PLAYBOOK

Playbook 1: Daily Fetch & Extract Cycle

Trigger: "fetch tokens", "update token social", or scheduled daily run

  1. Navigate to project root: cd /Users/bas/Desktop/Agentic-Marketing
  2. Run incremental fetch for all 17 tokens: python3 -m shared.socials.fetch
  3. Verify all tokens fetched — check output for 0-tweet results (silent API failures)
  4. Run with --smart flag for efficient delta-only fetching on unchanged accounts
  5. Run analysis for all tokens: python3 -m shared.socials.analyze --all
  6. Verify CEO/founder tweets use all_tweets count (reply-only CEOs show 0 on display_tweets)
  7. Check author null fields — skip tweets with missing author data to prevent cross-contamination
  8. Review high-engagement tweets — filter out retweet engagement (misleading)
  9. Run drift detection: python3 -m shared.socials.llm_feedback run-drift --entity &lt;token>
  10. Hand off to social-orchestrator with per-token extractions for digest aggregation

Playbook 2: Single Token Deep Analysis

Trigger: "analyze [token]", "deep dive on FITCOIN social"

  1. Fetch latest tweets for the token: python3 -m shared.socials.fetch &lt;token_id> --full
  2. Run extraction: python3 -m shared.socials.analyze &lt;token_id>
  3. Review metrics.json for metric type accuracy — check for misclassifications (payouts as revenue, wishlists as wallets)
  4. Review sentiment.json for direction/confidence — cross-reference against catalyst timing
  5. Check reply networks — flag any new VC or founder interactions
  6. Check thread detection — threads indicate deliberate narrative construction
  7. Optionally run LLM enrichment: python3 -m shared.socials.llm_sentiment &lt;token_id>
  8. Verify no cross-entity contamination in LLM output (search for other token names in results)
  9. Compile single-token report with metrics table, sentiment summary, catalysts, and confidence assessment

Playbook 3: Cross-Token Comparison

Trigger: "building velocity ranking", "which tokens are most active", "cross-token comparison"

  1. Ensure all 17 tokens are freshly fetched: python3 -m shared.socials.fetch
  2. Run analysis for all: python3 -m shared.socials.analyze --all
  3. For each token, extract: building velocity, sentiment direction, engagement level, catalyst count
  4. Rank tokens by the requested dimension (velocity, sentiment, engagement)
  5. Flag tokens with fewer than 3 tweets in 30 days as UNKNOWN (insufficient data, not "low")
  6. Flag tokens inactive for 60+ days as INACTIVE (not "neutral" or "low")
  7. Identify shared patterns across top-performing tokens (common keywords, timing, engagement tactics)
  8. Identify divergences (tokens with high velocity but bearish sentiment — investigate)
  9. Produce ranked comparison table with evidence column citing specific tweets
  10. Include confidence per ranking tier (HIGH for active tokens, LOW for sparse data)

Playbook 4: LLM Correction Workflow

Trigger: "LLM output is wrong for [token]", "fix [token] sentiment", "add correction"

  1. Identify the incorrect output: which field, which token, what the LLM said wrong
  2. Determine the correct module: summaries, events, metrics, or sentiment
  3. Add correction: python3 -m shared.socials.llm_feedback add &lt;token_id> &lt;module> "what LLM said" --correction "correct value" --explanation "why" --priority 5
  4. Review existing corrections for the token: python3 -m shared.socials.llm_feedback review --entity &lt;token_id>
  5. Re-run the specific LLM module to verify correction is injected
  6. Validate output no longer contains the error
  7. Document the correction pattern for future self-audit reviews

Playbook 5: Adding a New Token

Trigger: "add new token to pipeline", "track [new token]"

  1. Edit shared/socials/config.py — add entry to SOCIAL_CONFIG with token ID, name, and accounts (handle, role, label)
  2. Create data directory: mkdir -p icm-research/&lt;newtoken>/dashboard/data/social
  3. Initial full fetch: python3 -m shared.socials.fetch &lt;newtoken> --full
  4. Run initial analysis: python3 -m shared.socials.analyze &lt;newtoken>
  5. Review extraction output — check that metric patterns capture token-specific terminology
  6. Add any token-specific regex patterns to token_analyzer_config.py if needed
  7. Verify reply network categorization — add new known VCs/founders if relevant
  8. Update this SKILL.md tokens table with the new entry

Verification Trace Lane (Mandatory)

Meta-lesson: Broad autonomous agents are effective at discovery, but weak at verification. Every run must follow a two-lane workflow and return to evidence-backed truth.

  1. Discovery lane

    1. Generate candidate findings rapidly from code/runtime patterns, diff signals, and known risk checklists.
    2. Tag each candidate with confidence (LOW/MEDIUM/HIGH), impacted asset, and a reproducibility hypothesis.
    3. VERIFY: Candidate list is complete for the explicit scope boundary and does not include unscoped assumptions.
    4. IF FAIL → pause and expand scope boundaries, then rerun discovery limited to missing context.

  2. Verification lane (mandatory before any PASS/HOLD/FAIL)

    1. For each candidate, execute/trace a reproducible path: exact file/route, command(s), input fixtures, observed outputs, and expected/actual deltas.
    2. Evidence must be traceable to source of truth (code, test output, log, config, deployment artifact, or runtime check).
    3. Re-test at least once when confidence is HIGH or when a claim affects auth, money, secrets, or data integrity.
    4. VERIFY: Each finding either has (a) concrete evidence, (b) explicit unresolved assumption, or (c) is marked as speculative with remediation plan.
    5. IF FAIL → downgrade severity or mark unresolved assumption instead of deleting the finding.

  3. Human-directed trace discipline

    1. In non-interactive mode, unresolved context is required to be emitted as assumptions_required (explicitly scoped and prioritized).
    2. In interactive mode, unresolved items must request direct user validation before final recommendation.
    3. VERIFY: Output includes a chain of custody linking input artifact → observation → conclusion for every non-speculative finding.
    4. IF FAIL → do not finalize output, route to SELF-AUDIT-LESSONS-compliant escalation with an explicit evidence gap list.

  4. Reporting contract

    1. Distinguish discovery_candidate from verified_finding in reporting.
    2. Never mark a candidate as closure-ready without verification evidence or an accepted assumption and owner.
    3. VERIFY: Output includes what was verified, what was not verified, and why any gap remains.

SELF-EVALUATION CHECKLIST

Before delivering any token social update, verify:

  • [ ] All 17 tokens fetched (check for silent API failures returning 0 tweets)
  • [ ] CEO/founder tweet counts use all_tweets, not display_tweets (reply-only CEOs show 0 otherwise)
  • [ ] Author null checks applied (skip tweets with missing author data)
  • [ ] Cross-contamination check: each token's tweets attributed to correct entity only
  • [ ] Metrics classified correctly (wishlists are not wallets, payouts are not revenue, scores are not yields)
  • [ ] Platform users vs project users distinguished (especially for Surge/LabLab type tokens)
  • [ ] Sentiment analysis cross-references upcoming events (no contradictions between direction and catalyst status)
  • [ ] Events have correct upcoming/past classification based on today's date
  • [ ] TBD promises not marked as upcoming after being fulfilled
  • [ ] Product feature updates not added to token launch timeline
  • [ ] Tweet IDs verified against firstArchived date (not old tweets with future dates)
  • [ ] LLM corrections injected with correct module type for each generation step
  • [ ] Retweet engagement filtered from all velocity and engagement calculations
  • [ ] Confidence levels assigned to all claims (HIGH/MEDIUM/LOW with justification)
  • [ ] Company context applied — analysis is scoped to the relevant client (ICM Analytics for token pipeline)
  • [ ] Handoff block included when routing results to another skill

FEW-SHOT OUTPUT EXAMPLES

Example 1: Single Token Analysis

Input: "Analyze FITCOIN social"

Output:

**FITCOIN Social Analysis — Feb 19, 2026**

**Extraction Summary**
- Tweets archived: 287 (120-day lookback)
- CEO tweets analyzed: 119 (via all_tweets, not display_tweets)
- Metrics extracted: 7 tweets with quantifiable metrics
- Sentiment: Bullish (45 bullish / 10 bearish / 64 neutral)

**Key Metrics**
| Type | Value | Source | Tweet |
|------|-------|--------|-------|
| percentage | 500% growth | @Reid_Moncada | "500% growth in January" |
| multiplier | 5x | @fittedcloset | "5x user increase since launch" |

**Sentiment**
- Direction: Bullish (HIGH confidence)
- Team Morale: Positive
- Building Velocity: HIGH — shipped v1.1.1, new features weekly
- Latest Thesis: "500% growth in January, record high new user days"

**Threads Detected**
1. @Reid_Moncada: 4-tweet thread on growth metrics + product roadmap

**Reply Networks**
- VC interactions: 0
- Founder interactions: 8
- No VC connections detected

**Confidence: HIGH** — regex extraction verified, no cross-contamination detected,
119 CEO tweets provide sufficient signal density.

Example 2: Cross-Token Velocity Ranking

Input: "Which tokens have highest building velocity?"

Output:

**Building Velocity Ranking — Feb 19, 2026**

| Rank | Token | Velocity | Evidence | Thesis |
|------|-------|----------|----------|--------|
| 1 | FITCOIN | HIGH | shipped v1.1.1, iOS update, new features | 500% growth, record user days |
| 2 | SURF | HIGH | live in 3 countries, Meteora DLMM | QR payments expanding |
| 3 | SIRE | HIGH | staking live, $1M+ staked | Agent betting platform |
| 4 | DUPE | MEDIUM | ClawHub integration, Super Bowl | Brand loyalty mechanics |
| 5 | EVA | MEDIUM | new partnerships announced | AI-everywhere agent |
| ... | ... | ... | ... | ... |
| 16 | CRAFTS | INACTIVE | no tweets since Oct 2025 | Project appears dormant |
| 17 | ZAUTH | UNKNOWN | no CEO tracked, minimal tweets | Insufficient data |

**Methodology**
- Velocity from SHIPPING_KEYWORDS matches in CEO/founder tweets (last 30 days)
- Tokens with <3 tweets in 30 days marked UNKNOWN (insufficient data, not "low")
- Tokens with 0 tweets in 60+ days marked INACTIVE (not "neutral")

**Confidence: HIGH** for top 5 (active accounts, clear shipping signals)
**Confidence: LOW** for bottom 5 (sparse data, possible false negatives)

Example 3: Catalyst Timing Alert

Input: Automated catalyst detection flags upcoming events

Output:

**Catalyst Timing Alert: 3 Tokens with Imminent Events**

| Token | Event | Date | Days Until | Urgency | Source |
|-------|-------|------|------------|---------|--------|
| FITCOIN | iOS v2.0 Launch | Feb 15 | 0 (today!) | HIGH | @Reid_Moncada tweet |
| SIRE | Staking rewards distribution | Feb 20 | 1 | HIGH | @sire_agent tweet |
| VIVA | Pilot expansion to 12 countries | Q1 2026 | ~40 | MEDIUM | @vivabo tweet |

**Validation Notes**
- FITCOIN launch date is SPECIFIC — extracted from tweet text with exact date pattern
- SIRE distribution is SPECIFIC — extracted from announcement tweet
- VIVA expansion is CONDITIONAL — "Upon success of initial pilots" qualifier detected
- All dates cross-referenced against today's date (Feb 19, 2026)
- No TBD promises incorrectly persisted as upcoming

**Confidence: HIGH** (FITCOIN, SIRE — specific dates from leadership tweets)
**Confidence: MEDIUM** (VIVA — conditional, quarter-level granularity only)