{"id":18615,"plugin_id":"plugins_6a86f0bc955881919122c7c2d87da0d9","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:14:52.192Z","digest":"b2c9b166cdd3caf2b8392aa5e536f11820769a07fef084e4ca4c0914797f6fdb","against":null,"payload":{"description":"Use when a component may be alive but not ready, healthy, functional, or able to accept work.","included_files":[],"name":"verifier-health-readiness","skill_md_contents":"---\r\nname: verifier-health-readiness\r\ndescription: Use when a component may be alive but not ready, healthy, functional, or able to accept work.\r\n---\r\n# Vérifier health readiness\r\n\r\n## Fonction\r\nDistinguer vie, santé, disponibilité et readiness.\r\n\r\n## Procédure\r\n1. Définir ce que signifient alive, healthy, ready et functional pour le composant.\r\n2. Choisir des checks discriminants reliés aux dépendances critiques.\r\n3. Éviter les probes qui prouvent seulement le processus lui-même.\r\n\r\n## Preuve\r\nChaque état annoncé correspond à une preuve spécifique et utile.\r\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}