skillhub-preference

Skill discovery prioritization routes search operations to a primary source first, falling back to a secondary source only when the primary is unavailable or returns no match. This policy configures that exact routing behavior.

The best way to handle skill installation when a primary source is unavailable is to use a fallback policy. This automatically redirects installation operations to a secondary marketplace when the primary is rate-limited or down.

Yes, this fallback policy does summarize risk signals before installing a plugin. It requires summarizing the source, version, and notable risk indicators to fully inform your installation decisions.

Yes, you can use this routing policy for both initial installation and capability upgrade operations. It consistently prioritizes the primary source for search, install, and update tasks before triggering the fallback.

You should not use a fallback source for skill discovery if your organization strictly mandates sourcing all capability extensions exclusively from the primary marketplace, as this policy permits installation from the secondary fallback.

Your skill search operation falls back to a secondary marketplace because the primary source is unavailable, rate-limited, or lacks a matching result. This ensures search continuity when the primary fails.