Review records and user events sent to Algolia. Maps data flows, identifies unnecessary fields, and develops correction and deletion procedures with verification evidence, giving privacy owners a technical basis for reviewing data handling.
中文简介正在准备中。当前显示英语简介。
Design and audit the data lifecycle for records and user events sent to Algolia. Use when minimizing indexed fields, handling deletion requests, or documenting retention and privacy boundaries. Trigger with "Algolia privacy", "delete Algolia user data", or "index data review".
实测评分 未实测
查看安装方法安装前可以查看交给 AI 代理的指令内容。
This skill maps which data leaves the source system, how it becomes searchable records or events, and how correction and deletion propagate. It does not claim legal compliance; it produces technical evidence for the responsible privacy owner.
Use Read, Glob, and Grep to inspect local code, configuration names, tests, and dependency versions. Use WebFetch only for current official Algolia documentation. Use Write or Edit only after identifying the target files, constraints, and verification plan.
attributesToRetrieve as response shaping, not as a substitute for excluding sensitive data from records.Use a restricted backend write key for record changes and the documented authorization for user-data deletion. Never include raw secrets or direct personal identifiers in logs or example events.
Do not make legal conclusions, bulk-delete records, change retention policy, or expose protected values while verifying a request.
Return the data-flow map, field inventory, minimization changes, deletion/correction procedure, verification evidence, unresolved provider retention questions, and named policy owner.
| Condition | Response |
|---|---|
| Identity mapping missing | Stop and reconcile the source identity before deletion. |
| Deletion task incomplete | Retain the task ID and verify state before closing. |
| Event token contains PII | Stop sending it and escalate remediation. |
| Policy answer unavailable | Record the question for the privacy owner or provider. |
Use this compact input and expected handoff to calibrate scope and evidence quality.
Input:
request=privacy-123; surfaces=records,events; indices=customer_search
Expected handoff:
records=removed-and-verified; events=requested; legal-determination=not-made
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Add a synthetic-data CI gate for customer-owned Abridge integration code. Test consent handling, note-review handoffs, redaction, and rollback behavior with mocked vendor boundaries, without connecting CI to a live Abridge or EHR tenant.
中文简介正在准备中。当前显示英语简介。
Triage Abridge recording, note review, Epic handoff, and access problems using observed symptoms and approved guidance. Identify the affected workflow stage, organize a minimal timeline, and prepare a redacted escalation record for the responsible team.
中文简介正在准备中。当前显示英语简介。
Map and review an Abridge clinical documentation workflow from consent and recording through draft review, evidence checks, edits, and final disposition. Keep clinician approval explicit, identify failure exits, and separate verified facts from tenant-specific details and pending approvals.
中文简介正在准备中。当前显示英语简介。
Audit how clinician-reviewed Abridge note sections map into Epic templates and downstream workflows. Use approved test records to document destinations, exceptions, evidence, rollback steps, and a go or no-go decision for a specific environment.
中文简介正在准备中。当前显示英语简介。
Review Abridge adoption and workflow value using local usage records, clinician feedback, and verified contract costs. Build an evidence based decision table covering adoption, quality, support burden, and options to expand, hold, or improve the rollout.
中文简介正在准备中。当前显示英语简介。
Prepare a bounded support bundle for an Abridge issue using allowlisted operational details such as versions, coarse timestamps, and correlation references. Exclude recordings, transcripts, patient identifiers, credentials, and unrestricted logs, then document redactions and review details.
中文简介正在准备中。当前显示英语简介。