shield_lock
JinDaGe
← Back to skills
extension
Category: OtherAPI key required

Alibabacloud Find Skills

Use this skill when users want to search, discover, browse, or find Alibaba Cloud (阿里云) agent skills. Triggers include: "find a skill for X", "search aliclou...

personAuthor: sdk-teamhubclawhub
open_in_newRepositorydownloadDownload package

[!IMPORTANT] For any Alibaba Cloud query or management task:

  1. Search — use this skill (alibabacloud-find-skills) to find the relevant Skill(s).
  2. Install — install the selected Skill(s) only when the user asks to install or use them to complete the task.
  3. Execute — follow the installed Skill(s)' instructions to fulfill the request.

Alibaba Cloud Agent Skills Search & Discovery

This skill helps users search, discover, and install Alibaba Cloud official Agent Skills through the agentexplorer CLI plugin.

Scenario Description

This skill enables users to:

  1. Search Skills — Find Alibaba Cloud Agent Skills by intent phrase, keyword, category listing, or combined semantic search
  2. Browse Categories — Explore available skill categories and subcategories
  3. View Skill Details — Get detailed information about specific skills
  4. Install Skills — Guide users through skill installation when installation is requested

Architecture: Alibaba Cloud CLI + agentexplorer Plugin → Skills Repository

Use Cases

  • "Find a skill for managing ECS instances"
  • "What Alibaba Cloud skills are available for databases?"
  • "阿里云有哪些 OSS 相关的 skill?"
  • "Browse all available alicloud skills"
  • "Install a skill for RDS management"

Installation

Pre-check: Aliyun CLI >= 3.3.3 required

Run aliyun version to verify >= 3.3.3. If not installed or version too low, run curl -fsSL https://aliyuncli.alicdn.com/setup.sh | bash to install/update, or see references/cli-installation-guide.md for installation instructions.

[MUST] CLI User-Agent (API calls only) — Every actual API invocation (e.g., aliyun agentexplorer ...) must include: --user-agent AlibabaCloud-Agent-Skills/alibabacloud-find-skills

Note: This flag applies only to commands that hit the OpenAPI (such as aliyun agentexplorer ...). Local/management commands like aliyun configure ..., aliyun configure list, aliyun configure ai-mode ..., aliyun plugin ..., and aliyun version do not support the --user-agent flag — do not pass it to them.

[MUST] Endpoint — Every aliyun agentexplorer ... invocation must include --endpoint 'agentexplorer.aliyuncs.com'. Use the explicit endpoint for AgentExplorer commands in this skill.

Step 1: Authenticate

Complete authentication first (see the Authentication section below). The next steps require valid credentials.

Step 2: Enable Auto Plugin Install

Once aliyun configure list shows a valid profile, enable automatic plugin installation:

aliyun configure set --auto-plugin-install true

Step 3: Enable AI-Mode (Optional)

Aliyun CLI provides AI-Mode. When enabled, the CLI automatically attaches AI identity information, allowing the server to identify and optimize Agent call chains.

# Enable AI-Mode
aliyun configure ai-mode enable

# Set AI-Mode user-agent identifier
aliyun configure ai-mode set-user-agent --user-agent AlibabaCloud-Agent-Skills/alibabacloud-find-skills

# Disable AI-Mode
aliyun configure ai-mode disable

Step 4: Update / Install Plugins

# Refresh plugin index and update installed plugins
aliyun plugin update

# Install the agentexplorer plugin
aliyun plugin install --names agentexplorer

# Verify installation
aliyun plugin list | grep agentexplorer

# Optional: inspect command help
aliyun agentexplorer --help

Authentication

Pre-check: Alibaba Cloud Credentials Required

Security Rules:

  • NEVER read, echo, or print AK/SK values (e.g., echo $ALIBABA_CLOUD_ACCESS_KEY_ID is FORBIDDEN)
  • NEVER ask the user to input AK/SK directly in the conversation or command line
  • NEVER use aliyun configure set with literal credential values
  • ONLY use aliyun configure list to check credential status
aliyun configure list

Check the output for a valid profile (AK, STS, or OAuth identity).

If no valid profile exists, STOP here.

  1. Obtain credentials from Alibaba Cloud Console
  2. Configure credentials outside of this session (via aliyun configure in terminal or environment variables in shell profile)
  3. Return and re-run after aliyun configure list shows a valid profile

RAM Policy

This skill uses read-only APIs from the AgentExplorer service. Required permissions: agentexplorer:ListCategories, agentexplorer:SearchSkills, agentexplorer:GetSkillContent. For the full RAM policy JSON, see references/ram-policies.md.

[MUST] Permission Failure Handling: When any command or API call fails due to permission errors at any point during execution, follow this process:

  1. Read references/ram-policies.md to get the full list of permissions required by this SKILL
  2. Use ram-permission-diagnose skill to guide the user through requesting the necessary permissions
  3. Pause and wait until the user confirms that the required permissions have been granted

