Plan and build an Algolia indexing workflow from an authoritative dataset. Validate records and stable IDs, choose incremental updates or full replacement, wait for indexing tasks, verify search results and settings, and document rollback steps.
中文简介正在准备中。当前显示英语简介。
Build a reliable Algolia indexing pipeline for full replacements, incremental updates, settings, synonyms, and rules. Use when a source of truth must publish deterministic search state. Trigger with "Algolia indexing workflow", "replace index records", or "sync Algolia".
实测评分 未实测
查看安装方法安装前可以查看交给 AI 代理的指令内容。
This skill designs the write path from an authoritative dataset to Algolia. It separates record transformation, validation, transport, task completion, and publication so a failed run cannot silently leave ambiguous search state.
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.
objectID values from source identities and reject duplicates before upload.saveObjects for bounded upserts and replaceAllObjects only for an intentional full-state replacement.Run indexing only from a trusted backend with a custom key restricted to the target indices and required write ACLs. Keep search-only keys out of indexing jobs.
Do not run a full replacement, delete records, change settings, or swap a production target until the source snapshot and rollback plan are approved.
Return the data contract, operation choice, validation report, task receipts, post-write checks, deletion behavior, and rollback instructions.
| Condition | Response |
|---|---|
| Duplicate objectID | Fail before upload and report source records. |
| Partial batch failure | Stop publication and preserve successful task IDs. |
| Task timeout | Do not assume failure or success; query task state. |
| Verification mismatch | Keep the prior production target and investigate. |
Use this compact input and expected handoff to calibrate scope and evidence quality.
Input:
source=snapshot-2026-09-10; mode=full-replacement; target=products_next
Expected handoff:
records=48012; tasks=49-complete; sentinel-query=pass; cutover=pending-approval
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
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.
中文简介正在准备中。当前显示英语简介。