跳到主内容
智客 ZICQ

技能库 智客分类:Agent 工作流 skills-cli

Skills Cli

当用户要求发现,安装,列表,检查,更新,去除,备份,恢复,同步,或初始化代理技能时使用,提及"bunx swills","npx swills","chills.sh",或"chills-lock.json",询问"为X找到技能",或想要帮助扩展具有可安装技能的代理能力.

13 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

当用户要求发现,安装,列表,检查,更新,去除,备份,恢复,同步,或初始化代理技能时使用,提及"bunx swills","npx swills","chills.sh",或"chills-lock.json",询问"为X找到技能",或想要帮助扩展具有可安装技能的代理能力.

何时用

当用户 :

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Overview、When to Use、Discovery Workflow、Installation Quick Reference、Common sources、GitHub shorthand。 其中含规范建议的小节:分步指令。

文件分析

文件分析:这是一份仅含 SKILL.md 的指令型技能,代理激活后整份正文进入上下文。

官方 description(原文)

Use when users ask to discover, install, list, check, update, remove, back up, restore, sync, or initialize Agent Skills, mention `bunx skills`, `npx skills`, `skills.sh`, or `skills-lock.json`, ask "find a skill for X", or want help extending agent capabilities with installable skills.

OverviewWhen to UseDiscovery WorkflowInstallation Quick ReferenceCommon sourcesGitHub shorthandFull GitHub URLDirect path to one skill inside a repoGitLab URLAny git URLLocal package pathCommon install patterns

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
skills-cli
description
Use when users ask to discover, install, list, check, update, remove, back up, restore, sync, or initialize Agent Skills, mention `bunx skills`, `npx skills`, `skills.sh`, or `skills-lock.json`, ask "find a skill for X", or want help extending agent capabilities with installable skills.
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「skills-cli」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-e073a5fb5797d179-%E6%8A%80%E8%83%BD-Cli-%E8%AF%AD%E8%A8%80.html
请存为 .cursor/skills/skills-cli/SKILL.md 或 .claude/skills/skills-cli/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/xixu-me/skills' --list

