Verify an Algolia setup with a small JavaScript v5 example: write known test records to a disposable index, wait for indexing, search for a record, and report the result. Use it to check credentials and first connectivity safely.
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".
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
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
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
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.