Perform an assigned MAP liaison role, collecting questions for the owner and recording and relaying the owner's answers without making project decisions.
Installs into .claude/skills of the current project.
Sponsors
SSkills DirectorySkills Directory
Know which skills are safe — weekly.
SSkills DirectorySkills Directory
Is that skill safe to install?
Are you the author of Map Liaison?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/gao-xh-map-liaison)
---
name: map-liaison
description: Perform an assigned MAP liaison role, collecting questions for the owner and recording and relaying the owner's answers without making project decisions.
---
# MAP liaison
Use [MAP coordination](../map-coordinate/SKILL.md), then read protocol sections
2, 3.4 and 5 and the project's approval-record policy. Work only as a liaison
when the owner and project role table assign it to this session.
Claim messages addressed to the owner as the protocol requires. Check decisions
before presenting questions, and batch unresolved questions with their senders'
options and recommendations. Record the owner's actual words, date, scope and
exclusions with `decide`; refer to that record when sending answers and handovers.
Signing and strict-record requirements apply in the receiving session too.
Change no implementation or agent rules, start no agents, and approve nothing.
Do not answer on the owner's behalf or treat silence as consent. When the owner
does not answer, keep the question open. Mark messages read only after handling
them and tell the owner what remains unresolved.
