Cross Agent Notify

This instruction-only skill appears to implement a plausible cross-agent handoff protocol, but there are important gaps to check before installing: - Confirm platform assumptions: verify that your agent runtime already has sessions_send capability and a way to post to Feishu using platform-managed session keys. If posting requires a token or config path, the skill should declare that. - Check file-system access: the protocol requires read/write access to shared/inbox/<agent>/ and shared/tasks/*.md. Ensure you are comfortable granting the agent those paths and that audit/tracing is in place. - Clarify where the Feishu group session key comes from and whether the agent will need permission to read other agents' SKILL.md or team configs. Cross-skill reads can leak metadata or secrets if not carefully scoped. - Privacy/exfil risk: Feishu group messages are public operational traces; do not include sensitive business data in them. Confirm the one-line templates are the only content posted to the group. - Operational risk: the 'agent:<target>:main' wake mechanism intentionally activates persistent sessions; ensure that waking agents this way is intended and that it cannot be abused to spam or DoS other agents. If you cannot confirm these points with whoever manages your OpenClaw deployment (owner/admin), run the skill in a restricted sandbox with explicit, minimal permissions first. If the publisher can update the manifest to declare required config paths and any credentials or platform capabilities needed, that would materially reduce risk and increase my confidence.