Plan and verify releases for applications that use Algolia search. Map environments, separate browser search keys from server write keys, prepare index assets, run health and representative query checks, and document rollback steps.
中文简介正在准备中。当前显示英语简介。
Plan and verify deployment of an Algolia-backed application with separated browser and server credentials. Use when releasing search code, index configuration, or event instrumentation. Trigger with "deploy Algolia", "Algolia production rollout", or "search release checklist".
实测评分 未实测
查看安装方法安装前可以查看交给 AI 代理的指令内容。
This skill coordinates application deployment with the Algolia assets it depends on. It treats code, records, settings, keys, and events as separate release surfaces with explicit ordering and rollback.
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.
Provision custom least-privilege keys through the approved secret store. Never place Admin keys in static build variables, client bundles, deployment logs, or preview environments.
Do not overwrite production indices, rotate keys, promote settings, or enable events as an implicit side effect of application deployment.
Return the release topology, environment map, credential classification, ordered deployment plan, smoke evidence, rollback steps, and unresolved approvals.
| Condition | Response |
|---|---|
| Browser bundle contains write key | Stop deployment and rotate the exposed credential. |
| Target index is stale | Hold traffic and complete or rollback indexing. |
| Health check passes but relevance fails | Use representative query gates, not connectivity alone. |
| Rollback target unknown | Do not cut over. |
Use this compact input and expected handoff to calibrate scope and evidence quality.
Input:
release=abc123; environment=production; browser-key=search-only; server-key=custom-write
Expected handoff:
index-task=complete; smoke=pass; representative-queries=pass; rollback=previous-release
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
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.
中文简介正在准备中。当前显示英语简介。