Create a minimal Algolia JavaScript v5 indexing and search proof using a disposable index. Use when verifying credentials, learning the client boundary, or proving first connectivity. Trigger with "Algolia hello world", "first Algolia search", or "test Algolia setup".
インストールする前に、エージェントに与えられる指示の中身を確認できます。
This skill proves the smallest complete write-read-cleanup cycle: create known records, wait for the indexing task, query one record, and remove the disposable index after review.
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 client; methods such as saveObjects, waitForTask, and searchSingleIndex are called on the client.objectID values so verification is deterministic.Use a custom backend key restricted to the disposable index and necessary operations. The browser should never receive this write credential.
searchSingleIndex.Do not use a production index, copy an Admin key into source, or delete an index until its exact disposable name is displayed and approved.
Return package and API evidence, the redacted configuration, write and wait task IDs, search assertion, cleanup result, and next recommended integration step.
| Condition | Response |
|---|---|
| Authentication fails | Verify application/key pairing and required ACL. |
| Search is empty after write | Wait for the recorded task and confirm index name. |
| Unexpected existing records | Stop; the index is not disposable. |
| Cleanup not approved | Leave the index and report its exact name. |
Use this compact input and expected handoff to calibrate scope and evidence quality.
Input:
app=APP…9X; index=skill-smoke-20260910; records=2
Expected handoff:
save-task=complete; expected-object=movie-1; search=pass; cleanup=approved-and-complete
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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".
日本語の概要は準備中です。原文の説明を表示しています。