For detailed permission information, see references/ram-policies.md.

Core Workflow

Step 1: Understand What They Need

Before searching, identify:

  1. Domain — The relevant area or Alibaba Cloud product family, e.g., ECS, RDS, OSS, SLS, PAI, testing, deployment, data analysis.
  2. Specific task — What the user wants to do, e.g., diagnose ECS issues, sync files to OSS, build a data analysis project, review permissions.
  3. Skill likelihood — Whether this is a common enough task that an existing Skill likely exists.
  4. Category fit — Whether the domain obviously maps to a known category. Do not call list-categories during initial understanding unless the user explicitly asks to browse categories.

Use this understanding to form the search text. --keyword supports both short keywords and full intent phrases. Because search-skills uses semantic matching against Skill descriptions, prefer the user's intent when available, such as 建一个数据分析项目, instead of reducing every request to a single product word.

Before searching, convert this analysis into searchable intent units using Intent Analysis for Search. For compound requests, each meaningful requirement or support need must become its own searchable intent unit and be searched independently.

The Search Phrase must be capability-oriented. It should not simply copy the user's surface wording unless the surface wording already names the capability, product, or service clearly.

If a search phrase is mostly domain-specific labels, document titles, organization-specific terms, policy names, or private/internal terminology, rewrite it toward the underlying capability before searching.

Step 2: Search Skills

Default to semantic intent search for task-matching requests. Use category listing when the user asks to list or browse all Skills under a category.

  • Intent search (default for task matching): Use the user's task or full intent phrase as --keyword, with --search-mode semantic.
  • Keyword search: Use concise product/task keywords with --search-mode semantic when the intent is broad, noisy, or already names a product/capability.
  • Category browsing: Call list-categories when the user asks for available categories or when a category code must be confirmed.
  • List skills in a category: When the user asks to list all Skills in a category, use --category-code only. Do not pass --keyword or --search-mode semantic; this mode supports pagination.
  • Combined semantic search: After category selection, use both --keyword and --category-code with --search-mode semantic only when the user asks for best matches inside that category.

Choose one command shape based on the user request. Use --search-mode semantic for intent, keyword, and combined semantic search. Omit --search-mode semantic for category listing so pagination can be used. AgentExplorer calls must use --endpoint 'agentexplorer.aliyuncs.com'. If --search-mode is not shown in aliyun agentexplorer search-skills --help, install or update the agentexplorer plugin from the Installation section.

# Intent search (default for task matching)
aliyun agentexplorer search-skills \
  --keyword "<user-intent>" \
  --search-mode semantic \
  --max-results 20 \
  --endpoint 'agentexplorer.aliyuncs.com' \
  --user-agent AlibabaCloud-Agent-Skills/alibabacloud-find-skills

# Keyword search
aliyun agentexplorer search-skills \
  --keyword "<product-or-task-keyword>" \
  --search-mode semantic \
  --max-results 20 \
  --endpoint 'agentexplorer.aliyuncs.com' \
  --user-agent AlibabaCloud-Agent-Skills/alibabacloud-find-skills

# Get all categories before listing skills in a category
aliyun agentexplorer list-categories \
  --endpoint 'agentexplorer.aliyuncs.com' \
  --user-agent AlibabaCloud-Agent-Skills/alibabacloud-find-skills

# List skills in a category
aliyun agentexplorer search-skills \
  --category-code "<category-code>" \
  --max-results 20 \
  --endpoint 'agentexplorer.aliyuncs.com' \
  --user-agent AlibabaCloud-Agent-Skills/alibabacloud-find-skills

# Fetch the next category page if nextToken is returned
aliyun agentexplorer search-skills \
  --category-code "<category-code>" \
  --max-results 20 \
  --next-token "<next-token-from-previous-response>" \
  --endpoint 'agentexplorer.aliyuncs.com' \
  --user-agent AlibabaCloud-Agent-Skills/alibabacloud-find-skills

# Combined semantic search after category selection
aliyun agentexplorer search-skills \
  --keyword "<user-intent-or-keyword>" \
  --category-code "<category-code>" \
  --search-mode semantic \
  --max-results 20 \
  --endpoint 'agentexplorer.aliyuncs.com' \
  --user-agent AlibabaCloud-Agent-Skills/alibabacloud-find-skills

Step 3: Iterate Until Found

If a searchable intent unit has no clearly covering Skill, or the results are weak, overly generic, or only match surface/domain-specific wording, revise the search phrase and retry automatically before declaring a gap:

  1. Start with the user's full intent phrase when available
  2. Extract direct product/task keywords from the request
  3. Switch between Chinese and English terms ("cloud server" → "ECS", "object storage" → "OSS")
  4. Broaden or simplify keywords (drop qualifiers: "RDS backup automation" → "RDS")
  5. Use list-categories, select the best category, then retry with combined search
  6. Try synonyms or related terms ("instance" → "ECS", "bucket" → "OSS")

