← ClaudeAtlas

skills-clilisted

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.
aiskillstore/marketplace · ★ 329 · AI & Automation · score 79
Install: claude install-skill aiskillstore/marketplace
# Skills CLI 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 <source> --skill <name> ``` 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. Id