with one click
find-install-skills
// Find and install relevant Omnibot skills. Use when the user asks "找个 skill", "有没有这个功能的 skill", "find a skill for X", "is there a skill for X", or wants to extend the agent with an installable workflow.
// Find and install relevant Omnibot skills. Use when the user asks "找个 skill", "有没有这个功能的 skill", "find a skill for X", "is there a skill for X", or wants to extend the agent with an installable workflow.
| name | find-install-skills |
| description | Find and install relevant Omnibot skills. Use when the user asks "找个 skill", "有没有这个功能的 skill", "find a skill for X", "is there a skill for X", or wants to extend the agent with an installable workflow. |
CRITICAL: NEVER use
npx skills addto install skills. Always use the bundled git-clone-based installer script (install_with_skills_cli.sh) for installation.npx skills findis allowed only for searching. Installation MUST go through the script.
Use this skill to discover, compare, and install skills for Omnibot.
This version is adapted from the open vercel-labs/skills idea, but the workflow is aligned with Omnibot's phone runtime, .omnibot/skills workspace, built-in skill store, and agent tools.
Before searching the internet:
skills_list to see what is already installed or bundled.skills_read.Use this skill when the user:
terminal_execute to run npx skills find <query>.react performance, playwright e2e, pr review, android automation, or changelog.Do not use browser search, repository browsing, or skills.sh as the primary search path for the phone agent. Skill discovery on phone should happen through the command line with npx skills find.
The phone runtime usually installs npm and can run npx skills, so npx skills find should be the default and only search path for phone skill discovery. Do not use npx skills add for installation. Use the bundled git-clone-based installer script for the final install step.
Do not recommend a skill from a search snippet alone. Verify:
SKILL.mdWhen you find a candidate, tell the user:
Keep the list short. Usually give the best 1 to 3 options.
NEVER use
npx skills add. Always use the bundledinstall_with_skills_cli.shscript.
Only install a skill after the user confirms.
npx skills add under any circumstances. Use the bundled installer script instead..omnibot/skills/<skill-id>/.SKILL.md plus any scripts/, references/, assets/, or evals/.skills_list.terminal_execute to run raw npx skills find ... only for searching candidate skillsnpx skills add for installation — this is strictly forbidden; always use the bundled git-clone-based installer script.agents/skills as its primary runtime skill root.omnibot/skillsUse the script like this:
sh <scriptsDir>/install_with_skills_cli.sh claude-office-skills/skills@excel-automation
sh <scriptsDir>/install_with_skills_cli.sh vercel-labs/skills --skill find-skills
sh <scriptsDir>/install_with_skills_cli.sh https://github.com/vercel-labs/agent-skills --skill frontend-design
The script does all of the following:
git clone --depth 1 to fetch the repository into a temporary directorySKILL.md).omnibot/skills/Summary:
terminal_execute running npx skills find ...sh <scriptsDir>/install_with_skills_cli.sh ...owner/repo@skillskill-creator.Create or update an Omnibot / Xiaowan custom pet from a concept, reference image, or bare company name. Use when the user wants a selectable pet package, animated 8x9 sprite atlas, brand-discovery-driven mascot, or static fallback pet.
Built-in self-improvement loop for Omnibot agents. Use to record non-trivial failures, user corrections, outdated assumptions, and reusable best practices into structured workspace learnings, then promote stable rules into memory.
Guide for creating and updating effective Omnibot skills. Use when the user wants to add a new skill or improve an existing skill for the built-in Alpine workspace, tool workflows, or reusable domain knowledge.