Embedded Debugger
Adancurusul/embedded-debugger-mcp
Embedded hardware debugging workflow for probe-rs targets using embedded-debugger-mcp.
Expert in using a Saleae logic analyzer to test or debug embedded systems by analyzing bus protocols like I2C, SPI, and UART.
Install Saleae Analyzer
$ npx skills add pigweed-project/pigweed --skill saleae-analyzer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pigweed-project/pigweed saleae-analyzer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/pigweed-project/pigweed.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/saleae .claude/skills/saleae-analyzer && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "saleae-analyzer" agent skill from https://github.com/pigweed-project/pigweed/tree/main/.agents/skills/saleae into .claude/skills/saleae-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "saleae-analyzer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/pigweed-project/pigweed/tree/main/.agents/skills/saleaeType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add pigweed-project/pigweed --skill saleae-analyzer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pigweed-project/pigweed saleae-analyzer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pigweed-project/pigweed.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/saleae .agents/skills/saleae-analyzer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "saleae-analyzer" agent skill from https://github.com/pigweed-project/pigweed/tree/main/.agents/skills/saleae into .agents/skills/saleae-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "saleae-analyzer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pigweed-project/pigweed --skill saleae-analyzer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pigweed-project/pigweed saleae-analyzer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pigweed-project/pigweed.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/saleae .cursor/skills/saleae-analyzer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "saleae-analyzer" agent skill from https://github.com/pigweed-project/pigweed/tree/main/.agents/skills/saleae into .cursor/skills/saleae-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "saleae-analyzer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/pigweed-project/pigweed.git --path .agents/skills/saleae--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add pigweed-project/pigweed --skill saleae-analyzer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pigweed-project/pigweed saleae-analyzer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pigweed-project/pigweed.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/saleae .gemini/skills/saleae-analyzer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "saleae-analyzer" agent skill from https://github.com/pigweed-project/pigweed/tree/main/.agents/skills/saleae into .gemini/skills/saleae-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "saleae-analyzer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install pigweed-project/pigweed saleae-analyzerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add pigweed-project/pigweed --skill saleae-analyzer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/pigweed-project/pigweed.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/saleae .github/skills/saleae-analyzer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "saleae-analyzer" agent skill from https://github.com/pigweed-project/pigweed/tree/main/.agents/skills/saleae into .github/skills/saleae-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "saleae-analyzer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pigweed-project/pigweed --skill saleae-analyzer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install pigweed-project/pigweed saleae-analyzer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pigweed-project/pigweed.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/saleae .opencode/skills/saleae-analyzer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "saleae-analyzer" agent skill from https://github.com/pigweed-project/pigweed/tree/main/.agents/skills/saleae into .opencode/skills/saleae-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "saleae-analyzer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
saleae-analyzer- GitHub stars
- 548
- Token cost
- ~1.4k tokens
- SKILL.md length
- 892 words
- Files
- 2
- Skills in repo
- 10
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Expert in using a Saleae logic analyzer to test or debug embedded systems by analyzing bus protocols like I2C, SPI, and UART.
- Tasks that involve Embedded systems
- SKILL.md covers Channels, Capture triggers, Glitch filter and Analyzers, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Saleae Analyzer is an agent skill from pigweed-project/pigweed. Expert in using a Saleae logic analyzer to test or debug embedded systems by analyzing bus protocols like I2C, SPI, and UART.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `TEST.md`).
It sits in Development, covering Embedded systems. It works with Model Context Protocol. The repository describes itself as: Modern software development for embedded systems. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Embedded systems
Example prompts
- “/saleae-analyzer”
What it can do on your machine
Read from SKILL.md and the folder at commit e73c1a0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Saleae Analyzer loads about 1.4k tokens when it runs. Until then it costs about 35 tokens; SKILL.md has 892 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from pigweed-project/pigweed at commit e73c1a0, republished under its Apache-2.0 licence (© pigweed-project). 892 words, ~1,371 tokens.
Download SKILL.mdSave it as
.claude/skills/saleae-analyzer/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- saleae-analyzer
- description
- Expert in using a Saleae logic analyzer to test or debug embedded systems by analyzing bus protocols like I2C, SPI, and UART.
Saleae analyzer
A Saleae Logic Analyzer is a tool that can be used to capture and analyze digital signals from an embedded system. These signals can either be bus protocols like I2C, SPI, and UART, or they can be control signals like PWM or digital signals from a sensor.
In order to use a Saleae analyzer, the user must first:
- Connect all channels to the appropriate signals on their board.
- Connect the Saleae to their computer.
- Enable the MCP server in "Settings".
- Add the Saleae MCP server in the MCP manager.
Use the MCP interface for interacting with the Saleae analyzer.
Channels
A Saleae has either 8 or 16 total channels depending on the model. Channels can record digital signals, analog signals, or both simultaneously on supported hardware. Some bus protocols require multiple channels to decode; for example, I2C requires both a clock and a data channel to decode a transaction.
The user must specify which channels are used to capture which signals, as well as whether they should be captured as digital or analog channels.
Digital channels
Digital channels capture the binary logic state (high or low) of a signal over time. They are used for capturing digital logic waveforms, control lines (such as GPIOs or PWM), and bus protocols decoded by analyzers (such as I2C, SPI, and UART).
Digital signals can be configured to different voltage levels (e.g., 1.2V, 1.8V, or 3.3V+) to match the logic level of the system under test. Unless the user specifies a different voltage, select 3.3V+ by default.
Analog channels
Analog channels sample and record continuous voltage waveforms over time, similar to an oscilloscope. They are useful for measuring actual voltage levels, inspecting analog sensor outputs, and debugging signal integrity issues such as slow rise/fall times, voltage droop, ringing, or noise on digital lines.
Sample rate
The sample rate is the rate at which the Saleae captures the state of a signal.
The sample rate for digital signals should be at least 10x the maximum frequency of the signal you are capturing. For example, I2C at 100kHz should be sampled at 1MHz (1MSps), while SPI at 10MHz should be sampled at 100MHz (100MSps).
For analog signals, also use the 10x the maximum frequency, so a 10kHz sine wave would be captured at 100kHz or greater. If the signal being measured is a square wave (e.g. debugging signal integrity issues), start at 12.5MSps and only move up to 50MSps if requested by the user.
If the signal to be measured is faster than 2MHz, signal integrity may start to become an issue. If you are seeing unexpected or corrupted data, consider enabling the "Glitch Filter".
Capture triggers
Signal captures may be started in two main ways, Trigger and Timer. Do not use Looping captures unless directly instructed to by the user.
Tips:
- Captures should be started before running the on-device test. This ensures the Saleae captures the entire transaction.
- Prefer Trigger captures over Timer captures where possible.
Show full SKILL.md (399 more words)Show less
Trigger
A Trigger Capture starts after a defined event is detected on a channel and data is logged for a specified length of time.
Trigger captures should be used when:
- A well defined signal is expected on a specific channel and no other spurious signals are expected.
- It is unknown when exactly the signal will occur and the possible window is greater than 30 seconds.
Tips:
- Set the capture duration after the trigger based on the length of time you expect the test to run for but no longer than 30 seconds.
Timer
A Timer Capture starts immediately and data is logged for a specified length of time.
Timer captures should be used in any of the following cases:
- Signals are periodic and occur more frequently than every 10 seconds.
- There is no clear trigger event that can be used to start the capture, for example the signal of interest is mixed in with other signals.
- It is unknown when exactly the signal will occur but the possible window is no longer than 30 seconds.
At sample rates above 10MSps, do not use a timer length longer than 30 seconds.
Glitch filter
There is a glitch filter which can be enabled to remove high frequency glitches from the captured signals. Use this if you see what looks like bus noise on the signal or if the data being captured appears to be corrupted.
A good starting point for the glitch filter is 1/20th of one bit time of the signal. For example, if measuring SPI at 10MHz the bit time is 100ns so the glitch filter should be set to 5ns. If this does not fix the issue, you can try increasing the glitch filter up to 1/5th of one bit time of the signal. Alternatively, you can try changing the bit rate for asynchronous protocols, such as UART.
Analyzers
The Saleae software includes several analyzers that can be used to decode bus protocols. Some common analyzers include:
- Async Serial (UART)
- CAN
- I2C
- I2S
- LIN
- SPI
Analyzers work on specified channels, where each channel corresponds to a signal in the bus protocol. For example, for a standard I2C bus, you add an I2C analyzer and specify during configuration which channels are used for the clock and data lines.
Exporting data
Once a signal has been captured and analyzed, Saleae can export the captured
and analyzed data as .csv format.
© pigweed-project, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in .agents/skills/saleae of pigweed-project/pigweed.
- SKILL.md
- TEST.md
Open the folder on GitHubat commit e73c1a0
Compare with similar skills
Saleae Analyzer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Saleae Analyzer this skillpigweed-project/pigweed | 548 | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Embedded DebuggerAdancurusul/embedded-debugger-mcp | 202 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Intelliconnect Service Styleruanrongman/IntelliConnect | 147 | — | ~2.4k | Automated safety check: Pass | Apache-2.0 | |
| Debugging Executionsn8n-io/n8n | 207k | — | ~2.6k | Automated safety check: Pass | Custom licence | |
| ast-grep Structural Searchcode-yeongyu/oh-my-openagent | 70k | — | ~3.3k | Automated safety check: Pass | MIT | |
| Analyze Logsactivepieces/activepieces | 25k | 1 repos | ~1.6k | Automated safety check: Pass | MIT |
Similar skills
Intelliconnect Service Style
ruanrongman/IntelliConnect
Create or update IntelliConnect Spring Boot service/serviceimpl code in this repository style.
- Official
Debugging Executions
n8n-io/n8n
Debug failed or wrong-output workflow executions using executions tools.
ast-grep Structural Search
code-yeongyu/oh-my-openagent
Searches and rewrites code by syntax-tree shape across 25 languages with ast-grep, for codemods, structural queries and YAML lint rules, using a Python wrapper script.
Analyze Logs
activepieces/activepieces
Analyze application logs from the .evlog/logs/ directory. An agent skill from activepieces/activepieces.
Rea Changelog Update
morluto/rea
Prepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.
More from pigweed-project/pigweed
All 10 skills in this repoOncall
pigweed-project/pigweed
Pigweed oncall rotation runbooks and maintenance workflows (such as rolling CIPD client tools for b/315378787).
Crank
pigweed-project/pigweed
Autonomous "take the next step" workflow orchestrator for Pigweed.
Docs
pigweed-project/pigweed
A skill your agent uses for ALL documentation-related workflows: rst style guide, changelog updates, C/C++ API reference (Doxygen)
Freshen
pigweed-project/pigweed
Safely rebase or fast-forward the active Pigweed worktree onto its target branch (origin/main), resolve Pigweed dual-build and code conflicts, preserve Gerrit Change-Id footers, and verify local…
Manual CLI Test
pigweed-project/pigweed
Interactively "taste the CLI" and "kick the tires" on any CLI tool or subcommand (/manual-cli-test, /agent-cli-kick-tires).
Respond
pigweed-project/pigweed
Address Gerrit review comments and private author drafts on a Pigweed CL with calibrated engineering judgment—implementing valid fixes, answering questions, or pushing back respectfully with…
Related
Works with
Categories
Questions about Saleae Analyzer
What does Saleae Analyzer do?
Expert in using a Saleae logic analyzer to test or debug embedded systems by analyzing bus protocols like I2C, SPI, and UART. Saleae Analyzer is an agent skill from pigweed-project/pigweed. Expert in using a Saleae logic analyzer to test or debug embedded systems by analyzing bus protocols like I2C, SPI, and UART.
When should I use Saleae Analyzer?
Saleae Analyzer fits situations like: tasks that involve Embedded systems.
How do I install Saleae Analyzer in Claude Code?
Run `npx skills add pigweed-project/pigweed --skill saleae-analyzer -a claude-code`. Or copy the skill folder (.agents/skills/saleae in pigweed-project/pigweed) into .claude/skills/saleae-analyzer in your project. Claude Code loads it when a task matches its description.
How do I install Saleae Analyzer in Codex?
Run `npx skills add pigweed-project/pigweed --skill saleae-analyzer -a codex`. Or copy the skill folder (.agents/skills/saleae in pigweed-project/pigweed) into .agents/skills/saleae-analyzer in your project. Codex loads it when a task matches its description.
Can I use Saleae Analyzer in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add pigweed-project/pigweed --skill saleae-analyzer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/saleae-analyzer, .gemini/skills/saleae-analyzer, .github/skills/saleae-analyzer and .opencode/skills/saleae-analyzer in your project.
What does Saleae Analyzer need to run?
SKILL.md names no scripts, command-line tools or credentials: Saleae Analyzer is instructions for the agent only.
Does Saleae Analyzer access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Saleae Analyzer safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Saleae Analyzer use?
Saleae Analyzer is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Saleae Analyzer use?
About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Saleae Analyzer?
Skills that share tags, products or a category with Saleae Analyzer: Embedded Debugger (Adancurusul/embedded-debugger-mcp, 202 stars), Intelliconnect Service Style (ruanrongman/IntelliConnect, 147 stars), Debugging Executions (n8n-io/n8n, 207k stars) and ast-grep Structural Search (code-yeongyu/oh-my-openagent, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Saleae Analyzer?
pigweed-project (a GitHub organization) maintains it in pigweed-project/pigweed, which has 548 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 10, 2026.
Source: pigweed-project/pigweed on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.