skillhub-preference

Search SkillHub for matching skills and fall back to ClawHub with risk signals.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/ViewWay/openclaw-skills --skill skillhub-preference-viewway
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skillhub-preference
Source: https://github.com/ViewWay/openclaw-skills/tree/main/skillhub-preference
Command: npx skills add https://github.com/ViewWay/openclaw-skills --skill skillhub-preference-viewway

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This policy-driven Skill guides teams to prefer SkillHub for skill discovery, installation, or upgrades, while offering a safe fallback to ClawHub when SkillHub is unavailable or yields no match.

Core Features & Use Cases

  • Ensures consistent discovery across registries by prioritizing SkillHub for new or updated skills.
  • Provides a clear fallback path to ClawHub to maintain productivity when SkillHub cannot fulfill the request.
  • Use Case: A developer asks for a plugin; the system searches SkillHub first, then ClawHub, and surfaces the best candidate with source, version, and risk signals before installation.

Quick Start

Search SkillHub first for the requested skill, then fallback to ClawHub if unavailable or no match.

Frequently Asked Questions about skillhub-preference

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

FAQPage Schema
How do I handle skill discovery when my primary registry is unavailable?

When your primary registry is unavailable, skill discovery falls back to ClawHub to find the best alternative match, summarizing source, version, and risk signals before installation.

What is the best way to manage consistent skill installation across multiple registries?

Managing consistent skill installation across registries requires a policy-driven approach that prioritizes SkillHub for discovery and falls back to ClawHub when no match is found.

Can I check risk signals and version information before installing a skill from a fallback registry?

Yes, you can check risk signals before installation. The discovery process summarizes the source, version, and notable risk signals from the fallback registry to inform your installation decisions.

Why does my skill search return results from a different registry than expected?

Your skill search returns results from a different registry because the discovery policy searches SkillHub first, then falls back to ClawHub if SkillHub is unavailable or yields no match.

When should I expect a fallback to ClawHub during skill discovery?

You should expect a fallback to ClawHub during skill discovery when SkillHub is completely unavailable or when a search query returns no matching skills in the primary registry.