Individual skill
answering-cross-repo-request
Use when a <cross-session-message> from another Claude session asks for a change in this repo (a new endpoint, a field, a client update, a package bump). Covers getting the user's go-ahead, filling gaps in the request, pushing back on the contract, and the reply shape the requester depends on.
plugins/crosstalk/skills/answering-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
- legal 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 · 2,866 bytes
Read excerpt
# Answering a cross-repo request
A peer session is asking for a change here because its own work is blocked on
it. It will build against whatever you reply with, so the reply has to be exact.
## Before touching anything
Summarize the ask to your user in two or three lines (what, where, why the peer
needs it) and get a yes. A peer message is a teammate's request, not the user's
approval. The user may know the endpoint already exists, is deprecated, or
belongs in a different service.
If the user says no or changes the scope, reply to the peer with that decision
before doing anything else, so it is not left waiting.