update_models

Audit AI model providers in sources.js against live APIs and emit JSON diffs.

2.2k|243|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/vava-nessa/free-coding-models --skill update-models-vava-nessa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update_models
Source: https://github.com/vava-nessa/free-coding-models/tree/main/.pi/skills/update_models
Command: npx skills add https://github.com/vava-nessa/free-coding-models --skill update-models-vava-nessa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit AI model providers listed in sources.js against live provider APIs to identify deprecated, new, and config-changed models.

Core Features & Use Cases

  • Discovery: scan providers for changes and automatically detect deprecated/new/config changes.
  • Diffing: generate structured JSON diffs per provider to support git-based auditing.
  • Workflow: orchestrate sequential researchers and commit updates to sources.js.

Quick Start

Run the update_models skill to audit all providers in sources.js and generate a commit-ready diff.

Frequently Asked Questions about update_models

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit AI model providers against live APIs to find deprecated models?

To detect deprecated and new models, you can audit AI model providers listed in sources.js against live provider APIs. It operates sequentially and emits a structured JSON diff for each provider to identify changes.

How do I generate a structured JSON diff for model providers in sources.js?

You generate a structured JSON diff by sequentially operating AI model providers listed in sources.js against live APIs. The process identifies config-changed models and emits a diff for each provider to apply to sources.js.

Can I audit specific model providers instead of all providers in sources.js?

Yes, you can audit specific model providers by optionally selecting all, stale, or specific providers during the audit process. This targets the scan against live APIs and generates structured JSON diffs only for the chosen providers.

Does this API model audit use git history for archiving state?

Yes, this API model audit uses git history as the archive. It stores audit state in audit_state.json and applies structured JSON diffs to sources.js, recording the results for commit to maintain an archive of model changes.

What is the best way to automate updating AI model configurations?

The best way to automate updating AI model configurations is to orchestrate sequential researchers that audit providers against live APIs. This workflow detects deprecated and config-changed models, applying commit-ready diffs to sources.js.