npx skills add 'https://github.com/xixu-me/skills' --skill 'skills-cli'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版
--- name: skills-cli description: Use when users ask to discover, install, list, check, update, remove, back up, restore, sync, or initialize Agent Skills, mention `bunx skills`, `npx skills`, `skills.sh`, or `skills-lock.json`, ask "find a skill for X", or want help extending agent capabilities with installable skills. --- Use this skill to help users work with the open Agent Skills ecosystem through the `skills` CLI. ## Overview The `skills` CLI is the package manager for installable Agent Skills. Use it to discover skills, install them with the right flags, and manage them after installation. Examples below use `bunx skills`, but `npx skills` is the same workflow if Bun is not available in the user's environment. Always prefer the current CLI syntax: ```bash bunx skills add --skill ``` Do not use older `owner/repo@skill-name` examples. ## When to Use Use this skill when the user: - asks "find a skill for X", "is there a skill for X", or "how do I do X" and X sounds like a reusable workflow - asks "can you do X" and X sounds like a specialized capability that may already exist as a skill - wants help with `bunx skills`, `npx skills`, `skills.sh`, skill package installation, or `skills-lock.json` - wants to install a skill for a specific agent such as Codex or OpenCode - wants to list, check, update, remove, restore, sync, back up, or initialize installed skills - wants help searching for workflows, tools, templates, or domain-specific capabilities such as design, testing, deployment, documentation, or code review Do not use this skill when the user already has a local skill and wants help writing or improving its contents. In that case, use a skill-authoring workflow instead. ## Discovery Workflow When a user needs a skill, follow this sequence: 1. Identify the domain and task. Examples: React performance, PR review, changelog generation, PDF extraction. Also judge whether the task is common enough that a reusable skill is likely to exist. 2. Check [skills.sh](https://skills.sh/) first. Prefer well-known, well-installed skills when the domain is already covered there. 3. If the leaderboard does not clearly answer the need, search with: ```bash bunx skills find ``` 1. Verify quality before recommending anything: - install count: prefer skills with 1K+ installs and be cautious with anything under 100 - source reputation: prefer official or well-established maintainers such as `openai`, `anthropics`, `microsoft`, or similarly trusted publishers - repository quality: check the source repository and treat skills from repos with fewer than 100 stars skeptically 2. Present the options clearly. Include the skill name, what it helps with, the install count and source, why it looks trustworthy, the install command, and a link to learn more on `skills.sh`. 3. Offer installation help if the user wants to proceed. 4. If nothing fits, say so directly, help with the task using your general capabilities, and mention that the user can create their own package with `bunx skills init`. ## Installation Quick Reference ### Common sources ```bash # GitHub shorthand bunx skills add xixu-me/skills # Full GitHub URL bunx skills add https://github.com/xixu-me/skills # Direct path to one skill inside a repo bunx skills add https://github.com/xixu-me/skills/tree/main/skills/skills-cli # GitLab URL bunx skills add https://gitlab.com/org/repo # Any git URL bunx skills add [email protected]:owner/repo.git # Local package path bunx skills add ./my-local-skills ``` ### Common install patterns ```bash # List skills in a package without installing bunx skills add --list # Install one skill bunx skills add --skill skills-cli # Install multiple skills bunx skills add --skill pr-review --skill commit # Install globally bunx skills add --skill skills-cli -g -y # Install to a specific agent bunx skills add --skill skills-cli -a codex -y # Install all skills to all agents bunx skills add --all # Install all skills to one agent bunx skills add --skill '*' -a codex -y # Copy files instead of symlinking bunx skills add --skill skills-cli -a codex --copy -y ``` ### Installation methods When the user is choosing how to install: - symlink is the default and usually the best choice because updates stay centralized - `--copy` creates independent copies and is the fallback when symlinks are unsupported or inconvenient If the user only asks to install a skill, prefer the default symlink workflow unless they mention CI packaging, portability, filesystem restrictions, or explicitly ask for copies. ### Important flags | Flag | Use | | --------------------- | ---------------------------------------------- | | `--skill ` | install one or more named skills | | `-a, --agent ` | target specific agents such as `codex` | | `-g, --global` | install at user scope instead of project scope | | `-y, --yes` | skip prompts | | `--list` | list available skills in a package | | `--copy` | copy instead of symlink | | `--all` | shorthand for all skills to all agents | ## Managing Installed Skills Use these commands for ongoing maintenance: ```bash # List installed skills bunx skills ls bunx skills ls -g bunx skills ls -a codex bunx skills ls --json # Check for updates bunx skills check # Update installed skills bunx skills update # Remove installed skills bunx skills remove my-skill bunx skills remove my-skill -a codex bunx skills remove -g my-skill bunx skills remove --all # Initialize a new skill package bunx skills init bunx skills init my-skill # Restore from skills-lock.json bunx skills experimental_install # Sync node_modules skills into agent directories bunx skills experimental_sync bunx skills experimental_sync -a codex -y ``` When the user asks to initialize a skill, explain whether they want: - `bunx skills init` to create `SKILL.md` in the current directory - `bunx skills init ` to create a new subdirectory containing `SKILL.md` ## Related Tool: Skills Vault If the user wants declarative backup and restore of installed skills across machines or teams, use [Skills Vault](https://github.com/xixu-me/skills-vault). Skills Vault is a separate CLI companion for the `skills` ecosystem. It is not a `skills add` installable skill source. Use it when the user wants to snapshot installed skills into a manifest, preview restore commands, or reproduce the same setup elsewhere. Common companion commands: ```bash # Back up installed skills into skvlt.yaml bunx skvlt backup # Preview a restore bunx skvlt restore --dry-run # Restore everything from the manifest bunx skvlt restore --all # Diagnose the local environment bunx skvlt doctor ``` Prefer this tool over `skills experimental_*` when the user explicitly wants a portable manifest workflow, cross-machine backup and restore, or team-sharing of installed skill setups. ## Recommendation Format When recommending a skill, keep the answer concrete and installable. Use a structure like this: ```text I found a skill that should fit. Skill: Why it matches: Source: Quality check: Install: bunx skills add --skill [optional flags] Learn more: https://skills.sh/// If you want, I can install it for . ``` If the user mentions a target agent or scope, include it in the command. Examples: ```bash bunx skills add --skill -a codex -y bunx skills add --skill -g -y ``` Example: ```text I found a skill that might help. Skill: screenshot Why it matches: it focuses on OS-level desktop and window screenshot capture. Source: openai/skills Quality check: high install volume, trusted publisher, and a widely used source repository. Install: bunx skills add openai/skills --skill screenshot Learn more: https://skills.sh/openai/skills/screenshot ``` ## Common Skill Categories When the user's wording is vague, map it to likely 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` | ## Search Tips - Use specific keywords. `react testing` is better than just `testing`. - Try alternative terms. If `deploy` fails, try `deployment` or `ci-cd`. - Check popular sources first. Many strong skills come from established publishers. - If the first search is too broad, narrow by domain plus task. ## Common Mistakes - Recommending a skill from search results without checking whether it looks established. - Forgetting to specify `-a ` when the user asked for one particular agent. - Treating `bunx skills find --help` like a real help command. Use `bunx skills --help` for command help instead. - Assuming no skill exists after one weak search term. Try a more specific or adjacent query first. ## Troubleshooting If the user hits an error or confusing result: - "No skills found" - suggest a better query, check [skills.sh](https://skills.sh/), or help directly and mention `bunx skills init` - interactive prompts in automation or CI - add `-y` - wrong installation scope - switch between project install and `-g` - symlink issues - retry with `--copy` - uncertainty about available package contents - run `bunx skills add --list` - uncertainty about installed state - run `bunx skills ls` or `bunx skills ls --json` - portable backup or restore across machines - mention [Skills Vault](https://github.com/xixu-me/skills-vault) and its `backup` / `restore --dry-run` workflow When you are unsure about exact flags, use: ```bash bunx skills --help ```

相关技能

Agent 工作流

Skill Creator

创造有效技能指南。 当用户想创造出新的技能(或更新现有的技能),以专业知识,工作流程,或工具集成来扩展克洛德的能力时,应该使用这种技能.

Agent 工作流

Clawdhub

使用ClawdHub CLI搜索,安装,更新并发布从taladhub.com的代理技能. 需要获取苍蝇上的新技能时使用,将安装的技能同步到最新版本或特定版本,或者发布 npm-instainddhub CLI 的新/更新的技能文件夹.

Agent 工作流

Agent Team Orchestration

管弦乐团多代理团队,任务设定周期,交接协议,审查工作流程. 使用时间: (1)建立2+特派员队伍,具有不同专业,(2)确定任务路线和生命周期(收录框_ spec_建设_审查_完成),(3)在特派员之间制定交接协议,(4)建立审查和质量关口,(5)管理特派员之间的交流和文物共享.

Agent 工作流

Superpowers

Spec-first,TDD,子代理驱动的软件开发工作流程. 当:(1)构建任何新功能或应用——触发脑暴_计划_子代理执行回路,(2)调试出一个bug或测试失败——触发系统性的根起过程,(3)用户说"让我们构建","帮助我计划","我想添加X",或"这个被打破",(4)完成一个功…