mcpField
J
justin-sun-x-catalyst

justin-sun-x-catalyst

github.com/yan-labsOther267 installsUpdated 4w ago
Repository

About justin-sun-x-catalyst

A research skill for turning Justin Sun's public X posts into calibrated, short-horizon context on potentially affected crypto tokens and US-listed stocks. It requires fresh, verifiable posts and frames results as decision support, not trade recommendations or execution.

Key features

  1. 01Refresh and verify public X posts
  2. 02Map topics to related assets
  3. 03Calibrate signals with track records
  4. 04Report direction and reliability tier
  5. 05State duration and invalidation triggers
  6. 06Separate context from account truth

Use cases

  1. 01Assess possible market reactions to a post
  2. 02Compare a signal with historical hit rates
  3. 03Track catalysts with timestamps and links
  4. 04Review risks before manual trade planning

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/yan-labs/justin-sun-x-catalyst --skill justin-sun-x-catalyst

After installing, type/justin-sun-x-catalystin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

agents/
openai.yaml
references/
ecosystem-map.md
maintenance.md
methodology.md
track-record.md

Details

From the project README

Justin Sun X Catalyst

Overview

Use this lens to turn Justin Sun's public X posts into a calibrated list of tokens, crypto equities, and related US stocks that may react. Treat the output as short-horizon market context, not a thesis, recommendation, or live order.

Step 0 - Refresh First

Always refresh before analysis. X posts and crypto prices move quickly, and the local archive is only useful after it has been updated.

  1. Pull the latest yan-labs/justin-sun-x-catalyst repo or run python3 update.py from the repo root when maintaining the archive.
  2. Inspect the latest posts from https://x.com/justinsuntron or the refreshed data/justinsuntron_posts.json archive.
  3. Prefer xreach when its session is healthy. If it cannot authenticate, update.py parses exact status ids, text, and created_at_ms from the public x.com/justinsuntron profile HTML, then uses Jina public status pages only for profile rows it cannot parse. This fallback never reads browser cookies or login state.
  4. If the public fallback cannot establish a timestamp and permalink, try public search for from:justinsuntron plus the topic/ticker, then verify any quoted post against the X permalink.
  5. If fresh posts cannot be verified, say so plainly and analyze only the pasted post, screenshot, or user-provided link.
  6. Never call a post "latest" unless the timestamp and permalink were observed in the current run.

Core Workflow

  1. Load references/methodology.md for the tier system and per-post checklist.
  2. Load references/ecosystem-map.md to map the post topic into likely affected tokens, crypto equities, and US-listed names.
  3. Load references/track-record.md to weight the signal by observed base rate.
  4. Output each signal with timestamp, permalink, implicated asset(s), direction, reliability tier, expected duration, invalidation trigger, and data caveats.
  5. Keep broker/account language separate: public X and public market data are market context only, never uSMART account truth or fill confirmation.

Navigation

FileUse it for
references/methodology.mdClassify each post into catalyst tiers, amplifiers, anti-patterns, and output fields
references/ecosystem-map.mdTranslate topics into reaction baskets: TRON ecosystem, WLFI/TRUMP, WBTC, exchanges, crypto equities, Nasdaq TRON
references/track-record.mdSeed priors, live ledger template, and hit-rate calibration rules
references/maintenance.mdScheduled refresh, dedupe, scoring, source hygiene, and commit convention
../data/justinsuntron_posts.jsonRefreshed public X archive when using the full repo checkout

Risk Framing

  • State that the analysis is decision support only and not financial advice.
  • Flag Justin-linked assets as high manipulation/headline-risk instruments.
  • Separate "post can move price" from "asset is good to hold."
  • Prefer limit-order planning language if the user later discusses manual trades.
  • Never place, amend, cancel, or size trades from this skill.

Comments

Markdown supported