Daily investor-grade SpaceX / SPCX briefing for Grok & Claude agents. Live X + web search, price-moving lens, anti-fabrication. Not financial advice.
SaferSkills independently audited spacex-daily-briefing (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Produce one tight, investor-grade daily briefing on SpaceX / SPCX. The reader is a shareholder who wants the price-moving signal first and the strategic context second. Bias every choice toward "what could move SPCX or change the thesis in the next few days," not encyclopedic completeness.
This skill works in Grok Build (native X Search + Web Search) and in any Claude-compatible agent. It is designed to be run once a day — as a slash command (/spacex-daily-briefing) or headlessly on a schedule (see Daily automation).
Quick start: drop this folder in ~/.grok/skills/, then run /spacex-daily-briefing (or grok -p "/spacex-daily-briefing"). The first run reads references/ for the source list, live query set, and entity map.
Since the February 2026 SpaceX × xAI merger, the SPCX-listed company contains more than rockets. Track all of it, weighted by stock impact:
Full source list, the entity map with as-of figures, and the live query set live in references/sources-and-queries.md — read it at the start of each run.
In Grok Build, map each task to the native tool — these are the real tool names:
web_search — news, the live SPCX quote, YouTube fallback. Pass a focused query; favor recent results.browse_page — optional, background only (spacex.com, Wikipedia) with a tight summarizer instruction. Not reliable for live numbers and can error on JS/rate-limited pages — don't depend on it; if it fails, skip and use web_search.x_keyword_search — the daily X scrape. Supports mode="Latest", limit, and operators (since:, min_faves:, from:, filter:has_engagement).x_semantic_search — meaning-based X pass for sentiment/themes; supports from_date.render_inline_citation — attach a source to a specific claim.`web_search` is the workhorse — prefer it for the quote, news, YouTube, and Kalshi. Per-page fetchers (browse_page, or a WebFetch tool if the host exposes one) often fail on JS-heavy or rate-limited pages. A failed fetch or tool error is never fatal: skip that source, mark the affected item unverified this run, and keep going. Always produce the brief from whatever succeeded — never abort or stall because a page wouldn't load. If fetches keep failing, lean entirely on web_search + the X tools and note the gap in the brief.
In a non-Grok (Claude-compatible) agent, substitute your web search for web_search/browse_page and search x.com via the web for the X passes.
Do these in order. Fire independent searches in parallel where the tool allows.
./briefs/. If one exists, your job is the delta since then — surface what's new, don't re-report yesterday. If none exists, use a rolling 48-hour window.
web_search (e.g. query="SPCX stock price today",query="SPCX analyst price target OR rating"). Capture latest price, daily % move, volume, market cap / implied valuation, and any analyst initiations or rating changes. Anchor to the verified IPO facts in the reference file ($135 IPO price, ~$161 first-day close, ~$1.77T implied valuation) — and treat round numbers like "$2T" or a specific Musk stake % as claims to verify, not facts. Only state numbers you sourced this run. A stale or invented quote is worse than "last confirmed close $X as of <date>; intraday unverified." browse_page on a JS quote page is fine for context, but don't trust a hard number it can't cleanly parse — corroborate with a finance source or mark it unconfirmed. Also scan prediction-market odds (Kalshi — kalshi.com/search?q=spacex) for a forward-looking read on near-term SpaceX/Starship/SPCX events; report these as market-implied probabilities, not fact.
x_keyword_search (mode="Latest"). Run the query set in the reference file (#SpaceX, #SpaceXIPO, $SPCX, "SPCX stock", Starship/Starlink terms) plus a second pass from:elonmusk scoped to the company. Add since:<yesterday> and a min_faves: floor to stay fresh and signal-rich; optionally add an x_semantic_search pass for sentiment/themes. Capture: net sentiment, the 2–3 most viral or consequential posts (handles + links), and any breaking chatter not yet in mainstream news — labeled unconfirmed until corroborated.
web_search for SpaceX / Starlink / Starship / Starshield / xAI / Xdevelopments in the window: contracts and awards, launches and anomalies, earnings or revenue leaks, regulatory (FCC/FAA/SEC) actions, lockup / quiet-period milestones, index-inclusion talk, governance news.
#SpaceXIPO, #SpaceX,#ElonMusk, #nasdaq); if the hashtag page is thin, web_search with query="SpaceX IPO OR SPCX site:youtube.com". List a handful with title, channel, and link. You're surfacing what's circulating — don't invent view counts.
Fill assets/brief-template.md. Structure, in order:
[source] where the claim appears; do not append a long categorized sources list (it bloats the brief). At most one short line of the 3–5 key links at the very end. Citations must support the brief, not dominate it.Keep it tight: the headline + TL;DR must stand alone, and the whole brief should read in ~2 minutes (aim for roughly one screen plus the metrics table). Cut anything that isn't price-moving — depth lives in the linked sources, not in the prose. Don't restate the same fact across TL;DR, what-moved, and segments.
Investor decisions ride on this output, so accuracy beats completeness every time.
contracts, and valuations must come from this run's searches.
today. If you can't source it, say so explicitly rather than guessing.
a viral post become a stated fact.
window so the reader knows how fresh it is.
SPCX. Note this neutrally where xAI/Grok items appear; report them straight.
the investor decide — no buy/sell calls.
This skill is built to repeat. Two ways to run it daily:
/spacex-daily-briefing.grok -p "/spacex-daily-briefing" --output-format text > briefs/$(date +%F).mdwired to cron or a CI schedule. Writing each brief into ./briefs/ is what lets the next run compute the delta since yesterday (step 1). Create that folder if missing.
references/sources-and-queries.md — canonical sources, the live X/YouTube query set, the entity map with as-of figures, the daily key-metrics checklist, and dated catalysts to verify. Read at the start of every run.references/grok-tool-calls.md — exact, copy-ready Grok tool-call syntax (browse_page, web_search, x_keyword_search, x_semantic_search).assets/brief-template.md — the fill-in tiered template.web_search is the primary web tool; per-page fetch (browse_page/WebFetch) is optional and a failed fetch/tool error is non-fatal (skip + mark unverified, never abort the brief).$SPCX cashtag + higher engagement floor, SEC EDGAR (8-K / Form 4 / lockup) watch.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.