Individual skill
cross-repo-request
Use when work in this repo depends on a change in a different repo that has its own running Claude session (frontend needing a backend endpoint, backend needing a client change, a shared package bump). Covers finding the peer session, what to put in the request so it needs no follow-ups, and how to handle the reply.
plugins/crosstalk/skills/cross-repo-request/SKILL.md
Source commit 82ce2112b080810c6b72939201d6a53876116e12
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 3,737
- Repository last updated
- Nov 9, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude Repository topic
- claude-code Repository topic
- subagents Repository topic
- commands Repository topic
- claude-code-commands Repository topic
- cli-tool Repository topic
- mcp Repository topic
- mcp-server Repository topic
- mcp-tools Repository topic
- claude-skills Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 3,821 bytes
Read excerpt
# Cross-repo requests
## The failure this prevents
A frontend agent needs an endpoint that does not exist yet. Left alone it stubs
the response, invents a payload shape, and writes code against a contract the
backend never agreed to. The stub survives into review and the shapes do not
match. The same happens in reverse when a backend agent guesses at how a client
consumes a field.
If another repo owns the change, ask the session that owns that repo. Do not
guess the contract, and do not stub it silently.
## Finding the peer