Legacy alias for explicit model-landscape research or an observed provider/model change. Reuse installed model-radar or model-audit; no mandatory freshness action is added to ordinary delegation.
Installs into .claude/skills of the current project.
Are you the author of Refresh Model Landscape?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/papemati98-refresh-model-landscape)
---
name: refresh-model-landscape
description: "Legacy alias for explicit model-landscape research or an observed provider/model change. Reuse installed model-radar or model-audit; no mandatory freshness action is added to ordinary delegation."
---
# Model-landscape compatibility alias
Use this alias when model/provider facts are materially unknown or changed, or
when the owner explicitly requests a landscape review. It is not a gate before
every task, model choice or Fleet call.
Resolve the active managed `model-radar` or `model-audit` skill from installation
metadata and follow its current targeted research procedure. Use primary
provider evidence and the actual CLI/catalog version for the changed claim.
Keep one existing canonical evidence artifact; do not create another freshness
counter, copied policy, audit registry or standing model loop.
Do not infer subscription access, privacy/training settings or model identity
from a marketing name. An unknown remains unknown. Research does not grant
access, buy a plan, enable PAYG, authorize a denied model or change routing.
Do not read credential values or send project data as provider feedback.
Unchanged ordinary work reuses the current catalog and deterministic Fleet
availability gates. No extra council, second planner, receipt or 7-day market
refresh is imposed by this compatibility alias.
