메뉴
Add or run libcrafter packet behavior validation through oracle specs, backend adapters, offline checks, pcap checks, live checks, and artifacts. Use when packet behavior changes need validation coverage.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Provision and use one disposable remote endpoint provider target for libcrafter packet work. Use for single-endpoint raw sends, captures, debugging, artifact collection, or endpoint teardown; use lab-session for coordinated multi-endpoint oracle/probe workflows.
Add or maintain libcrafter lab provider adapters, capability contracts, provider matrix tests, and documentation for substrate-independent oracle and probe execution.
Provision, use, collect, and tear down multi-endpoint libcrafter lab sessions across Hetzner, QEMU, VirtualBox, and future lab providers. Use when oracle, probe, or generated tools need provider-backed packet work that must be independent of the developer machine.
Open, update, title, review, or prepare libcrafter pull requests so commits are ready for rebase-and-fast-forward landing and required validation is documented.
Use ignored .scratch workspaces for experiments, disposable prototypes, network probes, QEMU or dongle labs, generated exploratory code, and any task where the user asks to make a scratch folder or wants code/scripts that should not be committed until promoted.
Create, amend, reword, split, squash, or prepare libcrafter commits with the repository's Conventional Commits policy and scoped staging discipline.
| name | packet-validation |
| description | Add or run libcrafter packet behavior validation through oracle specs, backend adapters, offline checks, pcap checks, live checks, and artifacts. Use when packet behavior changes need validation coverage. |
Use this skill when a change affects packet behavior, including:
tools/oracle specs first so the expected behavior is
data-driven before backend code changes.tools/oracle/engine/backends/.
Do not add ad hoc backend snippets elsewhere.tools/oracle/run offline --profile <profile> --seed <seed> --count <count>.tools/oracle/run live, tools/probe/run,
and lab-backed appliance providers. Start with local dry-run providers and
then lab dry-runs for every provider involved:
tools/lab/run plan --provider <provider> --dry-run --profile smoke --seed 1 --role stimulus --role targettools/oracle/run live --provider <provider> --dry-run --profile smoke --seed 1 --count 10tools/probe/run --provider <provider> --dry-run --profile smoke --seed 1 --count 10
Inspect appliance_runtime metadata and request coarse profiles such as
wan-raw, lan-raw, whad-serial, or dot11-monitor instead of
protocol-specific endpoint capabilities. Use persistent asset leases for
prepared dongle VMs before any whad-serial or dot11-monitor live path.
Use lab-session for multi-endpoint provider-backed oracle/probe execution
and lab-provider when provider capability contracts or adapters change.
Preserve artifacts from any provider-backed run. Real provider execution
requires protected manual confirmation.Add packet behavior coverage through specs and backend adapters, not by creating standalone reference-backend code paths outside the oracle backend tree.