seam-probe

seam-probe

Use the bundled executable as the interface:

SEAM_PROBE="${CLAUDE_PLUGIN_ROOT}/bin/seam-probe"

The short name seam-probe below means "$SEAM_PROBE". A direct skill install does not include the plugin-level launcher, crate, or hook; install the binary independently on PATH or use the full plugin.

Pick the surface

• seam-probe inspect parses a library to discover exports without loading or executing it.
• seam-probe ffi loads a C-ABI dylib and drives lifecycle, callbacks, and input lanes described by a manifest.
• seam-probe socket sends NDJSON operations to a Unix-domain stream socket using the selected framing.
• seam-probe vocab prints the current stdin/stdout contract.

Run seam-probe vocab as preflight. If the launcher reports that the binary is not built, verify cargo is available and build the pinned crate:

cargo build --release --locked \
  --manifest-path "${CLAUDE_PLUGIN_ROOT}/crate/Cargo.toml" \
  --target-dir "${CLAUDE_PLUGIN_DATA:-${XDG_CACHE_HOME:-$HOME/.cache}/seam-probe}/target"

Then rerun seam-probe vocab. If installed behavior disagrees with this skill, inspect live help and request a plugin update rather than inventing flags.

Investigate progressively

Start with the least assumed knowledge:

1. Inspect an unfamiliar library before writing symbol names into a manifest.
2. Read headers, binding metadata, or the host's loading code to recover the actual ABI and callback-field order.
3. For sockets, inspect the server and client framing code before guessing. Use a small probe only to distinguish remaining plausible framings.
4. Create the smallest manifest that exposes the behavior under test.
5. Reproduce one meaningful operation before expanding into a sequence or fuzzing campaign.

Use references/discover-ffi-symbols.md and references/discover-socket-protocol.md only when discovery is needed.

Read both sides of the seam

The probe emits machine-readable NDJSON on stdout and diagnostics on stderr. The system under test may emit its own stderr, structured logs, panic report, or crash artifact. Capture these streams separately and correlate them by operation, sequence, session, and time.