seam-probe
SolidUse this skill to test, validate, fuzz, or debug a process boundary ("seam") that exposes itself as an FFI dynamic library or a Unix-domain socket — for example probing a Rust runtime hosted in a Swift or Electron app via its C ABI, or sending crafted length-prefixed frames to a daemon's UDS endpoint. The skill teaches how to drive the probe from the CLI, capture both the probe's NDJSON output AND the system- under-test's stderr/logs, and triage failures by correlating the two streams. Reach for it when the user asks to "probe", "fuzz", "exercise", "test the FFI surface", "test the socket protocol", "send raw frames", "discover what a dylib exports", "find a bug in the runtime", "reproduce a crash", or "see why the seam panics or hangs".
Install
Quality Score: 82/100
Skill Content
Details
- Author
- johnkozaris
- Repository
- johnkozaris/jko-claude-plugins
- Created
- 4 months ago
- Last Updated
- yesterday
- Language
- Rust
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
hive-finding-seams
Use when existing code has untestable dependencies that prevent writing tests -- direct construction of collaborators, static or global function calls, tight coupling to external systems, or singleton access patterns. Specifically for identifying substitution points (seams) that make legacy or tightly-coupled code testable without editing at the call site. Do NOT use for greenfield TDD (see tdd), general test writing patterns (see testing), or refactoring already-tested code (see refactoring).
ce-probe-sec
Security-probe a running target — web/API apps or CLI binaries — passive recon by default; smell-test and active-exploit tiers behind explicit opt-in. Twice-attested consent; refuses production; sandboxes binaries; findings, not verdicts. Triggers: security-test/sec-scan/probe a running app for vulnerabilities. Never production. For performance use /ce-probe-perf.
dependency-seam-detection
Trigger: dependency seam detection, hard dependencies. Find seams that make legacy code testable.