What problem does it solve? Perl XS and FFI modules need C libraries to link against, and authors must decide at install time whether to use a system library or build one from source. This Skill guides writing and debugging Alien::Build alienfiles so that probing, building, and flag gathering work correctly on every machine, including air-gapped hosts. ## Core Features & Use Cases - Alienfile authoring: Structure probe, sys, and share blocks correctly, use the PkgConfig plugin with a justified minimum_version, and bundle source tarballs via Fetch::Local for network-free installs. - Correct flag handling: Avoid hardcoded paths by using %{.install.prefix} interpolation, and understand install_prop versus runtime_prop so cflags and libs survive into alien.json. - Consumption and testing: Wire Alien::Base into XS Makefile.PL or FFI::Platypus consumers via configure_requires, and prove both system and share install paths with Test::Alien xs_ok snippets. - Use Case: You are packaging Net::LibSSH and need Alien::libssh to detect a system libssh 0.9+ via pkg-config, fall back to building a bundled tarball with CMake, and expose cflags and libs to your XS module. ## Quick Start Ask the AI to write an alienfile for a C library that probes with pkg-config, falls back to building a bundled tarball with CMake, and shows how an XS module consumes the resulting cflags and libs.