Clarify binding skeleton invocation

Signed-off-by: Wouter Born <github@maindrain.net>

Author: wborn

AGENTS.md

@@ -296,7 +296,7 @@ Before considering a change complete:
 - Read the binding development guide before creating a new binding: <https://www.openhab.org/docs/developer/#develop-a-new-binding>
 - Determine the binding name and real human author name from the user's request or reliable repository information; do not invent them.
 - Ensure the target binding does not already exist.
-- Use the provided `create_openhab_binding_skeleton` script rather than creating the binding structure manually.
+- Run the appropriate `create_openhab_binding_skeleton` script from the `bundles/` directory rather than creating the binding structure manually.
 - Quote the author name when passing it to the script because it can contain spaces.
 - Let the creation script update `CODEOWNERS`, inspect all generated changes, and remove anything unintended.
 - Run `mvn spotless:apply` from the generated binding directory after creation.
@@ -308,4 +308,4 @@ When creating a pull request, read and follow `.github/PULL_REQUEST_TEMPLATE.md`
 - Treat HTML-commented template text as instructions and write visible Markdown that addresses the applicable requirements; do not copy the comment delimiters or leave the PR description hidden inside an HTML comment.
 - The template's guidance about linking to automatically generated pull-request build artifacts is currently outdated; do not add such artifact links.
 - Before creating or updating a pull request, verify that its title and description still match the current diff and scope, especially after follow-up changes.
-- Treat the template as the source of truth for the remaining pull-request requirements rather than duplicating them here.
+- Treat the template as the source of truth for the remaining pull-request requirements rather than duplicating them here.