skillfile CLI
Skill and agent manager with a lock file: installs one set into Claude Code, Codex, Cursor and others and keeps your edits.
- 181 ★ on the repository
- Last commit
- Apache-2.0
Extended access
Why this level
- The installer downloads third-party skills and agents from GitHub, GitLab and URLs and drops them into your coding agent directories.
- GitHub and GitLab tokens can be saved in user config.
Install
- Works in
Manual install
curl -fsSL https://github.com/eljulians/skillfile/releases/latest/download/install.sh | shThe first README command; alternatives are `cargo install --locked skillfile` and `cargo binstall skillfile`.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The installer downloads third-party skills and agents from GitHub, GitLab and URLs and drops them into your coding agent directories.
- GitHub and GitLab tokens can be saved in user config.
This is third-party code. Review the repository files before installing.
What it does
skillfile describes skills and agents in a single `Skillfile`, like project dependencies. Lines set the source: GitHub, GitLab, a local file or a URL. `skillfile install` lays them out in the directories of the chosen tools, and `Skillfile.lock` pins exact revisions so another machine gets the same set. Edits to an installed file are kept as patches: `skillfile pin <name>` records the difference in `.skillfile/patches/`, and `skillfile install --update` pulls the fresh version and applies the patch on top. On a conflict `skillfile diff` shows the divergence and `skillfile resolve` settles the result. `skillfile search` queries the agentskill.sh and skills.sh registries in an interactive window with a preview. Installation targets Claude Code, Codex, Cursor, Copilot, Gemini CLI, Windsurf, OpenCode and a few more clients, plus any directory through `install-path`. No runtime is needed.
Who it is for. Teams and solo developers who keep the same skills across several machines and several coding agents and tweak them locally.
Good fit when
- A work laptop, a home computer and a server need identical skills.
- A shared `Skillfile` lives in the project repository and a new developer installs the set with one command.
- You tweaked someone else skill and the edit vanished when upstream updated.
- One skill has to reach Claude Code, Codex and Cursor at once.
Not a fit when
- You need one skill on one machine and copying a file is enough.
- Skills live in private sources and you have no GitHub or GitLab token.
- You want a graphical shell instead of a command line.
Example request
Add the anthropics/skills skills/slack-gif-creator skill to the Skillfile and install it into Claude Code and Cursor.Limitations
This is a console tool with no GUI. Private repositories need a token: `GITHUB_TOKEN` or `GH_TOKEN` for GitHub, `GITLAB_TOKEN` for GitLab. Building from source needs Rust 1.88 or newer, while prebuilt binaries do not. The `skillhub.club` registry joins only when `SKILLHUB_API_KEY` is set. The same file added twice becomes a separate skill, so check `skillfile list` before `skillfile add`. Patches are tied to upstream content, and large upstream changes mean resolving a conflict by hand.
How to disable. Delete the `skillfile` binary (`cargo uninstall skillfile` or by hand) and the installed skills from the tool directories. Remove `Skillfile`, `Skillfile.lock` and the `.skillfile/` folder from the project.
FAQ
How do I install skillfile?
Use the `install.sh` script from GitHub releases or `cargo install --locked skillfile`. `cargo binstall skillfile` also fetches prebuilt binaries.
Which clients does it install to?
Claude Code, Codex, Cursor, Copilot, Factory, Gemini CLI, Junie, OpenCode, Windsurf and Antigravity. Any other directory is set with an `install-path` line.
How do I keep my edits across updates?
Run `skillfile pin <name>`: the difference goes into `.skillfile/patches/`. After `skillfile install --update` the patch is applied to the new version.
Where do skills come from?
From GitHub, GitLab (including subgroups and a self-hosted server via `GITLAB_HOST`), local files and URLs.
How do I find a skill without a browser?
With `skillfile search "code review"`. A terminal window with a preview opens, and `--json` or `--no-interactive` switch to script mode.
Discussion
No questions or reviews yet.
Related
CLI toolssync-skill copies skill folders with SKILL.md between Claude Code, Codex, Cursor, Gemini CLI, Copilot, VS Code and OpenCode.
skill-kit builds agent skills as typed TypeScript state machines with schema-checked answers and a build into a SKILL.md directory
skills-npm links agent skills shipped in your dependencies in node_modules and listed in the skills field of package.json
Over 1,100 ready-made skills for Claude Code, Codex, Gemini CLI and Cursor, plus an MCP server that picks a skill for the task
skill-creator: skills from OpenAPI, GraphQL and MCP
@asnd/skill-creator
The /skill-creator command turns a link to an OpenAPI spec, GraphQL schema or MCP server into a ready skill with wrappers.
Skill Zoo finds, installs, updates and audits skills for Claude Code, Codex, Cursor and other agents in a window and a CLI.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| skillfile (this card) | no | 181 | |
| Universal Skills Manager | no | 115 | also distributes skills to clients; here a Skillfile with a lock file, patches over upstream and registry search |
| Agent Skill Manager | no | 974 | manages installed skills; here a declarative dependency file, pinned revisions and transfer to other machines |
README in short
The project treats skills and agents as dependencies: a source list, a lock file, patches over upstream and distribution to tools. It also searches shared registries straight from the terminal. The format is described in `SPEC.md`.