Skip to content
cccskills
FreePublished on GitHub

algolia-local-dev-loop

Develop and check Algolia record transformations and search queries with credential-free offline tests. When needed, run an optional integration check against a uniquely named disposable index, then verify and clean up its test records without touching production indices.

OriginalShow the original description

Create a fast local development loop for Algolia record transforms and search behavior without contaminating shared indices. Use when iterating on search code, fixtures, or client wrappers. Trigger with "Algolia local development", "mock Algolia", or "test search locally".

Run score Not tested

See how to install

Good for

  • Testing record transformations offline
  • Checking query construction and client behavior
  • Running an optional disposable-index integration test

Files included (2)

  • SKILL.md3.8 KB
  • references/official-docs.md1.3 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Algolia Local Development Loop

Overview

This skill combines deterministic offline tests with an optional disposable-index integration test. It makes the local loop useful without pretending a mock reproduces provider ranking, task timing, or authorization.

Prerequisites

  • A named repository, environment, and Algolia application or index in scope
  • The local lockfile and installed client types as implementation authority
  • A safe read-only query or explicitly disposable test target
  • Current first-party documentation for any provider behavior that affects the change

Tool Discipline

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.

Current Contract

  • Keep record transformation and query construction in pure functions that can be tested offline.
  • Mock only the application-owned client boundary, not internal SDK implementation details.
  • Use unique disposable index names for live checks and never reuse production credentials.
  • Wait for write tasks and clean up live fixtures explicitly.

Authentication

Offline tests need no credential. Optional live tests use a custom key restricted to the disposable prefix and are disabled when credentials are absent.

Instructions

  1. Inspect the current client wrapper, package scripts, fixtures, and test framework.
  2. Extract pure record-shaping and query-building functions with focused unit tests.
  3. Create a typed adapter and mock its application-level responses and failures.
  4. Add an opt-in live test that validates a generated disposable index name.
  5. Write known records, wait, query, assert, and clean up while retaining task receipts.
  6. Document how developers select offline versus live mode and how stale test indices are reported.

Approval Boundaries

Do not require live credentials for the default test command, share a personal Admin key, or clean up any index outside the validated disposable prefix.

Output

Return the local scripts, test boundary, fixtures, live-test guard, cleanup behavior, and evidence for both credential-free and optional integration modes.

Error Handling

ConditionResponse
Credential absentRun offline tests and report the live test as skipped.
Mock diverges from adapterUpdate the adapter contract and its typed fixture together.
Disposable prefix invalidFail before any network write.
Cleanup failsReport the exact retained index for manual review.

Examples

Use this compact input and expected handoff to calibrate scope and evidence quality.

Input:

mode=offline-default; integration=ALGOLIA_LIVE_TEST=1; prefix=dev-$USER-$RUN

Expected handoff:

unit=pass; live=skipped; production-index-access=none

Resources

Reviews

No reviews yet. Tell others what you thought.

Comments

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.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

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.

  • Adding regression checks to an Abridge integration repository
  • Testing consent and note-release handling
  • Checking logs for sensitive data exposure
jeremylongshore/tons-of-skills-marketplace2.9KUpdated Oct 25, 2026

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.

  • Separate recording problems from upload failures
  • Investigate note creation delays and editor issues
  • Identify the responsible team for Epic handoff failures
jeremylongshore/tons-of-skills-marketplace2.9KUpdated Oct 25, 2026

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.

  • Map a clinical note workflow for a care setting
  • Check where consent and patient identity are verified
  • Review draft notes against linked evidence before sign-off
jeremylongshore/tons-of-skills-marketplace2.9KUpdated Oct 25, 2026

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.

  • Checking Abridge note section mappings to Epic templates
  • Auditing a department’s approved documentation handoff
  • Preparing test evidence and a go or no-go decision
jeremylongshore/tons-of-skills-marketplace2.9KUpdated Oct 25, 2026

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.

  • Reviewing adoption after an Abridge rollout
  • Preparing evidence for a renewal decision
  • Comparing workflow outcomes across care settings
jeremylongshore/tons-of-skills-marketplace2.9KUpdated Oct 25, 2026

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.

  • Preparing reviewed evidence for an Abridge support case
  • Documenting redactions and excluded data
  • Collecting approved operational details for an incident
jeremylongshore/tons-of-skills-marketplace2.9KUpdated Oct 25, 2026

See all skills by jeremylongshore

Report a problem with this skill