When to reach for the Skylos skill

Updated Oct 08, 2026

Invoke the dedicated skill for a failing Skylos gate or safe cleanup:

Use $skylos to triage these SKY-U001 findings after a class rename.
Preserve real runtime callers and keep any exceptions narrowly justified.

skylos separates genuine dead code, implicit runtime callers, stale configuration, and unresolved evidence. Its references cover a Protocol and worker-callback case where renaming an entrypoint exception fixed one finding but left four live helpers reported.

The workflow distinguishes per-definition reporting exemptions from packaged script entry points. It includes explicit full_name rules, a configuration-contract test pattern, an unused-sibling negative control, and guidance for avoiding broad parent rules or vacuous tests. Use the consuming repository's pinned tool and project test environment; the documented 4.33.2 case is not a request to upgrade or downgrade it.

The skill installs with the existing cp -a skills/* command. Like the other skills, its agents/openai.yaml disables implicit invocation; load it explicitly or follow the router's direction. It does not install Skylos, run scans, or change CI policy merely by being loaded.

See migration-0.1.0.md for a summary of the routing changes that introduced this skill.