Set up the Algolia JavaScript v5 client with separate credentials for browser searches and server writes. Define environment settings, restrict each key’s permissions, and verify operation through read-only searches or writes to a disposable test index.
中文简介正在准备中。当前显示英语简介。
Install and verify the Algolia JavaScript v5 client with least-privilege credential separation. Use when bootstrapping a backend, browser search client, or environment configuration. Trigger with "install Algolia", "configure Algolia auth", or "Algolia API key setup".
实测评分 未实测
查看安装方法安装前可以查看交给 AI 代理的指令内容。
This skill establishes the package and credential boundary before feature work. It distinguishes the application ID from API keys and separates browser search from trusted write operations.
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.
algoliasearch v5 imports and client-level methods; do not introduce the removed initIndex pattern.Load credentials through the repository's approved secret mechanism. Never print values, commit .env files, or use the Admin key as the default backend credential.
Do not install dependencies, create provider keys, alter secret stores, or rotate existing credentials outside the repository and account scope provided.
Return the dependency diff, client factories, environment-name contract, key/ACL matrix, verification results, secret-scan evidence, and remaining setup actions.
| Condition | Response |
|---|---|
| v4 API appears in code | Use the official v5 migration guide before mixing patterns. |
| Key rejected | Verify application pairing, ACL, restriction, and environment. |
| Write key enters browser build | Stop, remove it, and rotate if exposed. |
| No safe test index | Limit verification to read-only search. |
Use this compact input and expected handoff to calibrate scope and evidence quality.
Input:
runtime=node; package-manager=pnpm; client-major=5; browser=search-only
Expected handoff:
read-check=pass; write-check=disposable-index-only; exposed-write-key=none
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
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.
中文简介正在准备中。当前显示英语简介。