{"id":49249,"plugin_id":"plugin_asdk_app_6abfd6483d1c81919c2f92c63590a6f9","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:39:09.197Z","digest":"7b102bf976b3aa4ac6bc64dbd464c7bda73388e3f374386e29cd6b57df4e551c","against":null,"payload":{"description":"Use when a user wants to inspect an authorized public site's static tracking signals, grade consent evidence, or obtain a tracker remediation playbook.","included_files":[],"name":"consent-evidence-review","skill_md_contents":"---\nname: consent-evidence-review\ndescription: Use when a user wants to inspect an authorized public site's static tracking signals, grade consent evidence, or obtain a tracker remediation playbook.\n---\n\n# RegSentry consent evidence review\n\nUse RegSentry as a technical evidence aid, not a legal compliance authority.\n\n- Call `inspect_site_tracking` only after the user confirms they own or are authorized to test the public domain.\n- Treat a static inspection as an observation; it does not prove whether runtime tracking fired before or after consent.\n- Use `interpret_consent_evidence` for redacted, caller-supplied observations.\n- Use `get_remediation_playbook` for reviewable guidance; it does not change a website or verify a fix.\n- Never characterize a result as legal advice, a compliance certification, or a liability determination.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}