Skip to content

chore: name skills@latest in the agent setup install command - #212

Merged
mwbrooks merged 3 commits into
mainfrom
mwbrooks-npx-skills-latest
Nov 6, 2026
Merged

mwbrooks merged 3 commits into
mainfrom
mwbrooks-npx-skills-latest

Conversation

@mwbrooks

@mwbrooks mwbrooks commented Nov 6, 2026 •

Copy link
Copy Markdown
Member

Summary

This pull request makes the agent setup prompt's npx skills install command ask for skills@latest by name, so maintainers and reviewers can see that tracking the latest skills release is a deliberate choice, not a missing pin:

npx -y skills@latest add slackapi/slack-skills-plugin -g -y -a <agent>

Current npm already resolves the latest release for a bare npx skills, so the version an agent installs does not change. The README keeps the shorter npx skills form that people type, and the README sync test maps between the two.

Testing

  • With npm 11.17.0, npx -y --loglevel http skills --version and npx -y --loglevel http skills@latest --version both revalidate registry.npmjs.org/skills and resolve the same release.
  • Ran the prompt's full command, npx -y skills@latest add slackapi/slack-skills-plugin -g -y -a opencode, with a clean HOME. It used skills 1.7.6 and installed all 9 skills to ~/.agents/skills without prompting.
  • make test-unit passes locally (31 passed).

Notes

  • A follow-up PR will point the same command at a release tag of this repository instead of main, so npx skills installs the skills that shipped with the prompt.

Requirements

  • I've read and understood the Contributing Guidelines and have done my best effort to follow them.
  • I've read and agree to the Code of Conduct.
  • I've run make test and the tests pass. Ran the unit tests only (make test-unit), and the evals run in CI.

@mwbrooks mwbrooks added semver:patch Changes trigger a patch version bump chore Maintainer work: repo files, release scaffolding, general maintenance security Security fixes, hardening, vulnerability patches area:agent-setup Agent setup prompt served at docs.slack.dev/agent-setup/prompt.md labels Nov 6, 2026
@mwbrooks mwbrooks self-assigned this Nov 6, 2026
@changeset-bot

changeset-bot Bot commented Nov 6, 2026 •

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: f1c4e48

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
slack Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@mwbrooks
mwbrooks marked this pull request as ready for review November 6, 2026 05:29
@mwbrooks
mwbrooks requested a review from a team as a code owner November 6, 2026 05:29

@zimeg zimeg left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ LGTM! Naming skills@latest makes the intent clear, and keeping the README on the shorter form people type reads well.

📝 nit (non-blocking): since this only changes the prompt's wording and the installed version stays the same, docs: might fit the title better than chore:, so the changeset reads as a docs tweak in the release notes. Earlier prompt edits went out as fix:, though, so happy either way!

@mwbrooks

mwbrooks commented Nov 6, 2026

Copy link
Copy Markdown
Member Author

Thanks @zimeg and @WilliamBergamin for the quick reviews, and William for keeping the branch up to date! 🙇

@mwbrooks
mwbrooks merged commit 99e027a into main Nov 6, 2026
7 checks passed
@mwbrooks
mwbrooks deleted the mwbrooks-npx-skills-latest branch November 6, 2026 19:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:agent-setup Agent setup prompt served at docs.slack.dev/agent-setup/prompt.md chore Maintainer work: repo files, release scaffolding, general maintenance security Security fixes, hardening, vulnerability patches semver:patch Changes trigger a patch version bump

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants