Diagnose Algolia request, credential, index, task, and query failures from concrete evidence. Use when an integration returns 4xx or 5xx responses, stale results, or unexpected empty hits. Trigger with "debug Algolia error", "Algolia 403", or "Algolia search failed".
インストールする前に、エージェントに与えられる指示の中身を確認できます。
This skill turns an Algolia symptom into a reproducible diagnosis. It favors the response status, message, request ID, client version, operation, and target index over generic error folklore.
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.
Inspect only redacted key metadata and ACL intent. Never print, paste, or replace a credential with an Admin key merely to make a failing request succeed.
Do not broaden ACLs, rotate keys, change production settings, or replay writes until the target and failure class are confirmed.
Return the symptom, evidence, root-cause hypothesis, ruled-out alternatives, minimum fix, verification result, and any remaining uncertainty.
| Condition | Response |
|---|---|
| 401 or 403 | Verify application/key pairing and required ACL; do not escalate privilege blindly. |
| 404 | Confirm endpoint, application, and exact index name. |
| 429 | Honor the response and measure request pressure before adding bounded retry. |
| Stale result | Wait for the specific task and verify the queried index. |
Use this compact input and expected handoff to calibrate scope and evidence quality.
Input:
operation=saveObjects; status=403; index=products_stage
Expected handoff:
cause=missing-addObject-ACL; fix=request-scoped-key; admin-key-used=no
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Build a synthetic-data CI gate for customer-controlled Abridge integration code without calling undocumented vendor interfaces. Use when adding regression checks to an Abridge deployment repository. Trigger with "test the Abridge integration".
日本語の概要は準備中です。原文の説明を表示しています。
Triage Abridge recording, note-review, Epic handoff, and access failures from observed evidence without inventing vendor error codes. Use when an Abridge clinical workflow is degraded. Trigger with "diagnose this Abridge issue".
日本語の概要は準備中です。原文の説明を表示しています。
Design and verify the clinician workflow from consent through recording, draft review, Linked Evidence, and final note disposition. Use when implementing or auditing an Abridge clinical documentation pathway. Trigger with "map the Abridge note workflow".
日本語の概要は準備中です。原文の説明を表示しています。
Verify the approved handoff of clinician-reviewed Abridge note sections into Epic templates and downstream workflows. Use when configuring or auditing Abridge-to-Epic documentation flow. Trigger with "verify the Abridge Epic handoff".
日本語の概要は準備中です。原文の説明を表示しています。
Evaluate Abridge adoption, workflow value, and avoidable operational friction without inventing prices or vendor billing meters. Use when reviewing an Abridge rollout or renewal. Trigger with "analyze Abridge value".
日本語の概要は準備中です。原文の説明を表示しています。
Produce a PHI-minimized Abridge support bundle with provenance, redaction, and protected escalation boundaries. Use when support needs reproducible evidence for an Abridge issue. Trigger with "build an Abridge debug bundle".
日本語の概要は準備中です。原文の説明を表示しています。