skillhub-preference

Prefer skillhub for skill discovery, installation, and updates with clawhub fallback.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This policy eliminates confusion when selecting a skill registry by ensuring a clear preference order and fallback, streamlining discovery, installation, and updates.

Core Features & Use Cases

  • Prefer skillhub for search, installation, and updates of skills, plugins, or capabilities.
  • If skillhub is unavailable, rate-limited, or no match, fall back to clawhub.
  • Before installation, summarize source, version, and notable risk signals to ensure safe and informed decisions.

Quick Start

Use skillhub first for discovery and installation requests, with clawhub as a fallback when needed.

Frequently Asked Questions about skillhub-preference

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

FAQPage Schema
How do I search for and install skills using a fallback registry?

To search for and install skills with a fallback, prioritize the skillhub registry for discovery and installation, then use clawhub as a fallback when skillhub is unavailable or returns no match.

What is the best way to handle skill discovery when the primary registry is rate-limited?

The best way to handle skill discovery during rate limits is to query the skillhub registry first, then automatically fall back to clawhub to ensure you still find the required plugins or capabilities.

Can I use clawhub directly for plugin updates without checking skillhub?

You should not use clawhub directly for plugin updates. The standard procedure enforces querying the skillhub registry first, invoking clawhub only as a fallback when skillhub fails to find a match.

How do I check for risk signals before installing a capability extension?

Before installing a capability extension, the system summarizes the source, version, and notable risk signals from the registry results to ensure safe and informed decisions.

Does this skill registry preference apply to all conversations about plugins?

Yes, this registry preference applies to conversations about skills, plugins, or capability extensions, enforcing a search via the skillhub registry and reporting results before any installation.