local-model-routing

Assess local or remote model endpoints for bounded task roles using verified evidence.

3|Updated Jul 28, 2026
One-click install
npx skills add https://github.com/marcmarti9/agentit --skill local-model-routing-marcmarti9
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: local-model-routing
Source: https://github.com/marcmarti9/agentit/tree/main/skills/local-model-routing
Command: npx skills add https://github.com/marcmarti9/agentit --skill local-model-routing-marcmarti9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams that want local-first AI execution often assume a listed endpoint or model name guarantees capability, leading to failed tasks, privacy leaks, or fabricated results. This Skill provides a disciplined assessment protocol so an agent only relies on a local or remote model endpoint after verifying it against real evidence. ## Core Features & Use Cases - Evidence-based capability verification: Test reasoning, coding, extraction, or critique roles against the real endpoint with a small representative task before relying on it. - Honest scope boundaries: Clarifies that models/capabilities.yaml is a discovery reference, not a live router, and that Agentit does not implement automatic model routing. - Privacy and authorization guardrails: Prevents sending private code to new providers, spending money, or downgrading high-risk critics without explicit authorization. - Use Case: A user asks the agent to run code review on a local OpenAI-compatible endpoint. The agent verifies tools, context capacity, transport, and privacy boundaries on the actual endpoint, records observed capabilities and failures, and only then assigns the bounded role. ## Quick Start Assess whether my available local model endpoint can handle bounded code extraction tasks and record the verified capabilities.

Frequently Asked Questions about local-model-routing

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

FAQPage Schema
How do I verify a local model endpoint before using it?▼

Verify a local model endpoint by running a small representative task against the real endpoint and checking tools, context capacity, transport, and privacy boundaries. Record the provider, model, version, observed capabilities, failures, and verification date as evidence.

Does listing a local model in preferences activate it?▼

No, listing an endpoint in preferences does not activate it, test it, or grant permission to send code to another provider. The endpoint must be explicitly available and verified against the actual task before use.

Does Agentit support automatic local model routing?▼

No, Agentit currently does not implement an automatic models.parent, worker, or critic route response. The capabilities.yaml file is a discovery reference in a repository checkout, not a live router result, and installed packaging may not include it.

Is an OpenAI-compatible endpoint proof of full feature support?▼

No, an OpenAI-compatible endpoint is an interface claim, not proof that every tool or context feature works. A model name or declared tier is not evidence of parity; only observed testing against the real endpoint counts.

What happens when a local model endpoint fails a task?▼

On failure, use an authorized capable alternative or surface the blocked capability rather than fabricating execution. Persist scoped evidence as data, retest after endpoint or version changes, and never silently downgrade a high-risk critic.