wiki-secret-audit

To scan wiki pages for exposed API keys and credentials, apply this Skill to targeted platform spaces, single pages, or search-selected collections. It performs regex-based detection of high-priority secret patterns while excluding common false positives, generating a structured audit report with remediation actions.

A wiki security audit detects high-priority secret patterns including connection strings, bearer tokens, API keys, and private key blocks. The scanner applies regex-based detection to locate these exposed credentials across documentation pages while filtering out common false positives.

Yes, you can audit specific wiki collections instead of an entire space. The Skill supports scoped auditing across single-page, collection, or search-driven scopes, allowing you to prioritize high-risk areas like runbooks, environment configurations, and setup guides.

After finding leaked credentials in documentation, follow the structured audit report's prescriptive remediation steps: remove or redact the exposed secrets, rotate the compromised credentials, and notify relevant stakeholders to reduce the incident blast radius.

You should run a wiki secret detection scan during post-incident investigations to locate leaked credentials, or as part of scheduled security reviews and periodic audits. This helps catch credentials that bypass standard repository secret scanners.