Plan and carry out a migration to Algolia by mapping data, queries, filters, and ranking behavior. Validate a new index against representative searches, then prepare an approved traffic cutover with acceptance criteria and a rollback procedure.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Plan and execute a reversible migration from another search system or legacy index design to Algolia. Use when translating schemas, queries, relevance behavior, or production traffic. Trigger with "migrate to Algolia", "Algolia cutover", or "search engine migration".
실행 점수 미검증
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
This skill treats migration as a measured compatibility program: source data, query semantics, ranking, filters, UI behavior, traffic, and rollback are assessed separately before cutover.
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.
Use separate least-privilege credentials for source reads, Algolia writes, and browser search. Keep all secret material outside migration artifacts.
Do not overwrite the current production index, declare relevance equivalence from a few queries, or retire the source system before rollback expiry.
Return the capability map, data transform, gap register, backfill evidence, query comparison, cutover plan, acceptance decision, and rollback procedure.
| Condition | Response |
|---|---|
| Unsupported query feature | Document the gap and design an approved product alternative. |
| Record counts differ | Reconcile filtering, deletes, and source snapshot boundaries. |
| Relevance regresses | Keep source traffic and tune against the approved query set. |
| Rollback data drifts | Define dual-write or replay before cutover. |
Use this compact input and expected handoff to calibrate scope and evidence quality.
Input:
source=legacy-search; snapshot=snap-184; target=products_algolia_next
Expected handoff:
records=reconciled; query-suite=198/200; two-gaps=owner-review; cutover=not-started
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
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.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.