Skip to content

feat(skills): ship the reply-adapter skills inside the package and install them from it - #36

Merged
ArtemKosolap merged 4 commits into
mainfrom
REPLY-52328-skills-in-package
Nov 5, 2026
Merged

ArtemKosolap merged 4 commits into
mainfrom
REPLY-52328-skills-in-package

Conversation

@ArtemKosolap

Copy link
Copy Markdown
Contributor

What changed

  • The Reply skills ship inside this package. The five reply-adapter skills (reply-api, reply-auth, reply-cli, reply-mcp, reply-operations-mapping) now live under skills/reply-adapter/ and are published with the package (files gains skills). They move as they stood, byte for byte. Their version is the CLI's own version.
  • The plugin manifests and the catalogue file of the old skills repository do not move: nothing here is a plugin any more.
  • reply skills install and update copy the pack from the installed package into every detected assistant. There is no network, no git and no registry fetch. Claude Code gets ~/.claude/skills, or .claude/skills with --project. Codex gets ~/.agents/skills, or .agents/skills with --project. The other hosts keep their directories.
  • One pack. With no argument the commands mean reply-adapter, and adapter stays an alias. Asking install or update for core, ai-sdr-core, runtime or agentic-runtime exits 2 with one sentence: the SDR expertise and the runtime skills ship with Jason (github.com/reply-team/jason-ai) and are not installed by this CLI. The pack registry, its embedded fallback, the clone path and the git requirement are gone.
  • What earlier versions installed still answers to list and remove. That covers copied packs recorded in the journal under any old name (entries written with a ref and commit still read), and the <pack>@reply-skills plugins on Claude Code and Codex.
    • install and update remove the old reply-adapter@reply-skills plugin through the host's own CLI, and only once the copy that replaces it is in place.
    • The other two old plugins are left installed, and so are copies of the two retired packs an earlier version made in the scope the run acts on. One report line names them, each host with its own.
    • If the removal fails, the copy still lands. The report then says the old plugin still loads beside it and prints the command that removes it.
  • reply skills list prints each pack with the version on disk in the human report too.
  • For --json consumers: the report's source member changes shape from {repo, ref, commit} to {version}, the CLI version the pack was copied at; a host outcome no longer carries a commit. On list and remove with no pack named, requested and resolved now also carry the retired names ai-sdr-core and agentic-runtime. On install and update, a host outcome may carry retired_packs, the retired packs an earlier version copied there, beside retired_plugins. Journal entries are written without ref and commit; entries an earlier version wrote with them still read.
  • The README presents the one pack and how it moves with the CLI (reply install, then reply skills update). It also gives the copied-file paths for Claude Code and Codex, and says that the operation catalogue and the runtime skills live in Jason (skills/business). The separate skills repository is no longer presented.

Why

The skills that teach an agent to use this CLI now ship and version with it. An install can no longer pick up skills that disagree with the CLI on the machine, and it needs nothing beyond the package. The vendor-neutral SDR skills are maintained with Jason.

On Claude Code the skills were plugin skills and are now standalone skills, so the reply-adapter: prefix on their names goes away. The alternative kept the plugin by registering a local-path marketplace inside the installed package. It was not taken: it ties each host to the path of one Node installation, it dangles after a version-manager switch or an uninstall, and it has not been verified for Codex.

Directories, from the vendors' pages

How it was verified

  • Unit and package tests. npm run build and npm test pass: 61 files, 935 tests, 5 skipped.
    • A new package test checks with npm pack --dry-run that every skill file is published.
    • It checks that the source and built layouts both find the pack, and that install, update, list and remove work offline against the package's own files, the copy byte for byte.
    • Every changed behaviour was seen failing first. The journal row of the earlier shape holds a tolerance the reader already had.
  • End to end with real Claude Code 2.1.318 on Windows, under a throwaway home, config directory and working directory. The CLI ran from a source build, so these runs show its version as 0.0.0-development; the unit rows hold that the pack is copied and journaled at the CLI's own version:
    • reply skills install copied the five skills into .claude/skills. It also copied them into .agents/skills for a Codex config directory whose binary was not on the PATH.
    • reply skills list then printed reply-adapter <version> already current for both, and --json carried the same version.
    • reply skills install core exited 2 with the sentence above.
  • End to end from the old plugins, under a second throwaway home:
    • The old marketplace was added and reply-adapter@reply-skills was installed through claude plugin install, which also brought in ai-sdr-core@reply-skills.
    • reply skills install replaced the plugin with the copy, reported that, and named ai-sdr-core@reply-skills as staying.
    • claude plugin list --json afterwards held ai-sdr-core@reply-skills alone, and reply skills list showed both.
  • npm run smoke:hosts passed under a throwaway home, with the real Claude Code exercised and the real home snapshot unchanged.

…l them from it

The five reply-adapter skills now live in this package under skills/,
at the CLI's own version. install and update copy them from the
installed package into every detected assistant, Claude Code and Codex
included, with no network and no git. The old reply-adapter plugin an
earlier version installed is removed through the host's own CLI once
the copy is in place. list and remove still act on what earlier
versions installed, under the old pack names too; asking install or
update for those names is a usage error naming where they now ship.
…lives

The README stops presenting three packs and the separate skills
repository: it names the pack this package carries, how it moves with
the CLI, the copied-file paths for Claude Code and Codex, and that the
SDR expertise and runtime skills ship with Jason.
reply skills list now prints each pack with the version installed in
that assistant, so the human report answers which version is where as
the JSON one already did. The line naming the old plugins left in place
agrees in number with how many there are.
…ame's own entry

install and update now name, in the one line about what stays, the
retired packs an earlier version copied into a host at the run's scope,
beside the old plugins, each host with its own names. A pack name is
looked up in the tables' own entries only, so a name such as
constructor is an unknown pack rather than a retired one. A test pins
update on a host that has neither a copy nor the old plugin.
@ArtemKosolap
ArtemKosolap merged commit 36832d1 into main Nov 5, 2026
6 checks passed
@ArtemKosolap
ArtemKosolap deleted the REPLY-52328-skills-in-package branch November 5, 2026 02:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant