adding skills changeset

Author: clavery

.changeset/setup-skills-command.md

@@ -0,0 +1,6 @@
+---
+'@salesforce/b2c-cli': minor
+'@salesforce/b2c-tooling-sdk': minor
+---
+
+Add `b2c setup skills` command for installing agent skills to AI-powered IDEs (Claude Code, Cursor, Windsurf, VS Code/Copilot, Codex, OpenCode)

AGENTS.md

@@ -106,14 +106,6 @@ pnpm mocha "test/clients/webdav.test.ts"         # Single file (no coverage)
 
 This project uses [Changesets](https://github.com/changesets/changesets) for version management. When making changes that affect users, create a changeset:
 
-```bash
-# Create a changeset (interactive prompt)
-pnpm changeset
-
-# Check pending changesets
-pnpm changeset status
-```
-
 Changeset guidelines:
 - Create a changeset for any user-facing changes (features, bug fixes); typically in new pull requests; 
 - a pull request can have multiple changesets
@@ -123,8 +115,9 @@ Changeset guidelines:
   - WHAT the change is
   - WHY the change was made
   - HOW a consumer should update their code
+- Good changesets are brief and user-focused (not contributor); they are generally 1 line or a short paragraph for detailed changes
 
-For headless/agentic use, create a changeset file directly in `.changeset/` with a unique filename (e.g., `descriptive-change-name.md`):
+create a changeset file directly in `.changeset/` with a unique filename (e.g., `descriptive-change-name.md`):
 
 ```md
 ---