Security
Secret Exposure Suspicions In Docs
Identify suspected exposed credentials in an authorized document set.
Configure this skill
The page and the file follow your answers.
CRM
Email
Chat
Documents
Calendar
Project tools
6 of 6 systems connected
KeepDirectMissing
Your assistantSKILL.md
Download ↓
When to use it
Identify suspected exposed credentials in an authorized document set.
What it covers
Inputs
Authorized documents, suspected secret types, review scope.
Result
Redacted suspected-exposure findings with location, evidence type, confidence and owner action.
What it uses
CalendarEmailDocumentsSlackProject toolsKeep memoryRead only
For developers
Retrieval instructions
Resolve people, accounts and projects by stable identifiers. Use only the sources this task needs. Cite the source and date for each finding. Keep source systems unchanged.
Data sources
Google Workspace, Slack, GitHub, Keep memory.
Procedure
- Call keep_status and report freshness for: Google Workspace, Slack, GitHub, Keep memory. If a required connector for Secret Exposure Suspicions In Docs is disconnected or stale, say so up front.
- Resolve inputs for Secret Exposure Suspicions In Docs: system, person, time_window, request_id. Default time window: recent access asks and security findings (override if caller provides time_window). Ask only for.
- Run keep_search with these skill-specific intents (keep meaning; adjust wording to corpus):