skilld CLI
The command-line client of the skilld.dev registry that installs agent skills into a project and tracks their changes
- 328 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The install command writes skill files into the project and agent directories, and skills carry instructions the agent will follow
- The client checks for and offers upgrades itself, and the curl script install edits PATH in the shell profile
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/skilldDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The install command writes skill files into the project and agent directories, and skills carry instructions the agent will follow
- The client checks for and offers upgrades itself, and the curl script install edits PATH in the shell profile
This is third-party code. Review the repository files before installing.
What it does
skilld is an open-source Rust CLI behind the skilld.dev registry. A skill here is a directory with a SKILL.md file in the Agent Skills format. The site names the author, links the exact file and records the commit the skill came from, so you can read the instructions before an agent follows them. Work goes in four steps. `skilld search` and `skilld trending` help find a skill. `skilld run` prints SKILL.md to standard output and writes nothing to disk, which suits a one-off task. For lasting use, `skilld install` puts a skill into the project and into the directories of chosen agents, from Claude Code to Zed. `skilld watch` and `skilld changes` track changes, and `skilld update` refreshes what is installed. The CLI itself generates no skills and has no agent runtime. The easiest path is to install the skilld skill once with `npx skilld install skilld --global` and ask the agent: "find me a skill for reviewing my Vue app". The agent finds and loads a fitting one itself. There is also a Claude Code plugin: it installs the skills maintained by the skilld team and adds the registry's MCP server. The server searches for skills and returns run and install commands but never runs a skill.
Who it is for. For people who give their agents third-party skills and want to check them before installing and hear about updates.
Good fit when
- You want to see which skills people discuss this week: skilld trending and skilld search
- You want to apply a skill to a single task: skilld run
- The same skill is needed in every session of a project: skilld install with version pinning in the lockfile
- You need to know whether the skills you use have changed: skilld watch and skilld changes
- You need to install one skill for several agents: the --agent all flag
Not a fit when
- You want to generate a new skill: the CLI has no generation logic, and separate authoring skills exist for that
- You need skill scripts to execute on run: skilld run never prints or executes them
- You cannot reach skilld.dev: the client relies on the registry
Example request
Find a skill for reviewing a Vue app in skilld, show the author and the file link, then run it on the current task without installing.Limitations
Installing writes files: the .skills directory, the lockfile and agent directories. If an agent runs the install, it must ask you first. Skill scripts are never printed or executed by `skilld run`. Signing in is needed for change tracking and the monthly change digest. Whether the registry is reachable from Russia was not checked for this card. The client checks for updates once a day and offers an upgrade; `SKILLD_NO_UPGRADE=1` turns that off.
How to disable. Skills are removed with skilld remove. The client itself is removed the way it was installed: npm uninstall --global skilld, or by deleting ~/.skilld/bin and the PATH line from the shell profile. For the Claude Code plugin disable it in the /plugin menu.
FAQ
How does skilld run differ from skilld install?
`skilld run` prints SKILL.md, writes no files and loads the source anew each time. `skilld install` writes the skill into the project with a pinned version, updates with `skilld update` and is removed with `skilld remove`.
How do I install skilld on my computer?
On macOS and Linux run curl -fsSL https://skilld.dev/install.sh | sh, in Windows PowerShell irm https://skilld.dev/install.ps1 | iex, or npm install --global skilld. The script installs one native executable in ~/.skilld/bin and verifies the signed release manifest.
How do I install skilld in Claude Code as a plugin?
Run /plugin marketplace add skilld-dev/skilld and /plugin install skilld@skilld. The plugin installs the skilld team's skills and adds the registry MCP server.
Does skilld collect telemetry?
No. The CLI sends no analytics and keeps account credentials in the operating system keychain.
What is an owner/repository/skill selector?
It is how the registry names a skill. In the selector `antfu/skills/vue` the first two parts point to the repository and the last one to the skill directory inside it. A two-part selector means every skill in the repository, and `skilld search` prints selectors.
Discussion
No questions or reviews yet.
Related
CLI toolsskills (npx skills)
skills
A skill package manager: installs, finds, updates and removes SKILL.md packages from GitHub and other git hosts across many agents
A skill that helps an agent author other skills to the agentskills.io spec: structure, metadata, progressive disclosure and validation
A desktop app and CLI to install, sync and organize agent skills across Claude Code, Codex, Cursor and other tools
A CLI and MCP server for Agent Skills: spec validation, installs from GitHub and on-demand loading of the right skill
A Go terminal UI for agent skills: list, check, update and find new ones in a single window
A CLI skill manager for AI agents: install from repositories, translate between agent formats and deploy into their configs
README in short
The description opens with a description of the registry and a table of four steps. It continues with installing the client and plugin, an explanation of owner/repository/skill selectors and run and install details. Much of the text deals with signature checks, updates and security.