How do I install the Cross Channel Cross Agent Sharing skill?

Run npx skillmds@latest add knownasnaffy/cross-channel-cross-agent-sharing-4 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Cross Channel Cross Agent Sharing safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Cross Channel Cross Agent Sharing?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Cross Channel Cross Agent Sharing free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Cross Channel Cross Agent Sharing?

knownasnaffy (@knownasnaffy) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Cross Channel Cross Agent Sharing by knownasnaffy

Name: Cross Channel Cross Agent Sharing
Rating: 4.2 (5 reviews)
Author: knownasnaffy

Cross Channel Cross Agent Sharing

Ensure new capabilities gained from workspace-installed tools/packages are propagated across channels and agent sessions. Use when any tool/env/package install (e.g., venv, pip, npm, apt, binaries) unlocks new workflows and you need consistent cross-channel + cross-agent awareness via TOOLS.md updates, reusable skill updates, memory logging, and session notifications.

knownasnaffy Updated Sep 22, 2026 0 repo stars

File contents

Cross-Channel & Cross-Agent Skill Sharing

Execute this workflow whenever workspace capability changes

Detect capability change source:
- New package/tool installed in workspace
- Existing tool upgraded and behavior changed
- New env/interpreter path required for capability
Update TOOLS.md with operational facts:
- Exact runtime/interpreter path
- Install command
- Verify command
- Package versions
- One-line usage note
Create or update a reusable skill when pattern is repeatable:
- Add/adjust SKILL.md
- Add scripts under scripts/ for deterministic steps
- Keep instructions concise and invocation-focused
- Prefer adding a verification script for fast capability checks
Log event in memory/YYYY-MM-DD.md:
- What changed
- How to verify
- Any limits/known caveats
Inform current conversation:
- Summarize new capability
- Show exact invocation command or trigger phrase
Propagate to active related sessions/agents:
- If likely relevant, send brief sync via sessions_send
- Include only invocation + critical caveat

Required output format in chat (short)

New capability:
Use it with: <exact command / trigger>
Scope: Applies to all channels and sessions using this workspace
Caveat:

Quick Verification Helper

Use bundled script to verify interpreter + modules before claiming capability:

scripts/check_capability.sh <python-bin> <module1> [module2 ...]

Example:

scripts/check_capability.sh ~/.openclaw/workspace/.venv-img/bin/python cv2 PIL numpy

Guardrails

Do not assume global python/node paths; prefer workspace-scoped env paths
Do not claim capability before running verify command
Keep cross-session notices minimal to avoid spam
If capability is channel-specific (provider restriction), state that explicitly

---name: cross-channel-cross-agent-sharing-4description: Ensure new capabilities gained from workspace-installed tools/packages are propagated across channels and agent sessions. Use when any tool/env/package install (e.g., venv, pip, npm, apt, binaries) unlocks new workflows and you need consistent cross-channel + cross-agent awareness via TOOLS.md updates, reusable skill updates, memory logging, and session notifications.---# Cross-Channel & Cross-Agent Skill Sharing## Execute this workflow whenever workspace capability changes1. Detect capability change source: - New package/tool installed in workspace - Existing tool upgraded and behavior changed - New env/interpreter path required for capability2. Update `TOOLS.md` with operational facts: - Exact runtime/interpreter path - Install command - Verify command - Package versions - One-line usage note3. Create or update a reusable skill when pattern is repeatable: - Add/adjust `SKILL.md` - Add scripts under `scripts/` for deterministic steps - Keep instructions concise and invocation-focused - Prefer adding a verification script for fast capability checks4. Log event in `memory/YYYY-MM-DD.md`: - What changed - How to verify - Any limits/known caveats5. Inform current conversation: - Summarize new capability - Show exact invocation command or trigger phrase6. Propagate to active related sessions/agents: - If likely relevant, send brief sync via `sessions_send` - Include only invocation + critical caveat## Required output format in chat (short)- **New capability:** <what is newly possible>- **Use it with:** <exact command / trigger>- **Scope:** Applies to all channels and sessions using this workspace- **Caveat:** <if any>## Quick Verification HelperUse bundled script to verify interpreter + modules before claiming capability:```bashscripts/check_capability.sh <python-bin> <module1> [module2 ...]```Example:```bashscripts/check_capability.sh ~/.openclaw/workspace/.venv-img/bin/python cv2 PIL numpy```## Guardrails- Do not assume global python/node paths; prefer workspace-scoped env paths- Do not claim capability before running verify command- Keep cross-session notices minimal to avoid spam- If capability is channel-specific (provider restriction), state that explicitly

Frequently asked questions