[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M751TRR5CFP7YK6VBHRXK2D6":3,"skill-same:01M751TRR5CFP7YK6VBHRXK2D6":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":31,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M751TRR5CFP7YK6VBHRXK2D6","space-earth-science",null,"Use when a task needs live space or geophysical data - \"recent earthquakes near X \u002F 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\u002Fgeocoding - use geo-places instead; if the request is a vague \"I need live data\", route through public-data-api-picker.","SkillMedev\u002Fskills","SkillMedev","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F298078254?v=4","01M74ZSGTQ918CB0VXW4EG3RMX","SkillMe","01M74ZSGVBT497NA95CBT8JTY4",25,"MIT","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fspace-earth-science\u002FSKILL.md",[],[],"2026-11-11 18:22:23",false,"---\nname: space-earth-science\ndescription: Use when a task needs live space or geophysical data - \"recent earthquakes near X \u002F 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\u002Fgeocoding - use geo-places instead; if the request is a vague \"I need live data\", route through public-data-api-picker.\nmetadata:\n  title: \"Space & Earth Science Data\"\n---\n\n# Space & Earth Science Data\n\nFetch 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.\n\n## Ranked APIs\n\n1. **USGS Earthquake FDSN** (earthquake.usgs.gov) - DEFAULT for anything seismic. Global catalog, rich filtering, GeoJSON, no key, fast.\n2. **NASA APIs** (api.nasa.gov) - APOD (picture of the day), NeoWs (near-Earth objects). `DEMO_KEY` works but is shared per-IP (~10-30 req\u002Fhr); a real key is a 30-second instant email signup at api.nasa.gov and lifts it to 1,000 req\u002Fhr. Use `DEMO_KEY` for one-off calls only.\n3. **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.\n\n## Procedure\n\n1. **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).\n2. **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 the `X-RateLimit-Remaining` header. A 429 here means quota, not outage - the fix is a key, not a retry.\n3. **Convert epoch times.** USGS `time` is **milliseconds** since epoch; NASA dates are `YYYY-MM-DD` strings. Report human-readable UTC.\n\nAsk the user only if missing - quakes: region (default: global), min magnitude (default: 4.5), window (default: past 7 days). NASA: date (default: today).\n\n## URL templates + real response shapes\n\n**Earthquakes:**\n\n```\nhttps:\u002F\u002Fearthquake.usgs.gov\u002Ffdsnws\u002Fevent\u002F1\u002Fquery?format=geojson\n  &starttime={YYYY-MM-DD}&endtime={YYYY-MM-DD}&minmagnitude=5\n  &latitude=35.6&longitude=139.7&maxradiuskm=500        ← optional region circle\n  &orderby=magnitude&limit=20\n```\n\n```json\n{\"features\":[{\"properties\":{\"mag\":6.2,\"place\":\"58 km W of Tobelo, Indonesia\",\n   \"time\":1783045888846,\"tsunami\":0,\"alert\":\"green\",\"felt\":7,\n   \"url\":\"https:\u002F\u002Fearthquake.usgs.gov\u002Fearthquakes\u002Feventpage\u002Fus6000t9r5\"},\n  \"geometry\":{\"coordinates\":[127.63,1.73,10.0]}}],\n \"metadata\":{\"count\":1}}\n```\n\nGotchas: `geometry.coordinates` is `[lon, lat, depth-km]` - longitude first. `orderby=time` is newest-first. `alert` (PAGER: green\u002Fyellow\u002Forange\u002Fred) and `tsunami` are the impact fields worth surfacing. Hard cap 20,000 events per query - page with `offset` (1-based) if you hit it.\n\n**NASA APOD** (note: this endpoint often takes 2-10s - set a generous timeout):\n\n```\nhttps:\u002F\u002Fapi.nasa.gov\u002Fplanetary\u002Fapod?api_key={KEY}&date={YYYY-MM-DD}\n```\n\n```json\n{\"date\":\"...\",\"title\":\"...\",\"explanation\":\"...\",\"media_type\":\"image\",\n \"url\":\"https:\u002F\u002Fapod.nasa.gov\u002Fapod\u002Fimage\u002F...jpg\",\"hdurl\":\"...\"}\n```\n\nCheck `media_type` - on video days `url` is a YouTube embed, not an image.\n\n**Near-Earth asteroids:**\n\n```\nhttps:\u002F\u002Fapi.nasa.gov\u002Fneo\u002Frest\u002Fv1\u002Ffeed?start_date={YYYY-MM-DD}&end_date={YYYY-MM-DD}&api_key={KEY}\n```\n\nMax 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).\n\n**Full-disk Earth image (keyless mirror):**\n\n```\nhttps:\u002F\u002Fepic.gsfc.nasa.gov\u002Fapi\u002Fnatural                       ← latest image list\nhttps:\u002F\u002Fepic.gsfc.nasa.gov\u002Farchive\u002Fnatural\u002F{yyyy}\u002F{mm}\u002F{dd}\u002Fpng\u002F{image}.png\n```\n\nList items carry `image` (basename) and `date`; split the date into the `{yyyy}\u002F{mm}\u002F{dd}` path parts and append `{image}.png`.\n\n## Deliverable\n\nThe fetched events\u002Fobjects with human-readable UTC times, magnitudes\u002Fdiameters with units, impact fields (alert, tsunami, hazardous flags) surfaced, and the exact URL used.\n\n## Do NOT use - reach for X instead\n\n- **SpaceX API (api.spacexdata.com)** - fails TLS (HTTP 525), verified; the project is archived. Don't cite it as a data source.\n- **ISS position (api.open-notify.org \u002F 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.\n- **Weather, storms, air quality** - weather-climate (the USGS\u002FNASA slot is rocks and space, not atmosphere).\n- **\"Where is this quake's city?\"** enrichment - geo-places for reverse geocoding beyond the `place` string USGS already gives you.\n\n## Quality bar\n\n- USGS filters ran server-side; no full-catalog downloads.\n- Epoch milliseconds became UTC datetimes; `[lon, lat]` order was respected.\n- Any loop against api.nasa.gov uses a real key, never `DEMO_KEY`.\n\nSourced and liveness-verified from the public-apis project (MIT).\n","# Space & Earth Science Data\n\nFetch 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.\n\n## Ranked APIs\n\n1. **USGS Earthquake FDSN** (earthquake.usgs.gov) - DEFAULT for anything seismic. Global catalog, rich filtering, GeoJSON, no key, fast.\n2. **NASA APIs** (api.nasa.gov) - APOD (picture of the day), NeoWs (near-Earth objects). `DEMO_KEY` works but is shared per-IP (~10-30 req\u002Fhr); a real key is a 30-second instant email signup at api.nasa.gov and lifts it to 1,000 req\u002Fhr. Use `DEMO_KEY` for one-off calls only.\n3. **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.\n\n## Procedure\n\n1. **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).\n2. **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 the `X-RateLimit-Remaining` header. A 429 here means quota, not outage - the fix is a key, not a retry.\n3. **Convert epoch times.** USGS `time` is **milliseconds** since epoch; NASA dates are `YYYY-MM-DD` strings. Report human-readable UTC.\n\nAsk the user only if missing - quakes: region (default: global), min magnitude (default: 4.5), window (default: past 7 days). NASA: date (default: today).\n\n## URL templates + real response shapes\n\n**Earthquakes:**\n\n```\nhttps:\u002F\u002Fearthquake.usgs.gov\u002Ffdsnws\u002Fevent\u002F1\u002Fquery?format=geojson\n  &starttime={YYYY-MM-DD}&endtime={YYYY-MM-DD}&minmagnitude=5\n  &latitude=35.6&longitude=139.7&maxradiuskm=500        ← optional region circle\n  &orderby=magnitude&limit=20\n```\n\n```json\n{\"features\":[{\"properties\":{\"mag\":6.2,\"place\":\"58 km W of Tobelo, Indonesia\",\n   \"time\":1783045888846,\"tsunami\":0,\"alert\":\"green\",\"felt\":7,\n   \"url\":\"https:\u002F\u002Fearthquake.usgs.gov\u002Fearthquakes\u002Feventpage\u002Fus6000t9r5\"},\n  \"geometry\":{\"coordinates\":[127.63,1.73,10.0]}}],\n \"metadata\":{\"count\":1}}\n```\n\nGotchas: `geometry.coordinates` is `[lon, lat, depth-km]` - longitude first. `orderby=time` is newest-first. `alert` (PAGER: green\u002Fyellow\u002Forange\u002Fred) and `tsunami` are the impact fields worth surfacing. Hard cap 20,000 events per query - page with `offset` (1-based) if you hit it.\n\n**NASA APOD** (note: this endpoint often takes 2-10s - set a generous timeout):\n\n```\nhttps:\u002F\u002Fapi.nasa.gov\u002Fplanetary\u002Fapod?api_key={KEY}&date={YYYY-MM-DD}\n```\n\n```json\n{\"date\":\"...\",\"title\":\"...\",\"explanation\":\"...\",\"media_type\":\"image\",\n \"url\":\"https:\u002F\u002Fapod.nasa.gov\u002Fapod\u002Fimage\u002F...jpg\",\"hdurl\":\"...\"}\n```\n\nCheck `media_type` - on video days `url` is a YouTube embed, not an image.\n\n**Near-Earth asteroids:**\n\n```\nhttps:\u002F\u002Fapi.nasa.gov\u002Fneo\u002Frest\u002Fv1\u002Ffeed?start_date={YYYY-MM-DD}&end_date={YYYY-MM-DD}&api_key={KEY}\n```\n\nMax 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).\n\n**Full-disk Earth image (keyless mirror):**\n\n```\nhttps:\u002F\u002Fepic.gsfc.nasa.gov\u002Fapi\u002Fnatural                       ← latest image list\nhttps:\u002F\u002Fepic.gsfc.nasa.gov\u002Farchive\u002Fnatural\u002F{yyyy}\u002F{mm}\u002F{dd}\u002Fpng\u002F{image}.png\n```\n\nList items carry `image` (basename) and `date`; split the date into the `{yyyy}\u002F{mm}\u002F{dd}` path parts and append `{image}.png`.\n\n## Deliverable\n\nThe fetched events\u002Fobjects with human-readable UTC times, magnitudes\u002Fdiameters with units, impact fields (alert, tsunami, hazardous flags) surfaced, and the exact URL used.\n\n## Do NOT use - reach for X instead\n\n- **SpaceX API (api.spacexdata.com)** - fails TLS (HTTP 525), verified; the project is archived. Don't cite it as a data source.\n- **ISS position (api.open-notify.org \u002F 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.\n- **Weather, storms, air quality** - weather-climate (the USGS\u002FNASA slot is rocks and space, not atmosphere).\n- **\"Where is this quake's city?\"** enrichment - geo-places for reverse geocoding beyond the `place` string USGS already gives you.\n\n## Quality bar\n\n- USGS filters ran server-side; no full-catalog downloads.\n- Epoch milliseconds became UTC datetimes; `[lon, lat]` order was respected.\n- Any loop against api.nasa.gov uses a real key, never `DEMO_KEY`.\n\nSourced and liveness-verified from the public-apis project (MIT).\n",{"name":5,"metadata":24,"description":7},{"title":25},"Space & Earth Science Data","main","97a13607d669157a4a16d5ba79b77f208319f7b9","skills\u002Fspace-earth-science",3,"https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills","https:\u002F\u002Fskillme.dev","https:\u002F\u002Fgithub.com\u002FSkillMedev","MCP-native catalog of Claude Agent Skills. Browse, recommend, install, and auto-apply skills in chat. Open source, every skill free and clonable on GitHub.","2026-10-14 03:19:31",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add SkillMedev\u002Fskills --skill space-earth-science",{"tool":41,"command":42},"bunx","bunx skills add SkillMedev\u002Fskills --skill space-earth-science",{"tool":44,"command":45},"pnpm","pnpm dlx skills add SkillMedev\u002Fskills --skill space-earth-science","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fspace-earth-science\u002FSKILL.md",true,[],[50,60,67,74,81,88],{"skillNo":51,"name":52,"nameZh":53,"description":54,"descriptionZh":55,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":59},"01M75271B256DF3FX2VG5VRYEE","zone-2-cardio-plan","有氧运动计划","Use when someone asks to build a steady-state cardio plan, train an aerobic base or Zone 2, structure easy or endurance weekly cardio, train by heart-rate zones, or improve resting heart rate, VO2, or endurance. Builds a heart-rate-zone aerobic training block with session structure, modality choice, and progression. General fitness guidance, not medical advice. Do NOT use to design a strength or lifting program (use Strength Training Plan), high-intensity interval conditioning, HIIT, or circuits (use Conditioning & HIIT Program), or a mobility\u002Fflexibility routine (use Mobility Routine).","当有人要求制定稳态有氧训练计划、进行有氧基础训练或达到第二区间、安排轻松或耐力型的每周有氧训练、按心率区间训练，或提高静息心率、最大摄氧量或耐力时，可以使用此方案。该方案构建了一个包含训练计划结构、训练方式选择和进度安排的心率区间有氧训练模块。本方案仅提供一般健身指导，不构成医疗建议。请勿用于设计力量或举重训练计划（请使用力量训练计划）、高强度间歇训练 (HIIT) 或循环训练（请使用体能训练和 HIIT 计划），或灵活性\u002F柔韧性训练（请使用灵活性训练计划）。","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzone-2-cardio-plan\u002FSKILL.md",[],[],"2026-11-11 18:27:18",{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":59},"01M7526VP1QBBKYBE17S1WR86Y","youtube-script-writer","Writes retention-engineered long-form YouTube scripts on a hook\u002Fbody\u002Fpayoff 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.","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-script-writer\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":59},"01M7526P2T0WKMHDXS4Q58237T","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.","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwin-back-campaign\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":59},"01M7526HF2RCDJ50P93WRZRHVV","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.","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwikipedia-style\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":59},"01M7526D43CTGRKGKNQ2GB0KVX","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.","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwhitepapers\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":59},"01M75268423Y3K50SY5WC2NX2G","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.","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwhite-space-analysis\u002FSKILL.md",[],[]]