[mwbrooks]

Summary

This pull request makes the agent setup prompt install the skills from the release tag that shipped with it, instead of from main, so a developer's coding agent only runs skills that went out in a release:

npx -y skills@latest add https://github.com/slackapi/slack-skills-plugin/tree/v1.7.0 -g -y -a <agent>

scripts/sync_versions.py moves the tag in the release PR, the same way it already moves the Claude Code marketplace ref. A new unit test fails if the tag and package.json drift apart. The README keeps the shorter slackapi/slack-skills-plugin form that people type.

Testing

• Ran the new command with a clean HOME: skills 1.7.6 installed all 9 skills, and ~/.agents/.skill-lock.json records "ref": "v1.7.0" for each one.
• Ran it again over an install made from main with the old command: each skill's ref moved from none to v1.7.0.
• Set package.json to 1.7.1 in a copy and ran scripts/sync_versions.py: the prompt's tag moved to v1.7.1 and the prompt tests still pass.
• make test-unit (32 passed), ruff check, mypy, and rumdl check pass locally.

Notes

• Between a merge to main and the next release, the prompt on main names the previous tag. docs.slack.dev serves the prompt from a release tag, so developers only see the prompt and the tag together.

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.

[changeset-bot]

🦋 Changeset detected

Latest commit: 6e9831f

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