003-skills/.claude/skills/nixtla-exogenous-integrator/SKILL.md
Incorporates external variables (holidays, weather, events) into TimeGPT forecasts to improve accuracy. Use when forecasts require external data, holidays impact sales, or weather affects demand. Trigger with 'include holidays', 'add weather data', 'integrate events'.
npx skillsauth add intent-solutions-io/plugins-nixtla nixtla-exogenous-integratorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Augments TimeGPT forecasts with exogenous variables for increased accuracy.
Enhances time series predictions by integrating external data sources like holidays, weather, and events.
This skill enriches TimeGPT forecasts by considering external factors influencing time series data. It reads exogenous data from CSV files, aligns it with the historical data, and passes both to the TimeGPT API. This integration improves forecast accuracy, especially when events or external conditions affect the time series. The skill outputs an augmented forecast incorporating the impact of these exogenous variables.
Tools: Read, Write, Bash, Glob, Grep
Environment: NIXTLA_TIMEGPT_API_KEY
Packages:
pip install nixtla pandas matplotlib
Read historical time series CSV and exogenous variables CSVs. Ensure they have a common date ('ds') column.
Script: {baseDir}/scripts/load_data.py
Usage:
python {baseDir}/scripts/load_data.py data.csv holidays.csv
The loader expects:
unique_id, ds, y columnsds column plus feature columnsMerge historical and exogenous dataframes based on the 'ds' column using the alignment script.
Script: {baseDir}/scripts/align_data.py
The script validates that both datasets share a 'ds' column and checks for column name conflicts. It performs a left join to preserve all historical timestamps.
Run the integration script with your data files and forecast parameters.
Script: {baseDir}/scripts/integrate_exogenous.py
Usage:
python {baseDir}/scripts/integrate_exogenous.py \
--input data.csv \
--exogenous holidays.csv \
--horizon 14 \
--freq D
Parameters:
--input: Historical time series CSV file--exogenous: Exogenous variables CSV file (optional)--horizon: Number of periods to forecast--freq: Time series frequency (D=daily, H=hourly, M=monthly, etc.)The script automatically:
Error: Exogenous data missing 'ds' column
Solution: Rename the date column in the exogenous data to 'ds'.
Error: Mismatch in date range between historical and exogenous data
Solution: Ensure the exogenous data covers the entire historical and forecast period.
Error: Exogenous variables have NaN values in the forecast horizon
Solution: Provide future values for exogenous variables for the entire forecast horizon.
Error: TimeGPT API rejected exogenous variables
Solution: Ensure exogenous variables are numeric and compatible with the TimeGPT API schema.
Error: NIXTLA_TIMEGPT_API_KEY environment variable not set
Solution: Set your TimeGPT API key as an environment variable before running the script.
Input (data.csv):
unique_id,ds,y
store_1,2024-01-01,100
store_1,2024-01-02,120
store_1,2024-01-03,115
Input (holidays.csv):
ds,holiday
2024-01-01,1
2024-01-02,0
2024-01-03,0
2024-01-04,0
Command:
python {baseDir}/scripts/integrate_exogenous.py \
--input data.csv \
--exogenous holidays.csv \
--horizon 7 \
--freq D
Output (forecast_exogenous.csv):
unique_id,ds,TimeGPT,TimeGPT-lo-90,TimeGPT-hi-90
store_1,2024-01-04,125,110,140
store_1,2024-01-05,128,113,143
Input (data.csv):
unique_id,ds,y
grid_1,2024-01-01 00:00,5000
grid_1,2024-01-01 01:00,5100
Input (weather.csv):
ds,temperature
2024-01-01 00:00,10
2024-01-01 01:00,8
2024-01-01 02:00,7
Command:
python {baseDir}/scripts/integrate_exogenous.py \
--input data.csv \
--exogenous weather.csv \
--horizon 24 \
--freq H
Output: Hourly forecast incorporating temperature trends.
{baseDir}/scripts/ directory contains all executable codetesting
This skill enables Claude to manage isolated test environments using Docker Compose, Testcontainers, and environment variables. It is used to create consistent, reproducible testing environments for software projects. Claude should use this skill when the user needs to set up a test environment with specific configurations, manage Docker Compose files for test infrastructure, set up programmatic container management with Testcontainers, manage environment variables for tests, or ensure cleanup after tests. Trigger terms include "test environment", "docker compose", "testcontainers", "environment variables", "isolated environment", "env-setup", and "test setup".
tools
This skill uses the test-doubles-generator plugin to automatically create mocks, stubs, spies, and fakes for unit testing. It analyzes dependencies in the code and generates appropriate test doubles based on the chosen testing framework, such as Jest, Sinon, or others. Use this skill when you need to generate test doubles, mocks, stubs, spies, or fakes to isolate units of code during testing. Trigger this skill by requesting test double generation or using the `/gen-doubles` or `/gd` command.
tools
This skill enables Claude to generate realistic test data for software development. It uses the test-data-generator plugin to create users, products, orders, and custom schemas for comprehensive testing. Use this skill when you need to populate databases, simulate user behavior, or create fixtures for automated tests. Trigger phrases include "generate test data", "create fake users", "populate database", "generate product data", "create test orders", or "generate data based on schema". This skill is especially useful for populating testing environments or creating sample data for demonstrations.
development
This skill analyzes code coverage metrics to identify untested code and generate comprehensive coverage reports. It is triggered when the user requests analysis of code coverage, identification of coverage gaps, or generation of coverage reports. The skill is best used to improve code quality by ensuring adequate test coverage and identifying areas for improvement. Use trigger terms like "analyze coverage", "code coverage report", "untested code", or the shortcut "cov".