What problem does it solve? When a feature that talks to an external service silently stops working — mails do not leave, translations do not update — this Skill guides the diagnosis of where the service key actually lives, what state it is in, and why a green probe does not guarantee a working feature. ## Core Features & Use Cases - Key Location Analysis: Distinguishes owner-created keys stored encrypted in the storage from application-wide keys living in the environment, and separates both from rollout secrets read only by the pipeline. - Integration State Interpretation: Decodes the five states of an integration row (unknown, storage unavailable, not set, nothing to decrypt with, unchecked/working/not working) to pinpoint the real cause of a silent feature. - Probe Limitation Awareness: Explains why a green probe does not prove the feature works, and why the feature itself must be verified after entering a key. - Use Case: Ten days of silent outgoing mail are traced not through server logs but through the integrations screen, which shows "not set" — the key was never created. ## Quick Start Ask the agent to analyze why an external integration such as mail delivery or translation updates is silent, and have it check the integration row state before inspecting logs.
