# How to Get the Latest Version of Leonxlnx/taste-skill: 3 Methods Explained > Discover three easy methods to get the latest Leonxlnx/taste-skill: clone from GitHub, download a tarball, or use npx skills add for instant updates. - Repository: [Leon Lin/taste-skill](https://github.com/Leonxlnx/taste-skill) - Tags: how-to-guide - Published: 2026-05-26 --- **Pull the source directly from the GitHub `main` branch using `git clone`, download a tarball, or run `npx skills add` to automatically fetch the freshest skill definitions at runtime.** The **Leonxlnx/taste-skill** repository is the canonical source for design-oriented skill definitions used by the taste-skill CLI. Because the project is under active development on the `main` branch, you should get the latest version of Leonxlnx/taste-skill directly from the source rather than waiting for packaged releases. Each method below provides a different balance between convenience and control, depending on whether you need the full repository history or just the current skill files. ## Method 1: Clone the Repository for Full Source Access Cloning gives you the complete development history, examples, and research material alongside the skill definitions. Run the following commands to clone the repository and optionally keep it synchronized: ```bash # Clone the repo to get the latest commit on the main branch git clone https://github.com/Leonxlnx/taste-skill.git cd taste-skill # Keep your local copy updated git pull origin main ``` **Why this works:** The `main` branch contains the current production-ready code. Running `git clone` creates a local replica of this branch, and `git pull origin main` fast-forwards your copy whenever new commits land. According to the repository source code, the root **README.md** describes this workflow as the standard way to inspect the full project structure. ## Method 2: Download a Tarball or ZIP Archive For environments where installing Git is not possible, fetch a snapshot of the current `main` branch as a compressed archive. ```bash # Download and extract the latest tarball without Git history curl -L https://github.com/Leonxlnx/taste-skill/archive/refs/heads/main.tar.gz | tar -xz cd taste-skill-main ``` **When to use this:** Static snapshots are ideal for CI/CD pipelines or air-gapped machines that only need a one-time copy of the `skills/` directory. GitHub automatically generates these archives at `https://github.com///archive/refs/heads/.tar.gz`, ensuring you receive the exact state of the repository at the moment of download. ## Method 3: Install Skills via the Official CLI (Recommended) The most dynamic way to get the latest version is to let the **taste-skill** CLI fetch files for you at runtime. The CLI reads the `skills/` folder directly from the remote URL each time it executes, so you always receive the newest definitions without manual updates. The repository includes a helper script, **[`skill.sh`](https://github.com/Leonxlnx/taste-skill/blob/main/skill.sh)**, that maps skill names to their corresponding [`SKILL.md`](https://github.com/Leonxlnx/taste-skill/blob/main/SKILL.md) files. When you run `npx skills add`, the tool uses this mapping to locate and register individual skills. Install all available skills or a specific one using these commands: ```bash # Add all skills from the repository (fetches latest files each run) npx skills add https://github.com/Leonxlnx/taste-skill # Add a single skill by its install name (the `name:` field in SKILL front-matter) npx skills add https://github.com/Leonxlnx/taste-skill --skill "design-taste-frontend" ``` **Key advantage:** Unlike cloning or downloading, this method does not store a persistent local copy of the repository. The CLI queries the `main` branch on every execution, meaning you automatically benefit from bug fixes and new skill definitions as soon as they are pushed. For implementation details, see the "Installing" section in **README.md** and the mapping logic in **[`skill.sh`](https://github.com/Leonxlnx/taste-skill/blob/main/skill.sh)**. ## Verify You Have the Latest Version After cloning or downloading, confirm you are on the most recent commit: ```bash # Display the current commit hash git rev-parse HEAD # Show the latest commit message and hash git log -1 --oneline ``` If you used the CLI method, inspect the fetched [`SKILL.md`](https://github.com/Leonxlnx/taste-skill/blob/main/SKILL.md) content directly (for example, by running `cat` on the file path returned by the add command) to verify it matches the latest version shown in the GitHub web interface. ## Summary - **Clone the repository** with `git clone https://github.com/Leonxlnx/taste-skill.git` when you need the full source, history, and ability to diff changes locally. - **Download a tarball** via `curl` for a quick, Git-free snapshot of the `main` branch. - **Use `npx skills add`** to dynamically fetch the latest skill definitions from the `skills/` directory at runtime without maintaining a local copy. - **Verify** your version by checking `git rev-parse HEAD` or inspecting the [`SKILL.md`](https://github.com/Leonxlnx/taste-skill/blob/main/SKILL.md) file contents. ## Frequently Asked Questions ### Does Leonxlnx/taste-skill use semantic versioning or release tags? The repository does not rely on traditional semantic versioning tags. Instead, the `main` branch serves as the rolling release channel. The **CHANGELOG.md** file tracks major updates, but the CLI always pulls from the HEAD of `main` to ensure users receive immediate updates. ### How often is the main branch updated? Updates land on `main` as soon as new skill definitions are validated. Because `npx skills add` reads directly from the repository URL at runtime, there is no publish step or release cycle delay—you get changes the moment they are committed. ### Can I pin a specific version instead of using the latest? Yes. While the CLI defaults to the latest commit, you can target a specific Git SHA by appending it to the URL in the `npx skills add` command, or by checking out a specific commit in a cloned repository using `git checkout `. The **[`skill.sh`](https://github.com/Leonxlnx/taste-skill/blob/main/skill.sh)** script resolves skill names against the current state of the repository, so pinning the underlying Git state effectively pins the skill version. ### What is the difference between cloning and using `npx skills add`? Cloning creates a persistent local copy of the entire repository, including all branches, history, and auxiliary files like research documents. Running `npx skills add` performs a transient fetch of only the requested [`SKILL.md`](https://github.com/Leonxlnx/taste-skill/blob/main/SKILL.md) files from the `skills/` directory, discarding them after registration. Choose cloning for development and debugging; choose the CLI for production deployments that always need the freshest definitions.