Best use case
instrument-saleae-logic is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Teams using instrument-saleae-logic 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/instrument-saleae-logic/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How instrument-saleae-logic Compares
| Feature / Agent | instrument-saleae-logic | 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?
This skill provides specific capabilities for your AI agent. See the About section for full details.
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
# Skill: Saleae Logic Analyzer (Automation)
## 1. Overview
The industry standard for digital signal debugging and protocol decoding.
* **Primary Roles**: I2C/SPI/UART/CAN decoding, timing verification.
* **Interface**: USB 3.0.
* **Control Lib**: `saleae` (Logic 1.x) or `logic2-automation` (Logic 2.x). Note: Logic 2 API is preferred.
## 2. Automation Logic (Logic 2 gRPC API)
Using the `saleae-logic2-automation` python package.
```python
from saleae import automation
import os.path
# Connect to running Logic 2 application
with automation.Manager.connect(port=10430) as manager:
# Configure Capture
device_configuration = automation.LogicDeviceConfiguration(
enabled_digital_channels=[0, 1, 2, 3],
digital_sample_rate=10_000_000, # 10 MS/s
digital_threshold_volts=1.2
)
capture_configuration = automation.CaptureConfiguration(
capture_mode=automation.TimedCaptureMode(duration_seconds=5.0)
)
# Start Capture
with manager.start_capture(
device_configuration=device_configuration,
capture_configuration=capture_configuration
) as capture:
capture.wait()
# Save to file
capture.save_capture(filepath=os.path.abspath("capture_test.sal"))
# Export Raw Data (CSV)
capture.export_raw_data_csv(
directory=os.path.abspath("output_csv"),
digital_channels=[0, 1]
)
```
## 3. Triggering
Automation is useless without precise triggering.
* You generally set up the trigger in the GUI for complex cases, or use simple digital edge triggers via API.
* For advanced CI/CD, use a **GPIO sync line** from the DUT to Channel 0 of Saleae to start recording exactly when the test starts.Related Skills
instrument-tektronix-scope
No description provided.
instrument-power-supply
No description provided.
instrument-keysight-uxm
No description provided.
instrument-jlink
No description provided.
instrument-dmm
No description provided.
instrument-cmw500
No description provided.
instrument-anritsu-mt8821
No description provided.
vuln-scan
Multi-language dependency security scan - Use Safety CLI and OSV-Scanner to quickly detect dependency vulnerabilities in Python/JS/Java projects
SKILL_ONBOARDING.md
> **Purpose**: Conduct a one-time "Handshake Interview" with the user to establish their Developer Persona.
usb-debug
No description provided.
sql-lint
SQL code style check - Use SQLFluff to check SQL statement style and syntax (supports PostgreSQL, MySQL, SQLite, etc.)
serial-debug
No description provided.