selecting-models
Wraps host.bridge.model_registry_client.discover() so the planner can ask "which models are installed for capability X?". Returns either a list of ModelHandle dicts or a MissingModelEnvelope. Used dur
SKILL.md.claude/skills/selecting-models/SKILL.md
GitHubselecting-models
Planning-category skill (v1.2 Stage 6). Scripts:
scripts/select.py— stdin{"capability": str, "requested_for": str?}, stdout either aModelHandleJSON or aMissingModelEnvelopeJSON.
Behavior
- Build a
ModelRegistryagainst the live ComfyUI base URL. - Call
reg.resolve(capability, requested_for). - If a match: emit the
ModelHandle(capability, folder, name, matched_glob). - If no match: emit a
MissingModelEnvelopewith the sanctioned download candidates frompolicies/model_sources.yaml. The planner is responsible for deciding whether to insert amodel_downloadsub-goal or surface the envelope to the user.
CLAUDE.md compliance
- §12 #3 — registry is discovery-driven; this skill never reads a hardcoded list.
- §12 #5 — missing model surfaces an envelope, never silently substitutes.