Best use case
can-communication is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
CAN bus design, analysis, and diagnostics expertise
Teams using can-communication should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/can-communication/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How can-communication Compares
| Feature / Agent | can-communication | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
CAN bus design, analysis, and diagnostics expertise
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# CAN/CAN-FD Communication Skill ## Purpose Provide CAN bus design, analysis, and diagnostics expertise for automotive network development and troubleshooting. ## Capabilities - DBC file creation and parsing - CAN message scheduling and bus load analysis - CAN-FD configuration and migration - J1939 and CANopen protocol support - Network topology design - Gateway routing configuration - Error frame analysis and bus-off handling - XCP/CCP calibration protocol ## Usage Guidelines - Design CAN networks with appropriate bus load margins - Schedule messages to avoid collisions and ensure timing - Configure CAN-FD for increased bandwidth applications - Implement proper error handling and recovery - Use appropriate termination and topology - Document network design and message definitions ## Dependencies - Vector CANoe - CANalyzer - PEAK PCAN tools - DBC editors ## Process Integration - ASD-001: AUTOSAR Architecture Implementation - ASD-002: ECU Software Development and Testing - ASD-003: Diagnostic Implementation (UDS/OBD) - TVL-002: Hardware-in-the-Loop Testing
Related Skills
Stakeholder Communication
Generate stakeholder-specific communications and presentations for product updates
nccl-communication
NVIDIA Collective Communications Library integration for multi-GPU operations. Initialize NCCL communicators, execute collective operations, configure communication topologies, profile collective performance, and support RCCL for AMD compatibility.
policy-communication
Translate research findings into accessible policy briefs, presentations, and stakeholder communications
arts-advocacy-communication
Craft persuasive advocacy messages, coordinate coalition building, and engage with policymakers to advance arts funding and cultural policy priorities
communication-plan-generator
Generate stakeholder communication plans and message templates for change initiatives
process-builder
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
babysitter
Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)
yolo
Run Babysitter autonomously with minimal manual interruption.
user-install
Install the user-level Babysitter Codex setup.
team-install
Install the team-pinned Babysitter Codex workspace setup.
retrospect
Summarize or retrospect on a completed Babysitter run.
resume
Resume an existing Babysitter run from Codex.