002-workspaces/timegpt-lab/skills/timegpt-lab-bootstrap/SKILL.md
Guides TimeGPT lab environment setup including Python dependencies, API key configuration, smoke testing, experiment workflows, and optional CI/CD integration. Inspects environment docs and scripts to provide step-by-step setup instructions, troubleshooting guidance, and onboarding for new developers. Use when setting up TimeGPT lab, troubleshooting environment issues, or running experiments.
npx skillsauth add intent-solutions-io/plugins-nixtla nixtla-timegpt-lab-bootstrapInstall 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.
Assists with setting up and validating the TimeGPT lab environment. Provides guidance on Python dependencies, API key configuration, environment validation, TimeGPT smoke testing, and config-driven experiment workflows. This skill is read-only and provides instructions without directly executing scripts or making API calls.
This skill helps developers configure their local TimeGPT lab environment correctly. It inspects the lab's setup documentation, validation scripts, smoke test implementation, experiment harness, and configuration files to provide actionable setup instructions. It serves as the entry point for new developers joining the TimeGPT lab and as a troubleshooting aid for environment, API access, and experiment workflow issues.
Key capabilities:
docs/timegpt-env-setup.md for canonical setup instructionsscripts/validate_env.py to understand validation requirementsscripts/timegpt_smoke_test.py smoke test behavior and expected resultsscripts/run_experiment.py experiment workflowsexperiments/timegpt_experiments.json) and resultsFor this skill to be useful, the user needs:
pip)Required files:
{baseDir}/docs/timegpt-env-setup.md - Setup documentation (includes CI/CD integration section){baseDir}/scripts/validate_env.py - Environment validation script{baseDir}/scripts/timegpt_smoke_test.py - TimeGPT API smoke test{baseDir}/scripts/run_experiment.py - Experiment harness{baseDir}/experiments/timegpt_experiments.json - Experiment configuration{baseDir}/.env.example - Example environment configuration{baseDir}/data/timegpt_smoke_sample.csv - Sample dataset for testing{baseDir}/reports/timegpt_smoke_forecast.csv - Forecast output (created after smoke test){baseDir}/reports/timegpt_experiments_results.csv - Experiment metrics (created after experiments){baseDir}/reports/timegpt_experiments_summary.md - Experiment summary (created after experiments)Optional CI/CD files (Phase 09):
.github/workflows/timegpt-real-smoke.yml - Weekly real-API smoke test workflowWhen this skill is invoked, follow these steps:
Read the canonical setup guide:
{baseDir}/docs/timegpt-env-setup.md
Extract:
NIXTLA_TIMEGPT_API_KEY)Read the environment validation script:
{baseDir}/scripts/validate_env.py
Understand what checks it performs:
Based on the user's request, provide tailored instructions:
For first-time setup:
pip install nixtla utilsforecast pandas).env file or shell export)validate_env.py to confirm readinesstimegpt_smoke_test.py to test TimeGPT API accessFor troubleshooting:
For smoke test guidance:
python scripts/timegpt_smoke_test.pyreports/timegpt_smoke_forecast.csv)For experiment guidance:
scripts/run_experiment.py)experiments/timegpt_experiments.json)python scripts/run_experiment.pyFor onboarding:
skills/, scripts/, experiments/, data/, reports/, docs/).env files or API keys to gitvalidate_env.py is safe to run (no network calls)timegpt_smoke_test.py makes ONE real API call (costs may apply)run_experiment.py makes ONE API call per enabled experimentThe primary output of this skill is guidance text formatted as markdown or plain text:
validate_env.py outputExample output format:
## TimeGPT Lab Setup Instructions
### 1. Create Python Virtual Environment
cd 002-workspaces/timegpt-lab
python3 -m venv .venv-timegpt
source .venv-timegpt/bin/activate
### 2. Install Dependencies
pip install nixtla>=0.5.0 utilsforecast pandas
### 3. Configure API Key
cp .env.example .env
# Edit .env and set NIXTLA_TIMEGPT_API_KEY=your_actual_key_here
### 4. Validate Environment
python scripts/validate_env.py
Expected output: All checks should show ✓ (green checkmarks)
### 5. Run TimeGPT Smoke Test
python scripts/timegpt_smoke_test.py
Expected output: Forecast saved to reports/timegpt_smoke_forecast.csv
### 6. Next Steps
- Review forecast results in reports/
- Explore docs/timegpt-env-setup.md for detailed guidance
- Experiment with TimeGPT features using the lab environment
Symptom: validate_env.py shows ✗ NIXTLA_TIMEGPT_API_KEY environment variable NOT set
Solution:
# Option 1: Export in current shell
export NIXTLA_TIMEGPT_API_KEY="your_key_here"
# Option 2: Use .env file (recommended)
cp .env.example .env
# Edit .env and add your key
Symptom: ImportError: No module named 'nixtla'
Solution:
pip install nixtla utilsforecast pandas
Symptom: validate_env.py shows ✗ Python 3.8.x (unsupported)
Solution:
# Upgrade Python to 3.9+ using your package manager
# Example (Ubuntu/Debian):
sudo apt update
sudo apt install python3.10
# Recreate virtual environment with new Python version
python3.10 -m venv .venv-timegpt
source .venv-timegpt/bin/activate
Symptom: Skill cannot locate docs/timegpt-env-setup.md or scripts/validate_env.py
Solution: Ensure Phase 3 was completed successfully. These files should have been created during TimeGPT lab bootstrap. If missing, re-run Phase 3 or contact the repository maintainer.
User Input: "How do I set up the TimeGPT lab environment?"
Skill Behavior:
docs/timegpt-env-setup.mdOutput: Step-by-step markdown guide (see "Output" section above)
User Input: "validate_env.py is failing with missing nixtla package"
Skill Behavior:
pip install nixtlaOutput:
## Troubleshooting: Missing nixtla Package
The error indicates the `nixtla` package is not installed in your current Python environment.
**Fix**:
pip install nixtla>=0.5.0 utilsforecast pandas
**Verify**:
python scripts/validate_env.py
All checks should now pass with ✓ symbols.
User Input: "How do I test that TimeGPT is working?"
Skill Behavior:
Output:
## Testing TimeGPT API Access
After validating your environment, run the TimeGPT smoke test:
**Run the Smoke Test**:
python scripts/timegpt_smoke_test.py
**What It Does**:
- Loads a small sample dataset (2 series, 90 days each)
- Makes ONE TimeGPT API forecast call (14-day horizon)
- Saves results to reports/timegpt_smoke_forecast.csv
**Expected Output (Success)**:
✓ TimeGPT Smoke Test: PASSED
Summary:
Input series: 2
Forecast horizon: 14 days
Output: reports/timegpt_smoke_forecast.csv
**If It Fails**:
- Authentication error: Check your NIXTLA_TIMEGPT_API_KEY
- Dataset missing: Ensure you're in the correct directory
- Network error: Check internet connection
**Cost Note**:
This makes ONE real API call. Cost is minimal due to tiny dataset but varies by your TimeGPT plan. Don't run in a tight loop.
**Next Steps**:
- Review the forecast CSV in reports/
- Experiment with your own time series data
- Explore TimeGPT features and parameters
User Input: "How do I run TimeGPT experiments and compare different forecast horizons?"
Skill Behavior:
experiments/timegpt_experiments.json to understand configured experimentsOutput:
## Running TimeGPT Experiments
The lab includes a config-driven experiment harness for systematic TimeGPT testing.
**Run Experiments**:
python scripts/run_experiment.py
**What It Does**:
- Loads experiment configs from experiments/timegpt_experiments.json
- Runs each enabled experiment (default: 2 enabled)
- Computes metrics (MAE, SMAPE) against holdout data
- Generates CSV + Markdown reports
**Default Experiments**:
- timegpt_baseline_14d: 14-day forecast (enabled)
- timegpt_baseline_28d: 28-day forecast (enabled)
- timegpt_short_7d: 7-day forecast (disabled)
**Expected Output**:
✓ Experiment Harness: COMPLETE
Experiments run: 2
Reports:
- reports/timegpt_experiments_results.csv
- reports/timegpt_experiments_summary.md
**Interpreting Results**:
- CSV: Per-series, per-experiment metrics for detailed analysis
- Markdown: Human-readable summary with comparative analysis
- Lower MAE/SMAPE indicates better forecast accuracy
**Cost Note**:
Each enabled experiment makes ONE API call. Default config = 2 API calls total.
**Modifying Experiments**:
- Edit experiments/timegpt_experiments.json
- Set "enabled": false to disable experiments
- Add new experiments by copying existing blocks
- Re-run to apply changes
User Input: "What is the TimeGPT lab and how do I get started?"
Skill Behavior:
Output:
## Welcome to TimeGPT Lab
The TimeGPT lab is a workspace for experimenting with Nixtla's TimeGPT API and developing forecasting workflows.
**Directory Structure**:
- skills/: Claude Skills for TimeGPT workflows
- scripts/: Python scripts for API experiments, validation, and smoke tests
- experiments/: Experiment configs (JSON)
- data/: Sample datasets (includes timegpt_smoke_sample.csv)
- reports/: Generated forecasts, metrics, and analysis
- docs/: Setup guides and best practices
**Getting Started**:
1. Follow setup instructions: docs/timegpt-env-setup.md
2. Run environment validation: python scripts/validate_env.py
3. Test TimeGPT access: python scripts/timegpt_smoke_test.py
4. Run experiments: python scripts/run_experiment.py
5. Review results in reports/
**Next Steps After Setup**:
- Review TimeGPT documentation: https://docs.nixtla.io/
- Experiment with custom datasets
- Design new experiments in experiments/timegpt_experiments.json
Internal References (use {baseDir} for portability):
{baseDir}/docs/timegpt-env-setup.md{baseDir}/scripts/validate_env.py{baseDir}/scripts/timegpt_smoke_test.py{baseDir}/scripts/run_experiment.py{baseDir}/experiments/timegpt_experiments.json{baseDir}/data/timegpt_smoke_sample.csv{baseDir}/.env.example{baseDir}/../.directory-standards.md (in 002-workspaces root)External References:
Related Skills (future):
nixtla-timegpt-forecaster: Execute TimeGPT forecasts (Phase 4+)nixtla-schema-mapper: Transform data to Nixtla schemanixtla-experiment-architect: Design forecasting experimentsSkill Version: 0.4.0 (Bootstrap + Smoke Test + Experiments + CI/CD Integration) Phase: 9 (TimeGPT Real-API CI Smoke) Status: Lab-only skill, not yet promoted to 003-skills/
testing
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".