biotender-max/cell-communication
Workflow for ligand-receptor communication inference in single-cell or spatial data with sender-receiver summaries and cautious interpretation.
npx skills add https://github.com/BioTender-max/awesome-bio-agent-skills --skill cell-communication
Reference examples assume recent stable releases of the preferred tools, especially pandas and the other tools listed below.
Before using code or command patterns, verify installed versions match the environment:
python -c "import <module>; print(<module>.__version__)"<tool> --versionWorkflow for ligand-receptor communication inference in single-cell or spatial data with sender-receiver summaries and cautious interpretation.
references/technical_reference.md when you need deeper tool-selection rules, environment adaptation notes, or extra validation guidance.SKILL.md as the main execution path and load the reference file only when the task or failure mode needs the extra detail.Preferred starting point: pandas
Inputs: annotated single-cell or spatial object, ligand-receptor resource, group or condition metadata
Outputs: interaction tables, sender-receiver summaries, communication visualizations
Communication analysis depends on robust cell labels or spatial domains.
Choose whether to infer communication across clusters, cell types, neighborhoods, or conditions.
Compute ligand-receptor evidence and apply filtering for expression support and redundancy.
Summarize signals by sender, receiver, pathway, or condition.
State clearly that inferred communication is hypothesis-generating unless validated experimentally.
results/ for final tables and serialized objectsfigures/ for plots and static visual exportsqc/ for checks that justify downstream interpretationinteraction tablessender-receiver summariescommunication visualizationsscRNA Preprocessing And ClusteringCell AnnotationTrajectory And LineageMultiome And scATACstring-databaseTake biotender-max/cell-communication from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.