Security audit
Security checks for vulnerabilities and agentic risk
This skill is a disclosed fact-checking workflow with no executable code, hidden install behavior, or evidence of exfiltration, though users should watch its CSV-saving and article-editing boundaries.
Installers should expect the skill to read article/source material, search for evidence, produce audit CSV/Markdown outputs, and possibly apply accepted factual corrections. Before use, decide where CSV and gold-set files should be saved, avoid feeding unnecessary confidential logs or drafts, and require explicit approval before any article file is modified.
- A direct quote in an article that cannot be found in the reported source is a P0, even if the surrounding story is true. - Near-miss numbers are still mismatches. An audit that reports 5810 when the source says 5817 must flag the difference. - Cross-platform periods are high-risk. If one version reads "2024" and the other "2025", the different year is an error, not a paraphrase. - Regulatory documents exist in specific jurisdictions. Never write "FDA, EU MDR, and China's regulations all say the same thing" without checking the governing text. ## Failure handling
No suspicious patterns detected.
