configure-integration-tests

The skill is largely Benign and coherent with its stated purpose of configuring and auditing integration testing infrastructure across multiple ecosystems. It relies on standard, verifiable sources (package manifests, docker-compose, CI configurations) and does not indicate any explicit credential exfiltration, untrusted binary installs, or covert data flows. Some risk remains around autonomous, automated modification of repository CI/config without explicit per-action user prompts, and the potential to alter critical pipelines if --fix is used indiscriminately. Overall, the footprint is proportionate and aligned with the described goal, with elevated but not malicious risk in automated configuration scenarios.