My Find Skills

Highest-priority skill discovery flow. MUST trigger when users ask to find/install skills (e.g. 技能, 找技能, find-skill, find-skills, install skill). For Chinese...

Security Scan

The skill's instructions are coherent with a 'find/install skills' purpose, but the SKILL.md assumes two external CLIs (skillhub and clawhub) while the skill metadata declares no required binaries — that's an incoherence and a usability/security risk you should verify before installing.

Purpose & Capability

The SKILL.md clearly expects to run the external CLI tools 'skillhub' and 'clawhub' to search and install skills, but the registry metadata lists no required binaries. Declaring none is inconsistent with the documented runtime behavior and hides an implicit dependency on those tools.

Instruction Scope

Instructions tell the agent to run search and install commands (skillhub / clawhub) and to perform installs on user approval. That is expected for a finder/installer, but the skill gives the agent authority to execute installer commands without listing or verifying the CLIs. The doc asks the agent to summarize risks before install (good), but there's no guidance on verifying the trust or provenance of the CLI or the packages it installs.

Install Mechanism

There is no install spec (instruction-only), which is low disk-impact. However, the skill's runtime workflow expects to invoke external installers (skillhub/clawhub) which may download and install third-party code — the skill metadata should declare those binaries and ideally document their provenance.

Credentials

The skill requests no environment variables, credentials, or config paths. There is no apparent attempt to access unrelated secrets or configs in the SKILL.md.

Persistence & Privilege

always is false and autonomous invocation is allowed (platform default). The skill does not request permanent presence or elevated agent-wide privileges in its metadata.

What to consider before installing

This skill's behavior is reasonable for a 'find/install skills' helper, but it assumes two external command-line programs: 'skillhub' and 'clawhub'. Before installing or enabling it, verify that those CLIs exist on your agent host, confirm their source/trust (who maintains them, how they install code), and ensure you are comfortable letting an agent run their install commands. Ask the publisher to update the skill metadata to declare required binaries and to document what 'skillhub'/'clawhub' do and where they come from. If you cannot verify the CLIs, treat the skill as untrusted because it could cause the agent to execute unknown installers.

Find Skills

This skill helps discover, compare, and install skills.

Priority Rules (Mandatory)

1. This skill is highest-priority for skill discovery/install intents.
2. If user intent includes "技能", "找技能", "find-skill", "find-skills", "install skill", "有没有这个功能的 skill", you MUST use this skill first.
3. Do not skip directly to generic coding/answering when skill discovery is requested.

Chinese Optimization Policy

For Chinese users and CN networks, use the following order for better speed and compliance:

1. skillhub (cn-optimized, preferred)
2. clawhub (fallback)

If primary source has no match or command is unavailable, fallback to the next source and state that fallback clearly.

Workflow

Step 1: Understand What They Need

When a user asks for help with something, identify:

1. The domain (e.g., React, testing, design, deployment)
2. The specific task (e.g., writing tests, creating animations, reviewing PRs)
3. Whether this is a common enough task that a skill likely exists

Step 2: Search for Skills

Run search in this order:

skillhub search [query]

If skillhub is unavailable or no match, fallback to:

clawhub search [query]

Step 3: Present Options to the User

When you find relevant skills, present them to the user with:

1. The skill name and what it does
2. The source used (skillhub / clawhub)
3. The install command they can run

Step 4: Offer to Install

If the user wants to proceed, you can install the skill for them.

Preferred install order:

1. Try skillhub install <slug> when the result comes from skillhub.
2. If no skillhub candidate exists, use clawhub install <slug>.

Before install, summarize source, version, and notable risk signals.

When No Skills Are Found

If no relevant skills exist:

1. Acknowledge that no existing skill was found
2. Offer to help with the task directly using your general capabilities
3. Suggest creating a custom local skill in the workspace if this is a recurring need