space-earth-science
Use when a task needs live space or geophysical data - "recent earthquakes near X / above magnitude Y", "NASA picture of the day", "near-Earth asteroids this week", or "latest full-disk Earth image". USGS FDSN is the default for quakes (no key, GeoJSON); NASA's APIs cover astronomy (DEMO_KEY works, free key is instant). Do NOT use for weather, storms, or air quality - use weather-climate instead; do NOT use for maps/geocoding - use geo-places instead; if the request is a vague "I need live data", route through public-data-api-picker.
- License 许可
- MIT
- 最近更新
- 2026-10-14
- Stars
- ★ 25
- Forks
- 3
01 前言 Front Matter
- name
- space-earth-science
- metadata
- { "title": "Space & Earth Science Data" }
- description
- Use when a task needs live space or geophysical data - "recent earthquakes near X / above magnitude Y", "NASA picture of the day", "near-Earth asteroids this week", or "latest full-disk Earth image". USGS FDSN is the default for quakes (no key, GeoJSON); NASA's APIs cover astronomy (DEMO_KEY works, free key is instant). Do NOT use for weather, storms, or air quality - use weather-climate instead; do NOT use for maps/geocoding - use geo-places instead; if the request is a vague "I need live data", route through public-data-api-picker.
03 SKILL.md 正文
Space & Earth Science Data
Fetch earthquakes and NASA astronomy data with verified endpoints. The mistakes this prevents: trusting community space APIs from training memory - the SpaceX API (api.spacexdata.com) and the popular ISS-position endpoints fail TLS or time out, verified - and burning NASA's shared DEMO_KEY quota mid-task.
Ranked APIs
- USGS Earthquake FDSN (earthquake.usgs.gov) - DEFAULT for anything seismic. Global catalog, rich filtering, GeoJSON, no key, fast.
- NASA APIs (api.nasa.gov) - APOD (picture of the day), NeoWs (near-Earth objects).
DEMO_KEYworks but is shared per-IP (~10-30 req/hr); a real key is a 30-second instant email signup at api.nasa.gov and lifts it to 1,000 req/hr. UseDEMO_KEYfor one-off calls only. - NASA EPIC mirror (epic.gsfc.nasa.gov) - full-disk Earth imagery, no key at all on this host. Prefer it over the api.nasa.gov EPIC route, which spends key quota for identical data.
Procedure
- Quakes: filter server-side. Time, magnitude, radius, and sort all belong in the query string - never fetch the whole feed and filter locally (templates below).
- NASA: budget the key. One-off →
DEMO_KEY. Anything in a loop, cron, or shipped app → tell the user to grab the instant free key and read theX-RateLimit-Remainingheader. A 429 here means quota, not outage - the fix is a key, not a retry. - Convert epoch times. USGS
timeis milliseconds since epoch; NASA dates areYYYY-MM-DDstrings. Report human-readable UTC.
Ask the user only if missing - quakes: region (default: global), min magnitude (default: 4.5), window (default: past 7 days). NASA: date (default: today).
URL templates + real response shapes
Earthquakes:
https://earthquake.usgs.gov/fdsnws/event/1/query?format=geojson
&starttime={YYYY-MM-DD}&endtime={YYYY-MM-DD}&minmagnitude=5
&latitude=35.6&longitude=139.7&maxradiuskm=500 ← optional region circle
&orderby=magnitude&limit=20
{"features":[{"properties":{"mag":6.2,"place":"58 km W of Tobelo, Indonesia",
"time":1783045888846,"tsunami":0,"alert":"green","felt":7,
"url":"https://earthquake.usgs.gov/earthquakes/eventpage/us6000t9r5"},
"geometry":{"coordinates":[127.63,1.73,10.0]}}],
"metadata":{"count":1}}
Gotchas: geometry.coordinates is [lon, lat, depth-km] - longitude first. orderby=time is newest-first. alert (PAGER: green/yellow/orange/red) and tsunami are the impact fields worth surfacing. Hard cap 20,000 events per query - page with offset (1-based) if you hit it.
NASA APOD (note: this endpoint often takes 2-10s - set a generous timeout):
https://api.nasa.gov/planetary/apod?api_key={KEY}&date={YYYY-MM-DD}
{"date":"...","title":"...","explanation":"...","media_type":"image",
"url":"https://apod.nasa.gov/apod/image/...jpg","hdurl":"..."}
Check media_type - on video days url is a YouTube embed, not an image.
Near-Earth asteroids:
https://api.nasa.gov/neo/rest/v1/feed?start_date={YYYY-MM-DD}&end_date={YYYY-MM-DD}&api_key={KEY}
Max 7-day window per call (400 above that). Shape: element_count, then near_earth_objects keyed by date, each object with name, is_potentially_hazardous_asteroid, estimated_diameter.meters.estimated_diameter_max, and close_approach_data[0].miss_distance.kilometers (a string - parse it).
Full-disk Earth image (keyless mirror):
https://epic.gsfc.nasa.gov/api/natural ← latest image list
https://epic.gsfc.nasa.gov/archive/natural/{yyyy}/{mm}/{dd}/png/{image}.png
List items carry image (basename) and date; split the date into the {yyyy}/{mm}/{dd} path parts and append {image}.png.
Deliverable
The fetched events/objects with human-readable UTC times, magnitudes/diameters with units, impact fields (alert, tsunami, hazardous flags) surfaced, and the exact URL used.
Do NOT use - reach for X instead
- SpaceX API (api.spacexdata.com) - fails TLS (HTTP 525), verified; the project is archived. Don't cite it as a data source.
- ISS position (api.open-notify.org / wheretheiss.at) - HTTP-only and timing out respectively, verified. No keyless ISS tracker ships in this pack; say so rather than pointing at a dead endpoint.
- Weather, storms, air quality - weather-climate (the USGS/NASA slot is rocks and space, not atmosphere).
- "Where is this quake's city?" enrichment - geo-places for reverse geocoding beyond the
placestring USGS already gives you.
Quality bar
- USGS filters ran server-side; no full-catalog downloads.
- Epoch milliseconds became UTC datetimes;
[lon, lat]order was respected. - Any loop against api.nasa.gov uses a real key, never
DEMO_KEY.
Sourced and liveness-verified from the public-apis project (MIT).
04 同仓库更多 Skills
有氧运动计划
zone-2-cardio-plan
当有人要求制定稳态有氧训练计划、进行有氧基础训练或达到第二区间、安排轻松或耐力型的每周有氧训练、按心率区间训练,或提高静息心率、最大摄氧量或耐力时,可以使用此方案。该方案构建了一个包含训练计划结构、训练方式选择和进度安排的心率区间有氧训练模块。本方案仅提供一般健身指导,不构成医疗建议。请勿用于设计力量或举重训练计划(请使用力量训练计划)、高强度间歇训练 (HIIT) 或循环训练(请使用体能训练和 HIIT 计划),或灵活性/柔韧性训练(请使用灵活性训练计划)。
youtube-script-writer
Writes retention-engineered long-form YouTube scripts on a hook/body/payoff architecture - a first-30-seconds hook that survives the retention cliff, a beat-sheet body with mini-hooks and bridges, timed pattern interrupts, and a payoff that over-delivers - with B-roll and editing cues marked inline. Use when someone says "script my next video", "my retention graph dies at the start", "tighten this draft", or "outline a video on X". Do NOT use for the 3-second opener of TikTok, Reels, or Shorts - use video-hook-writer instead; do NOT use for spoken voiceover synced to on-screen tutorial actions - use narration-script instead; do NOT use for a sales demo built on a buyer's discovery notes - use demo-script instead; do NOT use to design the thumbnail and title - use thumbnail-concept instead.
win-back-campaign
Designs segmented win-back email sequences for dormant users - dormancy tiers, a three-beat sequence with a single proportional incentive, and a suppression rule - and measures success by re-activation, not opens. Use when someone says "our users went quiet", "design a win-back campaign", "how do I re-engage lapsed customers", "should we email people who haven't logged in for months", or lifecycle messaging has stopped landing with a lapsed segment. Do NOT use for recovering an unfinished checkout - use abandoned-cart-sequence instead. Do NOT use for diagnosing and fixing why active customers cancel - use churn-reduction instead. Do NOT use for building always-on onboarding or nurture flows - use email-drip-builder instead.
wikipedia-style
Writes neutral, verifiable, encyclopedic prose following Wikipedia's core content policies and manual of style - NPOV, inline citations, notability-backed claims, and a strict ban on promotional language. Use when someone asks "write this like a Wikipedia article", "draft a Wikipedia page for this company or person", "make this neutral and encyclopedic", or "why does my article draft keep getting rejected". Do NOT use for persuasive or opinion writing - use op-ed-writer instead; for thesis-driven academic papers, use academic-essay; for verifying claims in existing text, use fact-checker.
whitepapers
Structures and writes authoritative B2B whitepapers - a standalone executive summary, a data-sized problem statement, methodology, evidence-driven findings, recommendations, and a soft call to action - flagging every claim that needs a real citation. Use when a marketer asks "write a whitepaper on this topic", "turn our research into a lead-gen asset", "make this credible enough for executives", or a draft reads like a product pitch instead of analysis. Do NOT use for customer-story-driven proof - use case-study-builder instead; for policy audiences, use policy-brief.
white-space-analysis
Finds unmet market gaps by ranking jobs-to-be-done on importance versus satisfaction, overlaying them against current solutions and workarounds, and validating that each gap is real, winnable, and worth winning. Use when someone asks "where are the gaps in this market", "what's underserved here", "where should we play next", or is hunting for product, feature, or market-entry opportunities. Do NOT use for profiling competitors and building battle cards - use competitive-intelligence instead; for putting a dollar figure on an identified opportunity - use market-sizing instead; for extracting jobs-to-be-done from raw customer interviews - use jtbd-extractor instead.