{"id":23921,"plugin_id":"plugins_6ab3634387ec81919729f26fb2a8e67b","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:17:50.275Z","digest":"0b000bcebc708f15cf8326c5806100633c67ec0c1daf44dbb538cacb31ee395d","against":null,"payload":{"name":"findings-remediation","description":"Produce prioritized, evidence-backed security findings, remediation plans, and verification checks.","included_files":[],"skill_md_contents":"---\nname: findings-remediation\ndescription: Produce prioritized, evidence-backed security findings, remediation plans, and verification checks.\n---\n\n# Findings, Remediation, and Retesting\n\nWrite concise but actionable findings with: ID/title, severity, confidence, affected resource, evidence/source/time, attack preconditions, impact, recommended fix, operational side effects, and verification/rollback. Prioritize exploitable exposure and identity/data-boundary failures before defense-in-depth gaps. Do not inflate severity or equate a missing best practice with a confirmed vulnerability.\n\nFor each fix, specify whether it is code, Cloudflare configuration, identity, CI/CD, or process work. Give a staged implementation order and tests that demonstrate the control. Retest the original condition, include regression cases (unauthenticated, wrong tenant/object, expired token, malformed input, preview route, cache cross-user), and record residual risk. Clearly state checks not performed and what evidence would close each gap. Never represent partial audit coverage as certification, compliance attestation, or “100% secure.”\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}