get-skill@1.3.11

• Repository links point at github.com/skillmds/SkillMD, the repo's new name: the package metadata, the MCP registry manifest and the READMEs. The old address still redirects. This also lets npm's provenance view resolve the source commit, and brings skillmds back in step with get-skill.

get-skill@1.3.10

• find-skills is now find-a-skill. SkillMD's skill-finder shared its name with Vercel's widely installed find-skills, and both go into the same ~/.agents/skills folder, so for anyone who already had Vercel's the offer after an install could only fail. It is now skillmd/find-a-skill, the old skillmd/find-skills address redirects to it, and an earlier install under the old name counts as already added.
• A failed follow-up install says why. When the find-a-skill offer can't install, the message gives the reason (for example a folder already in the way) instead of "try later", along with the command to add it yourself.

get-skill@1.3.9

• A new look. npx get-skill on its own now opens with the SkillMD logo, its two orange squares dropping into place, and the menu right under it. Any key skips the animation, which takes under a second.
• Brand colours throughout. Every question, picker and confirmation uses the SkillMD orange instead of cyan. Pickers show a one-line key reminder (↑/↓ to move · enter to choose, space to select · enter to confirm). Success is still green, warnings yellow and errors red.
• Loading lines made from the logo's squares. Fetching a skill, searching, installing, updating, checking and publishing each show a small animation built from the two squares while they wait. search, info, update, check and publish show it on stderr and erase it when done, so their output is unchanged.
• Quiet where it should be. Nothing animates in CI, when output is piped, with --json, or when an agent runs the CLI. With colour turned off (NO_COLOR) the logo prints plain. Consoles without block characters get the previous ASCII spinner.
• Prompts now run on @clack/core directly, in place of @clack/prompts.

get-skill@1.3.8

• Skills install all their files. add, update and the MCP install tool now fetch every registry skill's bundle, not only skills marked as packs. Some skills were recorded as single-file while carrying scripts or references, and installed only their SKILL.md. A single-file skill whose bundle can't be reached still installs from its SKILL.md, as before.

get-skill@1.3.7

• The package is now get-skill. Install and run it as npx get-skill add owner/name, npx get-skill search "pdf", and so on; MCP clients start the server with npx -y get-skill. npm i -g get-skill installs the get-skill and skillmd commands. Every release is still published as skillmds too, with identical contents, so existing setups keep working.

skillmds@1.3.6

• Installed skills name where they came from. A skill installed from the registry (with add, update or the MCP install tool) gets one line in its frontmatter, metadata.source: https://skillmd.com/skills/<owner>/<name>, so an agent reading it knows its SkillMD page. Every other byte is the author's: an existing metadata block gains that one line, and an author's own metadata.source is never replaced. The line is added after the integrity checks, and the lock file's digest still covers the bytes the registry served, so update is unaffected. GitHub, gist and local installs are written exactly as fetched.
• find-skills, offered once. After your first successful install in a terminal, add asks once whether to also add skillmd/find-skills, a skill that tells your agent to look on SkillMD when a task needs know-how it doesn't have, and to vet what it finds before suggesting it. Yes or no, it never asks again; an agent running the CLI, -y and --json are never asked.

skillmds@1.3.5

• The agent picker now says why Claude Code isn't in it. add plugin:owner/slug installs the plugin into Claude Code as a real plugin first, then asks which other agents should get its skills, leaving Claude Code out so it doesn't get the same skills twice. The question read "Which agents do you want to install to?", and the confirmation only printed after the run, so the list looked as if Claude Code hadn't been detected. It now asks: Claude Code already has <plugin> as a plugin. Which other agents should get its skills too?

skillmds@1.3.4

• A companion file that its source repo no longer serves no longer fails the install. When a registry pack links to a file the upstream repo has since deleted or moved, add (and the MCP install tool) now installs everything else and warns which files are missing, e.g. 1 companion file is gone from the source repo and was not installed (scripts/gone.ts). Before, one such link failed the whole bundle and add owner/name fell back to fetching the slug as a GitHub repo, ending in a misleading 404 with nothing installed. update stays strict: it never replaces a full install with a partial one.

@skillmds/core@1.0.1

• slugify no longer ends in a hyphen when the 60-character cut lands right after a word break ("…-informacion-reading-" → "…-informacion-reading"). A slug's name becomes the installed folder and the skill's name, and the Agent Skills spec rejects a name ending in a hyphen.

skillmds@1.3.3

See CHANGELOG.md