003-skills/.claude/skills-backup-20251210-155310/nixtla-usage-optimizer/SKILL.md
Audits Nixtla library usage and recommends cost-effective routing strategies. Scans TimeGPT, StatsForecast, and MLForecast patterns, identifies cost optimization opportunities, generates comprehensive usage reports, and suggests smart routing between models. Activates when user needs cost optimization, API usage audit, routing strategy design, or Nixtla cost reduction.
npx skillsauth add intent-solutions-io/plugins-nixtla nixtla-usage-optimizerInstall 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.
Audit Nixtla library usage and recommend cost-effective routing strategies.
This skill analyzes and optimizes Nixtla usage:
Required:
No Additional Packages: Uses only Read, Glob, Grep tools
Find all Nixtla library usage:
grep -r "NixtlaClient" --include="*.py" .
grep -r "StatsForecast" --include="*.py" .
grep -r "MLForecast" --include="*.py" .
Categorize usage by:
Create 000-docs/nixtla_usage_report.md with:
Apply recommendations:
Error: No Nixtla usage found
Solution: Repository may not use Nixtla - recommend adoption
Error: Cannot determine cost impact
Solution: Add usage metrics or API call logging
Error: Mixed usage patterns
Solution: Report both opportunities, prioritize high-impact
Error: No baseline models found
Solution: Recommend adding StatsForecast for fallback
Scan results:
Found Nixtla usage:
- TimeGPT: 12 locations
- StatsForecast: 5 locations
- MLForecast: 2 locations
Recommendations:
1. Replace TimeGPT in 4 low-impact areas (save ~40%)
2. Add fallback to StatsForecast baselines
3. Keep TimeGPT for high-value forecasts
Scan results:
Found Nixtla usage:
- StatsForecast: 8 locations
- TimeGPT: 0 locations
Recommendations:
1. Add TimeGPT for 2 high-value forecasts
2. Keep baselines for simple patterns
3. Implement tiered routing
Related Skills:
nixtla-experiment-architect: Validate routing decisionsnixtla-timegpt-finetune-lab: Evaluate fine-tuning ROInixtla-prod-pipeline-generator: Implement routing in productiontesting
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".