Menu
Auth/lab ref: Saleae Logic 2 capture and export workflow: `.sal` traces, raw CSV export, analyzer-table export, and automation API control.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Drive the MCPwn Kali-backed MCP server cleanly and fast: create a session, discover tools via the catalog (list_catalog/get_tools/get_tool/run_tool) instead of guessing names, pick the right execution path (execute_command vs detach+poll_job vs interactive shell), move files with the correct mechanism (write_workspace_file, request_upload/request_download data plane, import_artifact_to_workspace, upload_to_target, list_payloads/get_payload), and bring up connectivity (tunnel_up VPN/proxy/forward, tunnel_revshell, penelope reverse shells, run_in_shell/stabilize_shell). Use whenever running MCPwn / mcpwn_* tools, a Kali MCP, or when a run stalls on timeouts, lost output, missing routes, wrong tool names, or clumsy file transfer.
Keep the context window lean when reading large data. Use before opening big files, logs, dumps, PCAPs, decompiler output, research corpora, or a folder of worker artifacts. Enforces grep-first + windowed reads, extract-don't-hoard, and context quarantine (delegate a huge read to a sub-agent that returns a digest).
Auth assessment: web impact-validation; SQLi, SSTI, XXE, command injection, SSRF, XSS, uploads, deserialization, smuggling, WAF/parser checks.
Mode: /1337 - structured operator behaviour for coding and security; forces explicit reasoning, fast decisions, todos/lists, exact terms, evidence, verification, safety override.
Lab/CTF: pwn/binary challenges; native binaries, memory corruption, format strings, heap/ROP/SROP, shellcode artifacts, seccomp, kernel labs.
Auth/lab: reverse engineering methodology; malware triage, patch diffing, firmware/protocol RE, protections, exploitability handoff evidence.
| name | saleae-logic-2 |
| description | Auth/lab ref: Saleae Logic 2 capture and export workflow: `.sal` traces, raw CSV export, analyzer-table export, and automation API control. |
| compatibility | Windows, macOS, Linux; Saleae Logic 2 application; optional Python automation API. |
| metadata | {"author":"AeonDave","version":"1.0"} |
Use this when hardware traces need to become something analyzable instead of just pretty waveforms.
Use Saleae Logic 2 when you need to:
.sal captures and inspect digital or analog tracesIn Logic 2, use the three-dot menu next to Data and choose Export Table.
Use Options in the lower-right corner, then Export Raw Data. Choose channels, time range, format, and destination.
Use the three-dot menu next to a specific analyzer and choose Export to TXT/CSV.
from saleae import automation
with automation.Manager.connect() as manager:
capture = manager.load_capture("trace.sal")
capture.export_raw_data_csv("export_dir")
capture.close()
Key automation capabilities include:
Manager.connect() or Manager.launch()load_capture() for existing .sal filesexport_raw_data_csv() and export_data_table()save_capture() for .sal outputNo bundled scripts/, references/, or assets/.
Use Saleae's official export documentation and Logic 2 automation API docs for version-specific details.