Do not conclude "no dedicated Skill exists" until you have tried at least one capability-oriented search phrase for that intent unit.

Repeat until every searchable intent unit has a clearly covering Skill, is covered by a complementary selected Skill, or is confirmed as a known gap. If all attempts fail for an intent unit, inform the user what was tried.

Step 4: View Skill Details (Optional)

Optionally retrieve skill content to verify it matches user intent before installation. This step can be skipped if the search results already provide sufficient information.

aliyun agentexplorer get-skill-content \
  --skill-name "<skill-name>" \
  --endpoint 'agentexplorer.aliyuncs.com' \
  --user-agent AlibabaCloud-Agent-Skills/alibabacloud-find-skills

Step 5: Install Selected Skill(s)

Skip this step when the user only asks to list, browse, compare, or inspect Skills without installation. When installation is requested, execute the installation command for each selected Skill.

# Option A: Using npx skills add
# By default this command is interactive (blocks for user input).
# Recommended: use non-interactive mode to avoid blocking.
#   --agent <client>   Agent client to install for (see references/npx-skills-agents.md)
#   -g                 Install globally (home dir); omit for project-local install
#   -y                 Skip confirmation (requires --agent and -g/-local to be set)
npx skills add aliyun/alibabacloud-aiops-skills \
  --skill <skill-name> \
  --full-depth \
  --agent qwen-code \
  -g -y

# Option B: Using npx clawhub install (OpenClaw ecosystem)
npx clawhub install <selected-skill-name>

Verify each selected Skill appears in the available skills list after installation.

Command Reference

For complete parameter details and search parameter rules, see references/related-commands.md.

Success Verification

After each operation, verify success by checking:

  1. List Categories: Response contains categoryCode and categoryName fields
  2. Search Skills: Response contains skills array with valid skill objects
  3. Get Skill Content: Response contains complete skill markdown content
  4. Install Selected Skill(s): Each selected Skill appears in Claude Code skills list

For detailed verification steps, see references/verification-method.md.

Search Strategies

1. Intent Analysis for Search

Before choosing search text, analyze the user's request into searchable intent units. A searchable intent unit should describe what capability the Skill must provide, not only the user's surface wording.

For each meaningful requirement, identify:

  • Action: What operation is needed, e.g., query, generate, diagnose, deploy, install, validate, transform
  • Object: What the operation applies to, e.g., document, knowledge base, video, script, database, CLI environment
  • Context/source: Where the information or resource comes from, e.g., internal docs, cloud service, local file, OSS, database, runtime environment
  • Expected output: What the user expects back, e.g., answer with citations, generated script, report, command guidance, installed dependency
  • Support needs: Whether the request also needs credentials, plugins, permissions, runtime dependencies, environment checks, or troubleshooting

Treat explicit support, blocker, and fallback clauses as searchable intents, even when they are conditional. This includes requirements about setup, access, authorization, credentials, dependencies, runtime environment, plugins, connectivity, validation, troubleshooting, remediation, or handling errors that may occur during execution. Do not drop these clauses just because they are not the primary business goal; if they may require a separate Skill, search them independently.

Then form one or more searchable intent phrases using:

<action> + <object/capability> + <context/source> + <expected output>

For compound requests, create one searchable intent unit per meaningful requirement and search each unit independently. Do not assume one Skill covers the whole request unless the search result clearly states that it does.

A single searchable intent unit may still require multiple complementary Skills. When one Skill covers the main action but another Skill is needed for supporting needs such as credentials, plugins, runtime setup, permissions, data access, or validation, select both and explain their roles separately.

2. Search Text Selection

  • Use intent phrases first: Prefer the user's natural-language task or requirement, e.g., "建一个数据分析项目", "把本地文件同步到 OSS"
  • Use product/task keywords when intent is broad or noisy: Extract concise product and action terms, e.g., "ECS 诊断", "OSS 同步"
  • Use product codes as fallback or refinement: ecs, rds, oss, slb, vpc
  • Use Chinese and English variants: e.g., "云服务器" / "ECS", "对象存储" / "OSS"
  • Use broader terms only after specific intent searches fail: e.g., "compute", "storage", "network"

3. Category Filtering

  • Browse when needed: Use list-categories when the user asks about categories or when the domain should narrow the search
  • Select the best category: Map the domain to the closest categoryCode, then use it in --category-code
  • Combine with intent: For clear tasks inside a clear domain, use the task phrase as --keyword and the selected category as --category-code

