Set up separate Algolia search targets for development, staging, previews, and production. Define environment selection, credential scopes, reviewed promotion of search settings and data, and cleanup rules for temporary indices, the collections that hold searchable records.
中文简介正在准备中。当前显示英语简介。
Design isolated Algolia development, staging, preview, and production targets with explicit promotion rules. Use when environments share credentials or index names, or previews need bounded search data. Trigger with "Algolia environments", "Algolia staging setup", or "preview index".
实测评分 未实测
查看安装方法安装前可以查看交给 AI 代理的指令内容。
This skill makes environment isolation an application-owned contract. It does not assume one provider topology: separate applications, index namespaces, or a combination may be selected from security, data, cost, and operational requirements.
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 custom keys and secret scopes for each environment. Browser builds receive only the search credential for their resolved environment.
Do not create applications, copy production data, share keys, or delete preview indices until topology and data-policy owners approve.
Return the environment matrix, selected topology and tradeoffs, configuration resolver, key scopes, promotion flow, isolation tests, and lifecycle controls.
| Condition | Response |
|---|---|
| Unknown environment | Fail closed instead of selecting production. |
| Preview requests production data | Reject unless an explicit approved sanitized source exists. |
| Settings drift | Rebuild from versioned artifacts and review the diff. |
| Orphan cleanup uncertain | Report candidates without deleting them. |
Use this compact input and expected handoff to calibrate scope and evidence quality.
Input:
env=preview-482; app=nonprod; index=preview_482_products; data=synthetic
Expected handoff:
resolver=allowlisted; prod-fallback=none; cleanup-after=reviewed-policy
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
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.
中文简介正在准备中。当前显示英语简介。