{ "schemaVersion": "1.0", "item": { "slug": "rush-find-skills", "name": "@kanyun/rush-find-skills", "source": "tencent", "type": "skill", "category": "AI 智能", "sourceUrl": "https://clawhub.ai/krislavten/rush-find-skills", "canonicalUrl": "https://clawhub.ai/krislavten/rush-find-skills", "targetPlatform": "OpenClaw" }, "install": { "downloadMode": "redirect", "downloadUrl": "/downloads/rush-find-skills", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=rush-find-skills", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "installMethod": "Manual import", "extraction": "Extract archive", "prerequisites": [ "OpenClaw" ], "packageFormat": "ZIP package", "includedAssets": [ "SKILL.md" ], "primaryDoc": "SKILL.md", "quickSetup": [ "Download the package from Yavira.", "Extract the archive and review SKILL.md first.", "Import or place the package into your OpenClaw setup." ], "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run." } ] }, "sourceHealth": { "source": "tencent", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-23T16:43:11.935Z", "expiresAt": "2026-04-30T16:43:11.935Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard", "contentDisposition": "attachment; filename=\"4claw-imageboard-1.0.1.zip\"", "redirectLocation": null, "bodySnippet": null }, "scope": "source", "summary": "Source download looks usable.", "detail": "Yavira can redirect you to the upstream package for this source.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/rush-find-skills" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] }, "downloadPageUrl": "https://openagent3.xyz/downloads/rush-find-skills", "agentPageUrl": "https://openagent3.xyz/skills/rush-find-skills/agent", "manifestUrl": "https://openagent3.xyz/skills/rush-find-skills/agent.json", "briefUrl": "https://openagent3.xyz/skills/rush-find-skills/agent.md" }, "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run." } ] }, "documentation": { "source": "clawhub", "primaryDoc": "SKILL.md", "sections": [ { "title": "Find Skills (reskill)", "body": "This skill helps you discover and install skills from the reskill ecosystem." }, { "title": "Security & Trust", "body": "This skill instructs the agent to run CLI commands via reskill, an open-source, Git-based package manager for AI agent skills.\n\nWhy a specific registry?\nreskill supports multiple registries. This skill defaults to the Rush community registry (https://rush.zhenguanyu.com/) — the primary public registry for the reskill ecosystem, similar to how npm defaults to https://registry.npmjs.org. Users can override it at any time via --registry, the RESKILL_REGISTRY environment variable, or defaults.publishRegistry in skills.json.\n\nCLI execution approach:\nTo avoid downloading remote code on every invocation, we recommend installing reskill globally first:\n\nnpm install -g reskill\n\nIf a global installation is not available, npx reskill@latest can be used as a fallback. The agent should check for a global install before falling back to npx.\n\nKey Principles:\n\nSearch → Present → Ask → Install — always show results first, ask the user before installing.\nBe registry-aware — use the configured registry, tell the user which registry you're searching.\nPrefer local CLI — use globally installed reskill when available; fall back to npx only if needed." }, { "title": "When to Use This Skill", "body": "Use this skill when the user:\n\nAsks \"how do I do X\" where X might be a common task with an existing skill\nSays \"find a skill for X\" or \"is there a skill for X\"\nAsks \"can you do X\" where X is a specialized capability\nExpresses interest in extending agent capabilities\nWants to create, write, or publish a skill to a registry\nWants to search for tools, templates, or workflows\nMentions they wish they had help with a specific domain (design, testing, deployment, etc.)" }, { "title": "Quick Recommendations", "body": "For these well-known intents, skip the search and directly recommend the corresponding skill:\n\nUser IntentRecommended SkillCreate, write, or publish a skill to the registry@kanyun/rush-reskill-usage\n\nIf the skill is not already installed, offer to install it. Then proceed with Step 4 (Determine Target Agents) as usual." }, { "title": "What is reskill?", "body": "reskill is a Git-based package manager for AI agent skills. It provides declarative configuration, version locking, and seamless synchronization for managing skills across projects and teams.\n\nKey commands for skill discovery:\n\nreskill find — Search for skills by keyword\nreskill find --json — Search with machine-readable JSON output\nreskill install — Install a skill\nreskill list — List installed skills\nreskill info — Show skill details" }, { "title": "Step 0: Resolve CLI and Registry", "body": "CLI resolution: Check if reskill is installed globally. If available, use reskill directly. Otherwise fall back to npx reskill@latest.\n\nwhich reskill\n\nRegistry resolution (highest to lowest priority):\n\n--registry CLI option\nRESKILL_REGISTRY environment variable\ndefaults.publishRegistry in skills.json\nDefault: https://rush.zhenguanyu.com/\n\nIf none of the first three are set, pass --registry https://rush.zhenguanyu.com explicitly. Tell the user which registry you're searching." }, { "title": "Step 1: Understand What They Need", "body": "When a user asks for help with something, identify:\n\nThe domain (e.g., React, testing, design, deployment)\nThe specific task (e.g., writing tests, creating animations, reviewing PRs)\nWhether this is a common enough task that a skill likely exists" }, { "title": "Step 2: Search for Skills (Progressive Strategy)", "body": "Use --json for structured results. Examples below use reskill (substitute npx reskill@latest if not globally installed):\n\nreskill find \"\" --json --registry https://rush.zhenguanyu.com\n\nThe JSON output has this structure:\n\n{\n \"total\": 2,\n \"items\": [\n {\n \"name\": \"@scope/skill-name\",\n \"description\": \"What this skill does\",\n \"latest_version\": \"1.0.0\",\n \"keywords\": [\"keyword1\", \"keyword2\"],\n \"publisher\": { \"handle\": \"author\" },\n \"updated_at\": \"2025-01-01T00:00:00Z\"\n }\n ]\n}\n\nIMPORTANT: Use progressive search to maximize results. The registry may not support multi-word fuzzy matching, so follow this strategy:\n\nRound 1: Try the natural query first\n\nreskill find \"frontend design\" --json --registry https://rush.zhenguanyu.com\n\nIf total > 0, proceed to Step 3 (present results).\n\nRound 2: Try hyphenated version\n\nSkill names often use hyphens. If Round 1 returns 0 results, try connecting keywords with a hyphen:\n\nreskill find \"frontend-design\" --json --registry https://rush.zhenguanyu.com\n\nRound 3: Broaden to the most relevant single keyword\n\nIf still 0 results, pick the most specific keyword from the user's query and search with that alone:\n\nreskill find \"frontend\" --json --registry https://rush.zhenguanyu.com\n\nChoose the keyword that best narrows the domain (e.g., prefer \"frontend\" over \"design\" because \"design\" is too broad).\n\nRound 4 (optional): Try alternative/synonym keywords\n\nIf still no results, try synonyms or related terms:\n\n\"frontend\" → \"ui\", \"web\", \"react\"\n\"deploy\" → \"deployment\", \"ci-cd\", \"devops\"\n\"test\" → \"testing\", \"jest\", \"playwright\"\n\nAgent-side filtering\n\nWhen broader searches return multiple results, read each item's description field and filter by relevance to the user's original request. Only present skills whose description genuinely matches what the user needs. Do not present all results blindly.\n\nExample flow — user asks \"help me with frontend design\":\n\n1. find \"frontend design\" → 0 results\n2. find \"frontend-design\" → 0 results\n3. find \"frontend\" → 3 results\n4. Read descriptions → filter → 1 result is relevant to UI design\n5. Present that 1 result to user\n\nSearch query examples:\n\nUser saysRound 1Round 2 (hyphenated)Round 3 (single keyword)\"How do I make my React app faster?\"\"react performance\"\"react-performance\"\"react\"\"Can you help me with PR reviews?\"\"pr review\"\"pr-review\"\"review\"\"I need to create a changelog\"\"changelog\"——\"Help me write better TypeScript\"\"typescript practices\"\"typescript-practices\"\"typescript\"\n\nStop as soon as you get relevant results — no need to run all rounds." }, { "title": "Step 3: Present Results and Ask Before Installing", "body": "When you find relevant skills, present them clearly:\n\nThe skill name and description\nThe version and author\nWhich registry the result came from (public or private)\nThe install command\n\nThen ask the user which one(s) they want to install.\n\nExample response:\n\nI found a skill that might help! (from registry: rush.zhenguanyu.com)\n\n**@scope/react-best-practices** (v1.2.0)\nReact and performance optimization guidelines.\n\nTo install:\n reskill install @scope/react-best-practices -y --registry https://rush.zhenguanyu.com\n\nWould you like me to install it?\n\nIf multiple results are found, present the top 2-3 most relevant ones and let the user choose. Once the user confirms (e.g., \"install it\", \"yes\", \"install 1 and 3\"), proceed to install all confirmed skills — no need to ask again for each one." }, { "title": "Step 4: Determine Target Agents", "body": "Before installing, resolve which agent(s) to install to. Follow this priority:\n\nPriority 1: User explicitly specified --agent\n\nIf the user said something like \"install to cursor\" or \"install to claude-code\", pass -a directly — skip all detection.\n\nPriority 2: Read skills.json → defaults.targetAgents\n\nLook for skills.json in the current directory and up to 3 parent directories. If found, check for defaults.targetAgents:\n\n{\n \"defaults\": {\n \"targetAgents\": [\"cursor\", \"claude-code\"]\n }\n}\n\nIf targetAgents is configured, use those agents directly with -a:\n\nreskill install -y -a cursor claude-code --registry https://rush.zhenguanyu.com\n\nPriority 3: Detect agent directories\n\nIf no skills.json is found (or it has no targetAgents), scan the current directory and up to 3 parent directories for known agent directories:\n\nDirectoryAgent.cursor/cursor.claude/claude-code.codex/codex.windsurf/windsurf.github/skills/copilot.opencode/opencode\n\nNote: For GitHub Copilot, check .github/skills/ (not just .github/), since .github/ alone usually contains workflows/issue templates and does not imply Copilot usage.\n\nIf one or more agent directories are detected, tell the user what was found and confirm before installing:\n\nDetected agent directory: .cursor/\nWill install to Cursor (.cursor/skills/). Proceed? (or specify a different agent)\n\nIf the user confirms, install with -a:\n\nreskill install -y -a cursor --registry https://rush.zhenguanyu.com\n\nIf multiple agent directories are detected, list all of them and let the user choose which ones to install to.\n\nPriority 4: Ask the user\n\nIf no agent information is available from any of the above, ask the user which agent(s) to install to:\n\nNo agent configuration found. Which agent(s) would you like to install this skill to?\n\nSupported agents: cursor, claude-code, codex, windsurf, copilot, opencode\n\nThen install with the user's chosen agent(s)." }, { "title": "Step 5: Install the Skill", "body": "# Install to specific agent(s)\nreskill install -y -a --registry https://rush.zhenguanyu.com\n\n# Install globally (user-level, available in all projects)\nreskill install -y -g --registry https://rush.zhenguanyu.com\n\nThe -y flag skips CLI confirmation prompts.\n\nAfter installation, let the user know the skill is ready and briefly describe what new capabilities it provides." }, { "title": "Common Skill Categories", "body": "When constructing search queries, consider these categories:\n\nCategoryExample QueriesWeb Developmentreact, nextjs, typescript, css, tailwind, vueTestingtesting, jest, playwright, e2e, unit-testDevOpsdeploy, docker, kubernetes, ci-cd, github-actionsDocumentationdocs, readme, changelog, api-docsCode Qualityreview, lint, refactor, best-practices, clean-codeDesignui, ux, design-system, accessibility, figmaProductivityworkflow, automation, git, project-managementDatadatabase, sql, data-analysis, visualizationSkill Devreskill, publish, create-skill, skill-authoring" }, { "title": "Tips for Effective Searches", "body": "Follow the progressive strategy: multi-word → hyphenated → single keyword → synonyms\nPick the most specific keyword when narrowing down: prefer \"frontend\" over \"design\", prefer \"playwright\" over \"testing\"\nTry alternative terms: \"deploy\" → \"deployment\", \"ci-cd\", \"devops\"\nAlways read descriptions: when a broad search returns many results, use descriptions to filter relevant ones\nSkill names use hyphens: remember to try hyphenated versions like \"code-review\", \"best-practices\"" }, { "title": "When No Skills Are Found", "body": "If no relevant skills exist after exhausting all search rounds (multi-word → hyphenated → single keyword → synonyms):\n\nAcknowledge that no existing skill was found and briefly mention what you searched for\nOffer to help with the task directly using your general capabilities\nSuggest the user could create their own skill\n\nExample:\n\nI searched the registry with several queries (\"frontend design\", \"frontend-design\", \"frontend\")\nbut didn't find a matching skill.\n\nI can still help you with this task directly! Would you like me to proceed?\n\nIf this is something you do often, you could also create your own skill and share it:\n mkdir my-skill && echo \"---\\nname: my-skill\\n---\\n# My Skill\" > my-skill/SKILL.md" }, { "title": "Checking Installed Skills", "body": "Before searching for new skills, you can check what's already installed:\n\n# List all installed skills\nreskill list\n\n# Get details about a specific skill\nreskill info \n\nThis avoids suggesting skills the user already has." } ], "body": "Find Skills (reskill)\n\nThis skill helps you discover and install skills from the reskill ecosystem.\n\nSecurity & Trust\n\nThis skill instructs the agent to run CLI commands via reskill, an open-source, Git-based package manager for AI agent skills.\n\nWhy a specific registry? reskill supports multiple registries. This skill defaults to the Rush community registry (https://rush.zhenguanyu.com/) — the primary public registry for the reskill ecosystem, similar to how npm defaults to https://registry.npmjs.org. Users can override it at any time via --registry, the RESKILL_REGISTRY environment variable, or defaults.publishRegistry in skills.json.\n\nCLI execution approach: To avoid downloading remote code on every invocation, we recommend installing reskill globally first:\n\nnpm install -g reskill\n\n\nIf a global installation is not available, npx reskill@latest can be used as a fallback. The agent should check for a global install before falling back to npx.\n\nKey Principles:\n\nSearch → Present → Ask → Install — always show results first, ask the user before installing.\nBe registry-aware — use the configured registry, tell the user which registry you're searching.\nPrefer local CLI — use globally installed reskill when available; fall back to npx only if needed.\nWhen to Use This Skill\n\nUse this skill when the user:\n\nAsks \"how do I do X\" where X might be a common task with an existing skill\nSays \"find a skill for X\" or \"is there a skill for X\"\nAsks \"can you do X\" where X is a specialized capability\nExpresses interest in extending agent capabilities\nWants to create, write, or publish a skill to a registry\nWants to search for tools, templates, or workflows\nMentions they wish they had help with a specific domain (design, testing, deployment, etc.)\nQuick Recommendations\n\nFor these well-known intents, skip the search and directly recommend the corresponding skill:\n\nUser Intent\tRecommended Skill\nCreate, write, or publish a skill to the registry\t@kanyun/rush-reskill-usage\n\nIf the skill is not already installed, offer to install it. Then proceed with Step 4 (Determine Target Agents) as usual.\n\nWhat is reskill?\n\nreskill is a Git-based package manager for AI agent skills. It provides declarative configuration, version locking, and seamless synchronization for managing skills across projects and teams.\n\nKey commands for skill discovery:\n\nreskill find — Search for skills by keyword\nreskill find --json — Search with machine-readable JSON output\nreskill install — Install a skill\nreskill list — List installed skills\nreskill info — Show skill details\nHow to Help Users Find Skills\nStep 0: Resolve CLI and Registry\n\nCLI resolution: Check if reskill is installed globally. If available, use reskill directly. Otherwise fall back to npx reskill@latest.\n\nwhich reskill\n\n\nRegistry resolution (highest to lowest priority):\n\n--registry CLI option\nRESKILL_REGISTRY environment variable\ndefaults.publishRegistry in skills.json\nDefault: https://rush.zhenguanyu.com/\n\nIf none of the first three are set, pass --registry https://rush.zhenguanyu.com explicitly. Tell the user which registry you're searching.\n\nStep 1: Understand What They Need\n\nWhen a user asks for help with something, identify:\n\nThe domain (e.g., React, testing, design, deployment)\nThe specific task (e.g., writing tests, creating animations, reviewing PRs)\nWhether this is a common enough task that a skill likely exists\nStep 2: Search for Skills (Progressive Strategy)\n\nUse --json for structured results. Examples below use reskill (substitute npx reskill@latest if not globally installed):\n\nreskill find \"\" --json --registry https://rush.zhenguanyu.com\n\n\nThe JSON output has this structure:\n\n{\n \"total\": 2,\n \"items\": [\n {\n \"name\": \"@scope/skill-name\",\n \"description\": \"What this skill does\",\n \"latest_version\": \"1.0.0\",\n \"keywords\": [\"keyword1\", \"keyword2\"],\n \"publisher\": { \"handle\": \"author\" },\n \"updated_at\": \"2025-01-01T00:00:00Z\"\n }\n ]\n}\n\n\nIMPORTANT: Use progressive search to maximize results. The registry may not support multi-word fuzzy matching, so follow this strategy:\n\nRound 1: Try the natural query first\nreskill find \"frontend design\" --json --registry https://rush.zhenguanyu.com\n\n\nIf total > 0, proceed to Step 3 (present results).\n\nRound 2: Try hyphenated version\n\nSkill names often use hyphens. If Round 1 returns 0 results, try connecting keywords with a hyphen:\n\nreskill find \"frontend-design\" --json --registry https://rush.zhenguanyu.com\n\nRound 3: Broaden to the most relevant single keyword\n\nIf still 0 results, pick the most specific keyword from the user's query and search with that alone:\n\nreskill find \"frontend\" --json --registry https://rush.zhenguanyu.com\n\n\nChoose the keyword that best narrows the domain (e.g., prefer \"frontend\" over \"design\" because \"design\" is too broad).\n\nRound 4 (optional): Try alternative/synonym keywords\n\nIf still no results, try synonyms or related terms:\n\n\"frontend\" → \"ui\", \"web\", \"react\"\n\"deploy\" → \"deployment\", \"ci-cd\", \"devops\"\n\"test\" → \"testing\", \"jest\", \"playwright\"\nAgent-side filtering\n\nWhen broader searches return multiple results, read each item's description field and filter by relevance to the user's original request. Only present skills whose description genuinely matches what the user needs. Do not present all results blindly.\n\nExample flow — user asks \"help me with frontend design\":\n\n1. find \"frontend design\" → 0 results\n2. find \"frontend-design\" → 0 results\n3. find \"frontend\" → 3 results\n4. Read descriptions → filter → 1 result is relevant to UI design\n5. Present that 1 result to user\n\n\nSearch query examples:\n\nUser says\tRound 1\tRound 2 (hyphenated)\tRound 3 (single keyword)\n\"How do I make my React app faster?\"\t\"react performance\"\t\"react-performance\"\t\"react\"\n\"Can you help me with PR reviews?\"\t\"pr review\"\t\"pr-review\"\t\"review\"\n\"I need to create a changelog\"\t\"changelog\"\t—\t—\n\"Help me write better TypeScript\"\t\"typescript practices\"\t\"typescript-practices\"\t\"typescript\"\n\nStop as soon as you get relevant results — no need to run all rounds.\n\nStep 3: Present Results and Ask Before Installing\n\nWhen you find relevant skills, present them clearly:\n\nThe skill name and description\nThe version and author\nWhich registry the result came from (public or private)\nThe install command\n\nThen ask the user which one(s) they want to install.\n\nExample response:\n\nI found a skill that might help! (from registry: rush.zhenguanyu.com)\n\n**@scope/react-best-practices** (v1.2.0)\nReact and performance optimization guidelines.\n\nTo install:\n reskill install @scope/react-best-practices -y --registry https://rush.zhenguanyu.com\n\nWould you like me to install it?\n\n\nIf multiple results are found, present the top 2-3 most relevant ones and let the user choose. Once the user confirms (e.g., \"install it\", \"yes\", \"install 1 and 3\"), proceed to install all confirmed skills — no need to ask again for each one.\n\nStep 4: Determine Target Agents\n\nBefore installing, resolve which agent(s) to install to. Follow this priority:\n\nPriority 1: User explicitly specified --agent\n\nIf the user said something like \"install to cursor\" or \"install to claude-code\", pass -a directly — skip all detection.\n\nPriority 2: Read skills.json → defaults.targetAgents\n\nLook for skills.json in the current directory and up to 3 parent directories. If found, check for defaults.targetAgents:\n\n{\n \"defaults\": {\n \"targetAgents\": [\"cursor\", \"claude-code\"]\n }\n}\n\n\nIf targetAgents is configured, use those agents directly with -a:\n\nreskill install -y -a cursor claude-code --registry https://rush.zhenguanyu.com\n\nPriority 3: Detect agent directories\n\nIf no skills.json is found (or it has no targetAgents), scan the current directory and up to 3 parent directories for known agent directories:\n\nDirectory\tAgent\n.cursor/\tcursor\n.claude/\tclaude-code\n.codex/\tcodex\n.windsurf/\twindsurf\n.github/skills/\tcopilot\n.opencode/\topencode\n\nNote: For GitHub Copilot, check .github/skills/ (not just .github/), since .github/ alone usually contains workflows/issue templates and does not imply Copilot usage.\n\nIf one or more agent directories are detected, tell the user what was found and confirm before installing:\n\nDetected agent directory: .cursor/\nWill install to Cursor (.cursor/skills/). Proceed? (or specify a different agent)\n\n\nIf the user confirms, install with -a:\n\nreskill install -y -a cursor --registry https://rush.zhenguanyu.com\n\n\nIf multiple agent directories are detected, list all of them and let the user choose which ones to install to.\n\nPriority 4: Ask the user\n\nIf no agent information is available from any of the above, ask the user which agent(s) to install to:\n\nNo agent configuration found. Which agent(s) would you like to install this skill to?\n\nSupported agents: cursor, claude-code, codex, windsurf, copilot, opencode\n\n\nThen install with the user's chosen agent(s).\n\nStep 5: Install the Skill\n# Install to specific agent(s)\nreskill install -y -a --registry https://rush.zhenguanyu.com\n\n# Install globally (user-level, available in all projects)\nreskill install -y -g --registry https://rush.zhenguanyu.com\n\n\nThe -y flag skips CLI confirmation prompts.\n\nAfter installation, let the user know the skill is ready and briefly describe what new capabilities it provides.\n\nCommon Skill Categories\n\nWhen constructing search queries, consider these categories:\n\nCategory\tExample Queries\nWeb Development\treact, nextjs, typescript, css, tailwind, vue\nTesting\ttesting, jest, playwright, e2e, unit-test\nDevOps\tdeploy, docker, kubernetes, ci-cd, github-actions\nDocumentation\tdocs, readme, changelog, api-docs\nCode Quality\treview, lint, refactor, best-practices, clean-code\nDesign\tui, ux, design-system, accessibility, figma\nProductivity\tworkflow, automation, git, project-management\nData\tdatabase, sql, data-analysis, visualization\nSkill Dev\treskill, publish, create-skill, skill-authoring\nTips for Effective Searches\nFollow the progressive strategy: multi-word → hyphenated → single keyword → synonyms\nPick the most specific keyword when narrowing down: prefer \"frontend\" over \"design\", prefer \"playwright\" over \"testing\"\nTry alternative terms: \"deploy\" → \"deployment\", \"ci-cd\", \"devops\"\nAlways read descriptions: when a broad search returns many results, use descriptions to filter relevant ones\nSkill names use hyphens: remember to try hyphenated versions like \"code-review\", \"best-practices\"\nWhen No Skills Are Found\n\nIf no relevant skills exist after exhausting all search rounds (multi-word → hyphenated → single keyword → synonyms):\n\nAcknowledge that no existing skill was found and briefly mention what you searched for\nOffer to help with the task directly using your general capabilities\nSuggest the user could create their own skill\n\nExample:\n\nI searched the registry with several queries (\"frontend design\", \"frontend-design\", \"frontend\")\nbut didn't find a matching skill.\n\nI can still help you with this task directly! Would you like me to proceed?\n\nIf this is something you do often, you could also create your own skill and share it:\n mkdir my-skill && echo \"---\\nname: my-skill\\n---\\n# My Skill\" > my-skill/SKILL.md\n\nChecking Installed Skills\n\nBefore searching for new skills, you can check what's already installed:\n\n# List all installed skills\nreskill list\n\n# Get details about a specific skill\nreskill info \n\n\nThis avoids suggesting skills the user already has." }, "trust": { "sourceLabel": "tencent", "provenanceUrl": "https://clawhub.ai/krislavten/rush-find-skills", "publisherUrl": "https://clawhub.ai/krislavten/rush-find-skills", "owner": "krislavten", "version": "0.3.2", "license": null, "verificationStatus": "Indexed source record" }, "links": { "detailUrl": "https://openagent3.xyz/skills/rush-find-skills", "downloadUrl": "https://openagent3.xyz/downloads/rush-find-skills", "agentUrl": "https://openagent3.xyz/skills/rush-find-skills/agent", "manifestUrl": "https://openagent3.xyz/skills/rush-find-skills/agent.json", "briefUrl": "https://openagent3.xyz/skills/rush-find-skills/agent.md" } }