skill nits

Author: clavery

plugins/b2c-cli/skills/b2c-code/SKILL.md

@@ -73,6 +73,8 @@ b2c code activate <version-name>
 b2c code activate --reload
 ```
 
+**Note:** Activating a code version triggers Custom API endpoint registration. If you've added or modified Custom APIs, use `--reload` with deploy or activate to register them. Check registration status with the `b2c-cli:b2c-scapi-custom` skill.
+
 ### Delete Code Version
 
 ```bash
@@ -83,3 +85,9 @@ b2c code delete <version-name>
 ### More Commands
 
 See `b2c code --help` for a full list of available commands and options in the `code` topic.
+
+## Related Skills
+
+- `b2c-cli:b2c-scapi-custom` - Check Custom API registration status after deployment
+- `b2c-cli:b2c-webdav` - Low-level file operations (delete cartridges, list files)
+- `b2c:b2c-custom-api-development` - Creating Custom API endpoints

plugins/b2c-cli/skills/b2c-scapi-custom/SKILL.md

@@ -87,3 +87,8 @@ The tenant ID and short code can be set via environment variables:
 ### More Commands
 
 See `b2c scapi custom --help` for a full list of available commands and options.
+
+## Related Skills
+
+- `b2c:b2c-custom-api-development` - Creating Custom API endpoints (schema, script, mapping)
+- `b2c-cli:b2c-code` - Deploying and activating code versions (triggers registration)

plugins/b2c-cli/skills/b2c-webdav/SKILL.md

@@ -239,6 +239,24 @@ b2c webdav rm src/instance/old-export.zip
 b2c webdav rm old-file.txt --root=temp
 ```
 
+### Delete Cartridges
+
+To delete cartridges from a code version, use the `cartridges` root with the path format `{code-version}/{cartridge-name}`:
+
+```bash
+# delete a cartridge from a code version
+b2c webdav rm v25_1_0/app_mysite --root=cartridges
+
+# delete multiple cartridges
+b2c webdav rm v25_1_0/app_mysite --root=cartridges
+b2c webdav rm v25_1_0/int_myintegration --root=cartridges
+
+# list cartridges in a code version first
+b2c webdav ls v25_1_0 --root=cartridges
+```
+
+**Important:** The path is `{code-version}/{cartridge-name}`, not `/cartridges/{code-version}/...`. The `--root=cartridges` (or `-r cartridges`) flag sets the WebDAV root.
+
 ### Zip/Unzip Remote Files
 
 ```bash
@@ -252,3 +270,8 @@ b2c webdav unzip src/instance/archive.zip
 ### More Commands
 
 See `b2c webdav --help` for a full list of available commands and options in the `webdav` topic.
+
+## Related Skills
+
+- `b2c-cli:b2c-code` - Higher-level code deployment (preferred for cartridge upload)
+- `b2c-cli:b2c-job` - Import/export site archives

plugins/b2c/skills/b2c-custom-api-development/SKILL.md

@@ -291,12 +291,52 @@ To query the Custom API status report, use an Account Manager token with scope:
 2. **Define contract** (schema.yaml) with endpoints and security
 3. **Implement logic** (script.js) with exported functions
 4. **Create mapping** (api.json) binding endpoints to implementation
-5. **Upload cartridge** to your B2C instance
-6. **Activate code version** to register endpoints
-7. **Check status** to verify registration
-8. **Test endpoints** with appropriate authentication
-9. **Monitor logs** for errors during development
-10. **Iterate** on implementation as needed
+5. **Deploy and activate** to register endpoints
+6. **Check registration status** to verify endpoints are active
+7. **Test endpoints** with appropriate authentication
+8. **Monitor logs** for errors during development
+9. **Iterate** on implementation as needed
+
+### Deployment Commands
+
+Deploy your cartridge and activate to trigger Custom API registration:
+
+```bash
+# Deploy cartridge and reload (re-activate) to register endpoints
+b2c code deploy ./my-cartridge --reload
+
+# Or deploy then activate separately
+b2c code deploy ./my-cartridge
+b2c code activate my-code-version
+```
+
+See the `b2c-cli:b2c-code` skill for more deployment options.
+
+### Check Registration Status
+
+After deployment, verify your endpoints are registered:
+
+```bash
+# Check Custom API registration status
+# Tenant ID: derive from hostname (e.g., zzpq-013 → zzpq_013)
+b2c scapi custom status --tenant-id zzpq_013
+
+# Filter to see only failed registrations
+b2c scapi custom status --tenant-id zzpq_013 --status not_registered
+
+# Show error reasons for failed registrations
+b2c scapi custom status --tenant-id zzpq_013 --status not_registered --columns apiName,endpointPath,errorReason
+```
+
+See the `b2c-cli:b2c-scapi-custom` skill for more status options.
+
+### Common Registration Issues
+
+| Issue | Solution |
+|-------|----------|
+| Endpoint shows `not_registered` | Check errorReason column, verify schema.yaml syntax |
+| Endpoint not appearing | Verify cartridge is in site's cartridge path, re-activate code version |
+| 404 on requests | Endpoint not registered or wrong URL path |
 
 ## HTTP Methods Supported
 
@@ -344,6 +384,8 @@ To import a service configuration:
 
 ## Related Skills
 
+- `b2c-cli:b2c-code` - Deploying cartridges and activating code versions
+- `b2c-cli:b2c-scapi-custom` - Checking Custom API registration status
 - `b2c:b2c-webservices` - Service configuration, HTTP/FTP/SOAP clients, services.xml format
 - `b2c-cli:b2c-job` - Running jobs and importing site archives