model-selector

Classify textual tasks into complexity bands and propose abstract model labels.

21|4|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/JotJunior/cstk --skill model-selector-jotjunior
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: model-selector
Source: https://github.com/JotJunior/cstk/tree/main/global/skills/model-selector
Command: npx skills add https://github.com/JotJunior/cstk --skill model-selector-jotjunior

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires awk, grep, sed, tr, mktemp, head, wc, basename, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Classifies a textual task into complexity bands (rasa, media, profunda) and proposes an abstract model label (haiku, sonnet, opus, or manter-atual) to guide model selection for the next step in a pipeline.

Core Features & Use Cases

  • Deterministic classification using a catalog of signals to assign a complexity tier and suggest a cost-effective model.
  • Standardized output in Markdown with sections for the suggested model, signal counts, justification, and fallback option, enabling easy integration with orchestration tooling.
  • Offline, POSIX-compatible operation with a local signal catalog, designed for integration by an orchestrator or human operator prior to invoking heavier sub-agents.

Quick Start

Feed a textual task description to the classifier to obtain a model suggestion and score.

Frequently Asked Questions about model-selector

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

FAQPage Schema
How do I classify task complexity to select the right LLM model tier?

Task complexity classification assigns textual inputs to bands like rasa, media, or profunda, proposing a model label such as haiku, sonnet, or opus to guide selection. It uses a deterministic signal catalog to score the input and output a structured Markdown justification.

What's the best way to automate model selection before invoking expensive sub-agents?

Automated model selection uses a deterministic classifier to evaluate task descriptions and suggest a cost-effective model tier. It outputs a Markdown block with the suggested model, score, and justification, designed for integration by an orchestrator before calling heavier sub-agents.

Can I run deterministic task classification offline using only POSIX tools?

Yes, deterministic task classification runs offline relying exclusively on POSIX tools like awk, grep, and sed. It reads a local signal catalog and processes input strings up to 4096 characters without requiring network access or external dependencies.

Does this model selector approach support integration with existing orchestrator pipelines?

The model selector is designed for orchestrator integration, providing a standardized Markdown output with SuggestedModel, Score, Justification, and Alternative sections. This format enables automated parsing to route tasks to appropriate sub-agents based on complexity bands.

What are the limitations of using a signal catalog for model selection classification?

Signal catalog classification is limited to input strings of 4096 characters and processes a single task at a time. It relies on a static local references file, meaning the signal catalog must be manually maintained to reflect new task patterns or complexity indicators accurately.

How does deterministic signal-based model selection compare to dynamic LLM-based routing?

Deterministic signal-based classification uses fixed pattern matching with POSIX tools to assign complexity tiers, while dynamic routing typically consumes tokens for inference. The deterministic approach offers reproducible scores and offline operation but lacks adaptive contextual understanding of novel inputs.