003-skills/.claude/skills/nixtla-prod-pipeline-generator/SKILL.md
Transform forecasting experiments into Airflow/Prefect pipelines with monitoring. Use when deploying forecasts to production. Trigger with 'generate pipeline' or 'create Airflow DAG'.
npx skillsauth add intent-solutions-io/plugins-nixtla nixtla-prod-pipeline-generatorInstall 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.
Transform validated forecasting experiments into production-ready inference pipelines with proper orchestration, monitoring, and error handling.
This skill productionizes Nixtla forecasting workflows by generating complete deployment artifacts:
All pipelines implement: Extract -> Transform -> Forecast -> Load -> Monitor
Required:
forecasting/config.ymlEnvironment Variables:
NIXTLA_API_KEY: TimeGPT API key (if using TimeGPT)FORECAST_DATA_SOURCE: Production data connection stringFORECAST_DESTINATION: Output destination for forecastsInstallation:
pip install nixtla pandas statsforecast # Core
pip install apache-airflow # For Airflow
pip install prefect # For Prefect
Load experiment from forecasting/config.yml:
python {baseDir}/scripts/read_experiment.py --config forecasting/config.yml
Choose based on requirements:
python {baseDir}/scripts/generate_pipeline.py \
--config forecasting/config.yml \
--platform airflow \
--output pipelines/
python {baseDir}/scripts/add_monitoring.py \
--pipeline pipelines/forecast_dag.py \
--metrics smape,mase
Follow generated pipelines/README.md for deployment instructions.
Error: Config file not found
Solution: Run nixtla-experiment-architect first to create config
Error: NIXTLA_API_KEY not set
Solution: Export your TimeGPT API key or use StatsForecast baselines
Error: Database connection failed
Solution: Verify FORECAST_DATA_SOURCE connection string
Error: Forecast quality check failed
Solution: Pipeline auto-falls back to baseline models
python {baseDir}/scripts/generate_pipeline.py \
--config forecasting/config.yml \
--platform airflow \
--schedule "0 6 * * *" \
--output pipelines/
Output:
Generated: pipelines/forecast_dag.py
Schedule: Daily at 6am
Tasks: extract -> transform -> forecast -> load -> monitor
python {baseDir}/scripts/generate_pipeline.py \
--config forecasting/config.yml \
--platform cron \
--output pipelines/
{baseDir}/scripts/{baseDir}/assets/templates/Related Skills:
nixtla-experiment-architect: Creates experiments to productionizenixtla-timegpt-finetune-lab: Fine-tuned models for pipelinesnixtla-usage-optimizer: Cost-effective routing strategiestesting
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".