shield_lock
金大哥
联系我们
← 返回 Skill 列表
extension
分类: 其它无需 API Key

pptx

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

person作者: user_c0d57d10hubcommunity
download下载资源包

Find Skills

This skill helps you discover and install skills from the open agent skills ecosystem.

When to Use This Skill

Use this skill when the user:

  • Asks "how do I do X" where X might be a common task with an existing skill
  • Says "find a skill for X" or "is there a skill for X"
  • Asks "can you do X" where X is a specialized capability
  • Expresses interest in extending agent capabilities
  • Wants to search for tools, templates, or workflows
  • Mentions they wish they had help with a specific domain (design, testing, deployment, etc.)

What is the Skills CLI?

The Skills CLI (npx skills) is the package manager for the open agent skills ecosystem. Skills are modular packages that extend agent capabilities with specialized knowledge, workflows, and tools.

Key commands:

  • npx --yes skills find [query] - Search for skills interactively or by keyword
  • npx --yes skills add <package> -y - Install a skill from GitHub or other sources
  • npx --yes skills check - Check for skill updates
  • npx --yes skills update - Update all installed skills

Browse skills at: https://skills.sh/

How to Help Users Find Skills

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 the find command with a relevant query:

npx --yes skills find [query]

For example:

  • User asks "how do I make my React app faster?" → npx --yes skills find react performance
  • User asks "can you help me with PR reviews?" → npx --yes skills find pr review
  • User asks "I need to create a changelog" → npx --yes skills find changelog

The command will return results like:

Install with npx --yes skills add <owner/repo@skill> -y

vercel-labs/agent-skills@vercel-react-best-practices
└ https://skills.sh/vercel-labs/agent-skills/vercel-react-best-practices

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 install command they can run
  3. A link to learn more at skills.sh

Example response:

I found a skill that might help! The "vercel-react-best-practices" skill provides
React and Next.js performance optimization guidelines from Vercel Engineering.

To install it:
npx --yes skills add vercel-labs/agent-skills@vercel-react-best-practices -y

Learn more: https://skills.sh/vercel-labs/agent-skills/vercel-react-best-practices

Step 4: Offer to Install

If the user wants to proceed, install the skill for them:

npx --yes skills add <owner/repo@skill> -y

IMPORTANT: Both --yes and -y flags are REQUIRED. --yes tells npx to auto-install the skills package without prompting. -y tells the skills CLI to skip interactive agent selection. Without either flag, the command will hang in the sandbox environment. Always include both when running npx skills add.

Step 5: Package as .skill File

After installation, package the skill into a .skill file so it can be added to the skill library:

(cd .agents/skills && zip -r /tmp/<skill_name>.skill <skill_name>/) && mv /tmp/<skill_name>.skill .

Replace <skill_name> with the actual skill directory name (e.g., pptx).

After packaging, the .skill file will appear in the current working directory. The user can then click it in the workspace file panel and use the "添加到技能" button to import it into their personal skill library.

Common Skill Categories

When searching, consider these common categories:

| Category | Example Queries | | --------------- | ---------------------------------------- | | Web Development | react, nextjs, typescript, css, tailwind | | Testing | testing, jest, playwright, e2e | | DevOps | deploy, docker, kubernetes, ci-cd | | Documentation | docs, readme, changelog, api-docs | | Code Quality | review, lint, refactor, best-practices | | Design | ui, ux, design-system, accessibility | | Productivity | workflow, automation, git |

Tips for Effective Searches

  1. Always use English keywords: The skills ecosystem is English-based. Translate user queries to English before searching. For example, if the user says "小红书", search for "xiaohongshu"; if they say "PPT生成", search for "pptx" or "presentation".
  2. Use specific keywords: "react testing" is better than just "testing"
  3. Try alternative terms: If "deploy" doesn't work, try "deployment" or "ci-cd"
  4. Check popular sources: Many skills come from vercel-labs/agent-skills or ComposioHQ/awesome-claude-skills
  5. One search at a time: Run a single npx --yes skills find command per attempt. Do NOT chain multiple searches with || or && — it can cause incorrect results.

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 the user could create their own skill with npx skills init

Example:

I searched for skills related to "xyz" but didn't find any matches.
I can still help you with this task directly! Would you like me to proceed?

If this is something you do often, you could create your own skill:
npx --yes skills init my-xyz-skill