Best use case
uds-diagnostics is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Unified Diagnostic Services implementation and validation expertise
Teams using uds-diagnostics 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/uds-diagnostics/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How uds-diagnostics Compares
| Feature / Agent | uds-diagnostics | 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?
Unified Diagnostic Services implementation and validation 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
# UDS Diagnostics Skill ## Purpose Provide Unified Diagnostic Services implementation and validation expertise for automotive ECU diagnostics and OBD compliance. ## Capabilities - UDS service implementation (ISO 14229) - DTC configuration and memory management - ODX/PDX file generation - Security access implementation - Routine control design - Data identifier (DID) configuration - OBD-II legislated service implementation - Diagnostic session management ## Usage Guidelines - Implement UDS services per ISO 14229 specifications - Configure DTCs with appropriate detection and storage - Generate ODX files for diagnostic tool compatibility - Implement security access for protected functions - Design routine controls for manufacturing and service - Validate OBD compliance for emissions certification ## Dependencies - Vector CANoe/CANdela - ODX Studio - Diagnostic testers ## Process Integration - ASD-003: Diagnostic Implementation (UDS/OBD) - ASD-001: AUTOSAR Architecture Implementation - TVL-003: Homologation and Type Approval
Related Skills
mcmc-diagnostics
MCMC convergence diagnostics and analysis
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.
project-install
Install the Babysitter Codex workspace integration into the current project.
plan
Plan a Babysitter workflow without executing the run.
observe
Observe, inspect, or monitor a Babysitter run.
model
Inspect or change Babysitter model-routing policy by phase.