iceman1001
- 4 skills
- 0 followers
- 12 hours ago last updated
- ▌ Rigol Scope · iceman1001 bundleDrive a Rigol oscilloscope (DS2000-series / DS2302A) over LAN with `rigol.py` - configure channels/trigger/timebase, capture one-shot and delayed events, measure VMIN/VMAX/dips, dump full waveforms to CSV, and grab PNG screenshots. Use whenever you touch the scope; do NOT hand-roll `lxi scpi`.
- ▌ Ilspy Decompile · iceman1001 bundleRun the ilspycmd CLI on .NET assemblies to decompile them to readable C# BEFORE reading or analyzing them. Use this skill any time the user provides a `.dll`, `.exe`, `.netmodule`, `.winmd`, or `.nupkg` file and wants Claude to read, analyze, explain, audit, reverse-engineer, debug, extract secrets/keys/URLs from, or understand it — especially if the file is a compiled managed binary rather than source. Trigger this skill even when the user does NOT explicitly say "decompile" — the goal is that Claude is always reasoning about C# source rather than IL or opaque bytes. Also trigger when the user points at a directory of assemblies (e.g. a `bin/Release/` dump, a plugin folder, or an extracted NuGet package) and asks about its behavior. Do NOT trigger for source files (`.cs`, `.fs`, `.vb`), for native unmanaged PE binaries, or when the user explicitly asks about raw IL, metadata tables, or byte-level questions.
- ▌ Timestamp Hunter · iceman1001 bundleScan a byte array, binary file, hex string, or base64 blob for embedded date/time values across many encodings (unix32/64, unix-ms, Windows FILETIME, Apple NSDate, OLE date, HFS, DOS date-time, GPS time, and textual ISO-8601/RFC-2822) in both endiannesses. Use any time the user gives Claude raw bytes, a binary file, hex dump, memory dump, packet capture, firmware, or unknown binary blob and wants to know when it was created, what dates are in it, or whether it has timestamps. Trigger on phrases like "find dates in this", "are there timestamps", "when was this made", "what's in this binary", "decode these bytes", "reverse engineer this file", "what are these 8 bytes" — even if the user does not say "timestamp". Also trigger for forensics, malware analysis, and firmware reversing tasks. Do NOT trigger for text-only inputs where dates are already visible.
- ▌ Webcrack Deobfuscate · iceman1001 bundleRun the webcrack CLI on JavaScript files to deobfuscate, unminify, and unbundle them BEFORE reading or analyzing them. Use this skill any time the user provides a `.js`, `.mjs`, or `.cjs` file and wants Claude to read, analyze, explain, audit, modify, reverse-engineer, debug, or understand it — especially if the file appears minified, bundled (webpack/browserify/rollup/parcel), or obfuscated (obfuscator.io, string arrays, control-flow flattening, hex identifiers like `_0xabc123`). Trigger this skill even when the user does NOT explicitly say "deobfuscate" — the goal is that Claude is always reasoning about readable code rather than mangled output. Also trigger when the user pastes a long single-line JavaScript blob into chat. Do NOT trigger for clearly hand-written, well-formatted source files.