What problem does it solve? After writing a Yaklang hot-patch or codec plugin, developers struggle to confirm it actually works before loading it into Yakit. This Skill provides a verification workflow using the yaklang source engine and four yak CLI commands that exercise the same gRPC hook execution paths as the Yakit UI. ## Core Features & Use Cases - Source Engine Workflow: Run any .yak script via go run common/yak/cmd/yak.go or a prebuilt binary to test against the latest engine capabilities. - Four Validation Commands: yak hotpatch-mitm, hotpatch-global, hotpatch-webfuzzer, and codec-plugin feed real request/response files through the actual MixPluginCaller and MutateHookCaller chains, printing rewrite evidence to stdout. - Source-Level MITM Debugging: Grep recipes for locating hook signatures, test cases, and forward/drop semantics inside the yaklang repository when hook behavior diverges from expectations. - Use Case: You wrote a Web Fuzzer encryption hot-patch and want proof it decrypts responses correctly—run yak hotpatch-webfuzzer --script x.yak --request req.txt --response rsp.txt and inspect the printed evidence before pasting the script into Yakit. ## Quick Start Ask the AI to validate your hot-patch script by running the appropriate yak hotpatch command against a sample request file and checking the stdout evidence.