What problem does it solve? Internal tests, InternalsVisibleTo friendship, and successful in-repo builds can hide a public API that external consumers cannot actually use, extend, or rely on. This Skill audits a library from the consumer's perspective so broken contracts, leaky mutability, and accidental accessibility are caught before release. ## Core Features & Use Cases - Public surface inventory: Enumerates public and protected types, constructors, factories, validators, records, and compiler-generated members against the normative contract and API baseline. - Boundary and immutability audits: Verifies closed vs. open hierarchies, access modifier semantics, defensive copies, collection ownership, and serialization round trips. - External-consumer probes: Builds a minimal temporary project outside the repository that references the packed package to capture exact compiler diagnostics or runtime failures, then cleans up. - Use Case: A NuGet package passes all internal tests but its examples fail to compile after packing; this Skill runs a packed-package consumer probe, reconciles docs and API baselines, and reports findings by severity with file:line evidence. ## Quick Start Ask the agent to review this library's public API and compatibility surface as an external consumer, using a packed-package probe where source inspection is insufficient.
