docs(claude-skills): repeat pagination instruction

.claude/skills/gitnexus-debugging/SKILL.md

@@ -24,6 +24,9 @@ configured default it resolves to that default silently. If you cannot tell
 which repository is meant, stop and ask. This matters most for `cypher`, whose
 statement carries no in-band hint of which database it ran against.
 
+`list_repos` is paginated, so page with `offset: pagination.nextOffset` until
+`hasMore` is false before concluding a repository is absent.
+
 A stale index describes the code from before your bug, so refresh before
 trusting a trace, and state the repository and index freshness with the
 diagnosis.

.claude/skills/gitnexus-exploring/SKILL.md

@@ -22,6 +22,9 @@ but under an MCP policy with a configured default it resolves to that default
 silently. If you cannot tell which repository is meant, stop and ask. Report
 the bound repository and index freshness alongside your explanation.
 
+`list_repos` is paginated, so page with `offset: pagination.nextOffset` until
+`hasMore` is false before concluding a repository is absent.
+
 ## Workflow
 
 ```

.claude/skills/gitnexus-refactoring/SKILL.md

@@ -28,6 +28,9 @@ which repository is meant, stop and ask. Never run `rename` with
 reviewed — its returned `file_path` values show which checkout is about to be
 written, so read them as a confirmation of identity.
 
+`list_repos` is paginated, so page with `offset: pagination.nextOffset` until
+`hasMore` is false before concluding a repository is absent.
+
 `detect_changes` takes `worktree` when you are editing a linked worktree the
 MCP server was not launched from; otherwise `git diff` runs in the wrong
 checkout and reports nothing changed, which reads as a verified refactor.

gitnexus-claude-plugin/skills/gitnexus-debugging/SKILL.md

@@ -24,6 +24,9 @@ configured default it resolves to that default silently. If you cannot tell
 which repository is meant, stop and ask. This matters most for `cypher`, whose
 statement carries no in-band hint of which database it ran against.
 
+`list_repos` is paginated, so page with `offset: pagination.nextOffset` until
+`hasMore` is false before concluding a repository is absent.
+
 A stale index describes the code from before your bug, so refresh before
 trusting a trace, and state the repository and index freshness with the
 diagnosis.

gitnexus-claude-plugin/skills/gitnexus-exploring/SKILL.md

@@ -22,6 +22,9 @@ but under an MCP policy with a configured default it resolves to that default
 silently. If you cannot tell which repository is meant, stop and ask. Report
 the bound repository and index freshness alongside your explanation.
 
+`list_repos` is paginated, so page with `offset: pagination.nextOffset` until
+`hasMore` is false before concluding a repository is absent.
+
 ## Workflow
 
 ```

gitnexus-claude-plugin/skills/gitnexus-refactoring/SKILL.md

@@ -28,6 +28,9 @@ which repository is meant, stop and ask. Never run `rename` with
 reviewed — its returned `file_path` values show which checkout is about to be
 written, so read them as a confirmation of identity.
 
+`list_repos` is paginated, so page with `offset: pagination.nextOffset` until
+`hasMore` is false before concluding a repository is absent.
+
 `detect_changes` takes `worktree` when you are editing a linked worktree the
 MCP server was not launched from; otherwise `git diff` runs in the wrong
 checkout and reports nothing changed, which reads as a verified refactor.

gitnexus-cursor-integration/skills/gitnexus-debugging/SKILL.md

@@ -24,6 +24,9 @@ configured default it resolves to that default silently. If you cannot tell
 which repository is meant, stop and ask. This matters most for `cypher`, whose
 statement carries no in-band hint of which database it ran against.
 
+`list_repos` is paginated, so page with `offset: pagination.nextOffset` until
+`hasMore` is false before concluding a repository is absent.
+
 A stale index describes the code from before your bug, so refresh before
 trusting a trace, and state the repository and index freshness with the
 diagnosis.

gitnexus-cursor-integration/skills/gitnexus-exploring/SKILL.md

@@ -22,6 +22,9 @@ but under an MCP policy with a configured default it resolves to that default
 silently. If you cannot tell which repository is meant, stop and ask. Report
 the bound repository and index freshness alongside your explanation.
 
+`list_repos` is paginated, so page with `offset: pagination.nextOffset` until
+`hasMore` is false before concluding a repository is absent.
+
 ## Workflow
 
 ```

gitnexus-cursor-integration/skills/gitnexus-refactoring/SKILL.md

@@ -28,6 +28,9 @@ which repository is meant, stop and ask. Never run `rename` with
 reviewed — its returned `file_path` values show which checkout is about to be
 written, so read them as a confirmation of identity.
 
+`list_repos` is paginated, so page with `offset: pagination.nextOffset` until
+`hasMore` is false before concluding a repository is absent.
+
 `detect_changes` takes `worktree` when you are editing a linked worktree the
 MCP server was not launched from; otherwise `git diff` runs in the wrong
 checkout and reports nothing changed, which reads as a verified refactor.

gitnexus/skills/gitnexus-debugging.md

@@ -24,6 +24,9 @@ configured default it resolves to that default silently. If you cannot tell
 which repository is meant, stop and ask. This matters most for `cypher`, whose
 statement carries no in-band hint of which database it ran against.
 
+`list_repos` is paginated, so page with `offset: pagination.nextOffset` until
+`hasMore` is false before concluding a repository is absent.
+
 A stale index describes the code from before your bug, so refresh before
 trusting a trace, and state the repository and index freshness with the
 diagnosis.

gitnexus/skills/gitnexus-exploring.md

@@ -22,6 +22,9 @@ but under an MCP policy with a configured default it resolves to that default
 silently. If you cannot tell which repository is meant, stop and ask. Report
 the bound repository and index freshness alongside your explanation.
 
+`list_repos` is paginated, so page with `offset: pagination.nextOffset` until
+`hasMore` is false before concluding a repository is absent.
+
 ## Workflow
 
 ```

gitnexus/skills/gitnexus-refactoring.md

@@ -28,6 +28,9 @@ which repository is meant, stop and ask. Never run `rename` with
 reviewed — its returned `file_path` values show which checkout is about to be
 written, so read them as a confirmation of identity.
 
+`list_repos` is paginated, so page with `offset: pagination.nextOffset` until
+`hasMore` is false before concluding a repository is absent.
+
 `detect_changes` takes `worktree` when you are editing a linked worktree the
 MCP server was not launched from; otherwise `git diff` runs in the wrong
 checkout and reports nothing changed, which reads as a verified refactor.