[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EMZNQHBA9211MD90V7DY3J":3,"skill-same:01M7EMZNQHBA9211MD90V7DY3J":47},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7EMZNQHBA9211MD90V7DY3J","exoplanet-detection",null,"Finding exoplanets — transit and radial-velocity methods, light-curve vetting, and false-positive rejection.","TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-exoplanet-detection\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: exoplanet-detection\ndescription: Finding exoplanets — transit and radial-velocity methods, light-curve vetting, and false-positive rejection.\ncategory: scientific\n---\n\n## Overview\n\nExoplanets reveal themselves indirectly: tiny dips in starlight (transits)\nor tiny stellar wobbles (radial velocity). This skill covers both\ndetection methods end to end — from light curves and spectra to planet\nparameters — plus the false-positive vetting (eclipsing binaries,\nblends, stellar activity) that separates discoveries from retractions.\n\n## When to use\n\n- Searching light curves (TESS, Kepler, ground-based) for transit signals\n- Planning or interpreting radial-velocity follow-up of a candidate\n- Vetting a transit candidate: ruling out eclipsing binaries and blends\n- Deriving planet radius, mass, and orbital parameters from the data\n- Assessing a habitability claim critically\n\n## Core concepts\n\n- **Transit depth:** δ = (R_p\u002FR_★)² — a Jupiter around a Sun-like star gives ~1%; an Earth gives ~0.008% (80 ppm) — the signal scale sets the required photometric precision.\n- **Transit shape:** duration, ingress\u002Fegress slope, and flat bottom encode impact parameter and eccentricity; V-shaped transits scream grazing eclipsing binary.\n- **Radial velocity semi-amplitude:** K ∝ M_p sin i \u002F √(a M_★) — Jupiter at 1 AU around the Sun: ~12 m\u002Fs; Earth: ~9 cm\u002Fs — the instrumental frontier.\n- **The sin i degeneracy:** RV alone gives minimum mass (M sin i); only transits (or astrometry) break it to true mass.\n- **False positives:** background\u002Fforeground eclipsing binaries diluted in the aperture, hierarchical triples, stellar variability — each mimics transits; each has a diagnostic test.\n- **Validation vs confirmation:** statistical validation (vespa\u002FTRICERATOPS: planet hypothesis more likely than all false positives) vs dynamical confirmation (RV mass measurement) — know which a claim rests on.\n\n- **Transit-timing variations (TTVs):** gravitational tugs from unseen companions shift transit times — TTVs discover non-transiting planets and measure masses without radial velocity.\n- **Phase curves and secondary eclipses:** the planet's own light (reflected + thermal) varies with orbital phase; secondary-eclipse depth gives dayside temperature — atmospheric characterization without resolving the planet.\n- **Astrometric detection:** Gaia measures stellar wobbles on the sky — sensitive to long-period massive planets that transits and RV miss; the coming Gaia exoplanet catalog fills the outer-orbit gap.\n\n## Practical workflow\n\n### 1. Find transit signals\n\n1. Detrend the light curve (biweight filters, Gaussian processes) — preserving transit shapes; over-detrending erases shallow signals.\n2. Run Box Least Squares (BLS) over a period grid; inspect the top candidates phase-folded — by eye, always.\n3. Check the basics: odd\u002Feven transit depth consistency (eclipsing binaries often differ), secondary eclipse (stellar companion), transit duration vs stellar density (the photoeccentric check).\n\n### 2. Vet ruthlessly\n\n1. **Centroid test:** does the transit source coincide with the target star? Offset centroids = background blend.\n2. **Aperture test:** does depth change with aperture size? Dilution-dependent depth = contaminating eclipsing binary.\n3. **Color\u002Fodd-even:** depth varying with filter or between odd\u002Feven transits = binary.\n4. **High-resolution imaging:** adaptive optics\u002Fspeckle to find close companions diluting the light curve.\n5. **Spectroscopy:** single- vs double-lined spectra; bisector spans correlating with RV = stellar activity or blend, not a planet.\n\n### 3. Measure the planet\n\n1. Fit the transit (Mandel–Agol model) with MCMC: R_p\u002FR_★, impact parameter, limb darkening (constrain from stellar models, don't leave fully free), ephemeris.\n2. Get stellar parameters right first — planet radius inherits stellar radius uncertainty directly (spectroscopy + Gaia parallax + isochrones).\n3. RV follow-up: sample the orbit phase coverage fully; model stellar activity (GPs) jointly with the Keplerian — activity can fake or hide planets.\n\n### 4. Interpret habitability honestly\n\n1. Compute insolation and equilibrium temperature; the habitable zone is a necessary, not sufficient, condition.\n2. Radius alone doesn't give composition — the mass–radius diagram needs a measured mass; \"Earth-like\" from radius only is marketing.\n3. State what's actually measured (radius, minimum mass, insolation) vs inferred (composition, atmosphere, habitability).\n\n### 5. Plan a follow-up campaign for a new candidate\n\n1. Prioritize: ephemeris precision first (schedule transit observations before the window goes stale), then reconnaissance spectroscopy (is it a binary? what's the star?).\n2. Order observations by cost: photometric vetting (cheap) → high-resolution imaging (moderate) → precision RV (expensive) — kill false positives early.\n3. Set a decision point: define in advance what evidence promotes the candidate to \"planet\" vs demotes it — ad-hoc thresholds invite confirmation bias.\n\n### 6. Quick-reference checklist\n\n- [ ] Light curve detrended without erasing transit shapes\n- [ ] BLS candidates inspected phase-folded by eye\n- [ ] Odd\u002Feven depth consistency and secondary eclipse checked\n- [ ] Centroid and aperture tests run (blend diagnostics)\n- [ ] High-resolution imaging obtained for close companions\n- [ ] Stellar parameters (radius!) nailed before planet parameters\n- [ ] RV phase coverage complete; activity modeled jointly\n- [ ] \"Habitable\" claims restricted to what's actually measured\n\n## Common pitfalls\n\n- **BLS without eyeballs:** algorithms return the strongest periodic dip, which is often systematics or a binary — inspect phase folds.\n- **Ignoring dilution:** unresolved companions make transits shallower and planets smaller than reported — high-res imaging is part of the measurement.\n- **Activity blindness:** stellar spots and pulsations mimic both transits and RV signals — check activity indicators (Ca H&K, Hα, bisectors).\n- **Single-transit overclaiming:** one dip gives a period lower limit, not a period — don't publish orbits from single events.\n- **Eccentricity from under-sampled RV:** sparse RV fits inflate eccentricity — require good phase coverage or report upper limits.\n- **\"Habitable\" hype:** equilibrium temperature in the HZ ≠ habitable — atmosphere, water, magnetic field, and stellar activity are all unknown for most candidates.\n- **Ephemeris decay:** transit windows go stale as period uncertainty accumulates — a candidate unobserved for two years may need re-detection, not just scheduling.\n- **Stellar-radius errors propagating silently:** a 20% stellar-radius error is a 20% planet-radius error and a misclassified \"Earth-like\" — nail the star first, always.\n","## Overview\n\nExoplanets reveal themselves indirectly: tiny dips in starlight (transits)\nor tiny stellar wobbles (radial velocity). This skill covers both\ndetection methods end to end — from light curves and spectra to planet\nparameters — plus the false-positive vetting (eclipsing binaries,\nblends, stellar activity) that separates discoveries from retractions.\n\n## When to use\n\n- Searching light curves (TESS, Kepler, ground-based) for transit signals\n- Planning or interpreting radial-velocity follow-up of a candidate\n- Vetting a transit candidate: ruling out eclipsing binaries and blends\n- Deriving planet radius, mass, and orbital parameters from the data\n- Assessing a habitability claim critically\n\n## Core concepts\n\n- **Transit depth:** δ = (R_p\u002FR_★)² — a Jupiter around a Sun-like star gives ~1%; an Earth gives ~0.008% (80 ppm) — the signal scale sets the required photometric precision.\n- **Transit shape:** duration, ingress\u002Fegress slope, and flat bottom encode impact parameter and eccentricity; V-shaped transits scream grazing eclipsing binary.\n- **Radial velocity semi-amplitude:** K ∝ M_p sin i \u002F √(a M_★) — Jupiter at 1 AU around the Sun: ~12 m\u002Fs; Earth: ~9 cm\u002Fs — the instrumental frontier.\n- **The sin i degeneracy:** RV alone gives minimum mass (M sin i); only transits (or astrometry) break it to true mass.\n- **False positives:** background\u002Fforeground eclipsing binaries diluted in the aperture, hierarchical triples, stellar variability — each mimics transits; each has a diagnostic test.\n- **Validation vs confirmation:** statistical validation (vespa\u002FTRICERATOPS: planet hypothesis more likely than all false positives) vs dynamical confirmation (RV mass measurement) — know which a claim rests on.\n\n- **Transit-timing variations (TTVs):** gravitational tugs from unseen companions shift transit times — TTVs discover non-transiting planets and measure masses without radial velocity.\n- **Phase curves and secondary eclipses:** the planet's own light (reflected + thermal) varies with orbital phase; secondary-eclipse depth gives dayside temperature — atmospheric characterization without resolving the planet.\n- **Astrometric detection:** Gaia measures stellar wobbles on the sky — sensitive to long-period massive planets that transits and RV miss; the coming Gaia exoplanet catalog fills the outer-orbit gap.\n\n## Practical workflow\n\n### 1. Find transit signals\n\n1. Detrend the light curve (biweight filters, Gaussian processes) — preserving transit shapes; over-detrending erases shallow signals.\n2. Run Box Least Squares (BLS) over a period grid; inspect the top candidates phase-folded — by eye, always.\n3. Check the basics: odd\u002Feven transit depth consistency (eclipsing binaries often differ), secondary eclipse (stellar companion), transit duration vs stellar density (the photoeccentric check).\n\n### 2. Vet ruthlessly\n\n1. **Centroid test:** does the transit source coincide with the target star? Offset centroids = background blend.\n2. **Aperture test:** does depth change with aperture size? Dilution-dependent depth = contaminating eclipsing binary.\n3. **Color\u002Fodd-even:** depth varying with filter or between odd\u002Feven transits = binary.\n4. **High-resolution imaging:** adaptive optics\u002Fspeckle to find close companions diluting the light curve.\n5. **Spectroscopy:** single- vs double-lined spectra; bisector spans correlating with RV = stellar activity or blend, not a planet.\n\n### 3. Measure the planet\n\n1. Fit the transit (Mandel–Agol model) with MCMC: R_p\u002FR_★, impact parameter, limb darkening (constrain from stellar models, don't leave fully free), ephemeris.\n2. Get stellar parameters right first — planet radius inherits stellar radius uncertainty directly (spectroscopy + Gaia parallax + isochrones).\n3. RV follow-up: sample the orbit phase coverage fully; model stellar activity (GPs) jointly with the Keplerian — activity can fake or hide planets.\n\n### 4. Interpret habitability honestly\n\n1. Compute insolation and equilibrium temperature; the habitable zone is a necessary, not sufficient, condition.\n2. Radius alone doesn't give composition — the mass–radius diagram needs a measured mass; \"Earth-like\" from radius only is marketing.\n3. State what's actually measured (radius, minimum mass, insolation) vs inferred (composition, atmosphere, habitability).\n\n### 5. Plan a follow-up campaign for a new candidate\n\n1. Prioritize: ephemeris precision first (schedule transit observations before the window goes stale), then reconnaissance spectroscopy (is it a binary? what's the star?).\n2. Order observations by cost: photometric vetting (cheap) → high-resolution imaging (moderate) → precision RV (expensive) — kill false positives early.\n3. Set a decision point: define in advance what evidence promotes the candidate to \"planet\" vs demotes it — ad-hoc thresholds invite confirmation bias.\n\n### 6. Quick-reference checklist\n\n- [ ] Light curve detrended without erasing transit shapes\n- [ ] BLS candidates inspected phase-folded by eye\n- [ ] Odd\u002Feven depth consistency and secondary eclipse checked\n- [ ] Centroid and aperture tests run (blend diagnostics)\n- [ ] High-resolution imaging obtained for close companions\n- [ ] Stellar parameters (radius!) nailed before planet parameters\n- [ ] RV phase coverage complete; activity modeled jointly\n- [ ] \"Habitable\" claims restricted to what's actually measured\n\n## Common pitfalls\n\n- **BLS without eyeballs:** algorithms return the strongest periodic dip, which is often systematics or a binary — inspect phase folds.\n- **Ignoring dilution:** unresolved companions make transits shallower and planets smaller than reported — high-res imaging is part of the measurement.\n- **Activity blindness:** stellar spots and pulsations mimic both transits and RV signals — check activity indicators (Ca H&K, Hα, bisectors).\n- **Single-transit overclaiming:** one dip gives a period lower limit, not a period — don't publish orbits from single events.\n- **Eccentricity from under-sampled RV:** sparse RV fits inflate eccentricity — require good phase coverage or report upper limits.\n- **\"Habitable\" hype:** equilibrium temperature in the HZ ≠ habitable — atmosphere, water, magnetic field, and stellar activity are all unknown for most candidates.\n- **Ephemeris decay:** transit windows go stale as period uncertainty accumulates — a candidate unobserved for two years may need re-detection, not just scheduling.\n- **Stellar-radius errors propagating silently:** a 20% stellar-radius error is a 20% planet-radius error and a misclassified \"Earth-like\" — nail the star first, always.\n",{"name":5,"category":24,"description":7},"scientific","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-exoplanet-detection",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill exoplanet-detection",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill exoplanet-detection",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill exoplanet-detection","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-exoplanet-detection\u002FSKILL.md",true,[],[48,55,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]