4. Result Optimization

  • Start with intent: Begin with the user's task description, then add category filtering only when the domain is clear or initial results are too broad
  • Keep complementary Skills together: If one Skill handles the main task and another handles required setup, access, validation, or troubleshooting, include both instead of choosing only the top-ranked main Skill
  • Check install counts: Popular skills usually have higher install counts
  • Read descriptions: Match skill description to your specific use case

5. When No Results Found

# Strategy 1: Try the full user intent
# Instead of just "OSS", try "把本地文件同步到 OSS"

# Strategy 2: Extract product/task keywords
# Instead of "云服务器故障排查", try "ECS 诊断"

# Strategy 3: Try Chinese and English variants
# Instead of "云服务器" try "ECS" or "instance"

# Strategy 4: Use broader terms
# Instead of "RDS backup automation" try just "RDS" or "database"

# Strategy 5: Browse or filter by category
aliyun agentexplorer list-categories \
  --endpoint 'agentexplorer.aliyuncs.com' \
  --user-agent AlibabaCloud-Agent-Skills/alibabacloud-find-skills

aliyun agentexplorer search-skills \
  --keyword "ECS 实例管理" \
  --category-code "<selected-category-code>" \
  --search-mode semantic \
  --max-results 20 \
  --endpoint 'agentexplorer.aliyuncs.com' \
  --user-agent AlibabaCloud-Agent-Skills/alibabacloud-find-skills

6. Display Results to Users

When presenting search results, format as table:

Found N skills:

| Skill Name | Display Name | Description | Category | Install Count |
|------------|--------------|-------------|----------|---------------|
| alibabacloud-ecs-batch | ECS Batch Operations | Batch manage ECS instances | Computing > ECS | 245 |
| ... | ... | ... | ... | ... |

Include:

  • skillName: For installation and detailed queries
  • displayName: User-friendly name
  • description: Brief overview
  • categoryName + subCategoryName: Classification
  • installCount: Popularity indicator

Cleanup

This skill does not create any resources. No cleanup is required.

Best Practices

  1. Verify credentials first — Use aliyun configure list before AgentExplorer operations
  2. Choose the right search mode — Use semantic intent or keyword search for task matching; use category listing without --search-mode semantic when the user asks to list all Skills in a category
  3. Search by intent units — Split compound requests into meaningful capability and support needs, then search each unit independently
  4. Refine weak results — If results only match surface wording or miss an intent unit, rewrite the phrase toward the underlying capability and retry before declaring a gap
  5. Keep complementary Skills together — Select multiple Skills when one covers the main task and another covers required setup, access, validation, troubleshooting, or runtime support
  6. Display results clearly — Use tables with skillName, display name, category, description, and install count
  7. Install only when requested — Do not install for list-only, browse-only, or compare-only requests
  8. Verify before installation — Use get-skill-content when search results are not sufficient to confirm fit
  9. Verify after installation — Confirm every selected Skill is available after installation

Common Use Cases & Examples

For examples, see references/search-examples.md.

Reference Documentation

| Reference | Description | | ---------------------------------------------------------------------------- | -------------------------------------------- | | references/ram-policies.md | Detailed RAM permission requirements | | references/related-commands.md | Complete CLI command reference | | references/verification-method.md | Success verification steps for each workflow | | references/cli-installation-guide.md | Alibaba Cloud CLI installation guide | | references/acceptance-criteria.md | Testing acceptance criteria and patterns | | references/category-examples.md | Common category codes and examples | | references/search-examples.md | Common search workflow examples | | references/npx-skills-agents.md | Supported --agent values for npx skills add |

Troubleshooting

Error: "failed to load configuration"

Cause: Alibaba Cloud CLI not configured with credentials.

Solution: Follow authentication section above to configure credentials.

Error: "Plugin not found"

Cause: agentexplorer plugin not installed.

Solution:

aliyun plugin install --names agentexplorer
aliyun agentexplorer version

No Results Returned

Cause: Search mode, search phrase, or category code does not match the user's request.

Solutions:

  1. For semantic intent search, rewrite the phrase toward the underlying capability instead of repeating private/internal wording
  2. Try Chinese and English variants, product codes, and concise product/task keywords
  3. For weak semantic results, retry with a selected --category-code and --search-mode semantic
  4. For category listing, verify the categoryCode with list-categories, omit --keyword and --search-mode semantic, and use --next-token when pagination is returned
  5. Declare a gap only after each searchable intent unit has been retried with at least one capability-oriented phrase

Notes

  • Read-only operations: This skill only performs queries, no resources are created
  • Credential check first: Follow the Authentication section before AgentExplorer operations
  • Multi-language support: Keywords support both English and Chinese
  • Regular updates: Skills catalog is regularly updated with new skills
  • Community skills: Some skills may be community-contributed, check descriptions carefully