SkillAgentSearch skills...

light-curve-preprocessing

Preprocessing and cleaning techniques for astronomical light curves

Install / Use

npx skills add benchflow-ai/skillsbench --skill light-curve-preprocessing

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

82/100

Supported Platforms

Universal

Tags

Our assessment of light-curve-preprocessing

light-curve-preprocessing scores 82/100 on our quality scale, 3259th of 4,700 Development & Engineering skills we index.

Its SKILL.md is 5.4 KB long, well organised into 37 sections with 8 code examples: a solid amount of guidance for an agent.

With 1,813 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
20/20
Description
12/15
Adoption
14/20
Freshness
11/15

Maintenance, license and trust

  • The repository was last updated about 4 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.
  • Our last check on 2026-11-07 found the source still online.
  • It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 98/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-01. Automated pattern scan on 2026-10-01. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

light-curve-preprocessing compared with similar skills

All 4 of these similar skills score higher than light-curve-preprocessing; compare them before choosing.

SkillScoreStarsUpdatedFormat
light-curve-preprocessing (this skill)by benchflow-ai821.8k4mo agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.1ktodayCLAUDE.md
claude-howtoby luongnv8910047.3k2d agoCLAUDE.md
lobehubby lobehub10085.6ktodayMCP Server

Frequently asked questions

How do I install light-curve-preprocessing?
Run npx skills add benchflow-ai/skillsbench --skill light-curve-preprocessing. The install tabs above show the steps for each supported agent.
Which AI agents does light-curve-preprocessing work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is light-curve-preprocessing safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 98/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is light-curve-preprocessing still maintained?
The repository was last updated about 4 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.

name: light-curve-preprocessing description: Preprocessing and cleaning techniques for astronomical light curves. Use when preparing light curve data for period analysis, including outlier removal, trend removal, flattening, and handling data quality flags. Works with lightkurve and general time series data.

Light Curve Preprocessing

Preprocessing is essential before period analysis. Raw light curves often contain outliers, long-term trends, and instrumental effects that can mask or create false periodic signals.

Overview

Common preprocessing steps:

  1. Remove outliers
  2. Remove long-term trends
  3. Handle data quality flags
  4. Remove stellar variability (optional)

Outlier Removal

Using Lightkurve

import lightkurve as lk

# Remove outliers using sigma clipping
lc_clean, mask = lc.remove_outliers(sigma=3, return_mask=True)
outliers = lc[mask]  # Points that were removed

# Common sigma values:
# sigma=3: Standard (removes ~0.3% of data)
# sigma=5: Conservative (removes fewer points)
# sigma=2: Aggressive (removes more points)

Manual Outlier Removal

import numpy as np

# Calculate median and standard deviation
median = np.median(flux)
std = np.std(flux)

# Remove points beyond 3 sigma
good = np.abs(flux - median) < 3 * std
time_clean = time[good]
flux_clean = flux[good]
error_clean = error[good]

Removing Long-Term Trends

Flattening with Lightkurve

# Flatten to remove low-frequency variability
# window_length: number of cadences to use for smoothing
lc_flat = lc_clean.flatten(window_length=500)

# Common window lengths:
# 100-200: Remove short-term trends
# 300-500: Remove medium-term trends (typical for TESS)
# 500-1000: Remove long-term trends

The flatten() method uses a Savitzky-Golay filter to remove trends while preserving transit signals.

Iterative Sine Fitting

For removing high-frequency stellar variability (rotation, pulsation):

def sine_fitting(lc):
    """Remove dominant periodic signal by fitting sine wave."""
    pg = lc.to_periodogram()
    model = pg.model(time=lc.time, frequency=pg.frequency_at_max_power)
    lc_new = lc.copy()
    lc_new.flux = lc_new.flux / model.flux
    return lc_new, model

# Iterate multiple times to remove multiple periodic components
lc_processed = lc_clean.copy()
for i in range(50):  # Number of iterations
    lc_processed, model = sine_fitting(lc_processed)

Warning: This removes periodic signals, so use carefully if you're searching for periodic transits.

Handling Data Quality Flags

IMPORTANT: Quality flag conventions vary by data source!

Standard TESS format

# For standard TESS files (flag=0 is GOOD):
good = flag == 0
time_clean = time[good]
flux_clean = flux[good]
error_clean = error[good]

Alternative formats

# For some exported files (flag=0 is BAD):
good = flag != 0
time_clean = time[good]
flux_clean = flux[good]
error_clean = error[good]

Always verify your data format! Check which approach gives cleaner results.

Preprocessing Pipeline Considerations

When building a preprocessing pipeline for exoplanet detection:

Key Steps (Order Matters!)

  1. Quality filtering: Apply data quality flags first
  2. Outlier removal: Remove bad data points (flares, cosmic rays)
  3. Trend removal: Remove long-term variations (stellar rotation, instrumental drift)
  4. Optional second pass: Additional outlier removal after detrending

Important Principles

  • Always include flux_err: Critical for proper weighting in period search algorithms
  • Preserve transit shapes: Use methods like flatten() that preserve short-duration dips
  • Don't over-process: Too aggressive preprocessing can remove real signals
  • Verify visually: Plot each step to ensure quality

Parameter Selection

  • Outlier removal sigma: Lower sigma (2-3) is aggressive, higher (5-7) is conservative
  • Flattening window: Should be longer than transit duration but shorter than stellar rotation period
  • When to do two passes: Remove obvious outliers before detrending, then remove residual outliers after

Preprocessing for Exoplanet Detection

For transit detection, be careful not to remove the transit signal:

  1. Remove outliers first: Use sigma=3 or sigma=5
  2. Flatten trends: Use window_length appropriate for your data
  3. Don't over-process: Too much smoothing can remove shallow transits

Visualizing Results

Always plot your light curve to verify preprocessing quality:

import matplotlib.pyplot as plt

# Use .plot() method on LightCurve objects
lc.plot()
plt.show()

Best practice: Plot before and after each major step to ensure you're improving data quality, not removing real signals.

Dependencies

pip install lightkurve numpy matplotlib

References

Best Practices

  1. Always check quality flags first: Remove bad data before processing
  2. Remove outliers before flattening: Outliers can affect trend removal
  3. Choose appropriate window length: Too short = doesn't remove trends, too long = removes transits
  4. Visualize each step: Make sure preprocessing improves the data
  5. Don't over-process: More preprocessing isn't always better

Related Skills

View on GitHub
GitHub Stars1.8k
CategoryDevelopment
Updated3mo ago
Forks368

Languages

PDDL

Trust signals

98/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 info