본문으로 건너뛰기
cccskills
무료GitHub에 공개

algolia-install-auth

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".

jeremylongshore/tons-of-skills-marketplace

실행 점수 미검증

설치 방법 보기

이럴 때 유용합니다

  • Set up Algolia in a JavaScript project
  • Separate browser search keys from server write keys
  • Check configuration and accidental key exposure

포함된 파일(2)

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

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Algolia Install and Authentication

Overview

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.

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

  • Inspect and follow the repository's package manager and lockfile rather than installing an unpinned latest package.
  • Use algoliasearch v5 imports and client-level methods; do not introduce the removed initIndex pattern.
  • Expose only a search-only or appropriately secured key in browser configuration.
  • Use custom keys with minimum ACLs and index restrictions for backend jobs.

Authentication

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.

Instructions

  1. Inspect runtime, package manager, lockfile, existing wrappers, and environment conventions.
  2. Select a compatible pinned v5 version and add it through the native package workflow.
  3. Define separate environment names for application ID, browser search key, and server write key.
  4. Create one client factory per trust boundary and reject missing configuration without echoing values.
  5. Verify browser search with a read-only query and backend writes only against a disposable index.
  6. Scan built assets and source history for accidental write-key exposure.

Approval Boundaries

Do not install dependencies, create provider keys, alter secret stores, or rotate existing credentials outside the repository and account scope provided.

Output

Return the dependency diff, client factories, environment-name contract, key/ACL matrix, verification results, secret-scan evidence, and remaining setup actions.

Error Handling

ConditionResponse
v4 API appears in codeUse the official v5 migration guide before mixing patterns.
Key rejectedVerify application pairing, ACL, restriction, and environment.
Write key enters browser buildStop, remove it, and rotate if exposed.
No safe test indexLimit verification to read-only search.

Examples

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

Resources

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

abridge-ci-integration

무료

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.9천2026년 10월 23일 업데이트

abridge-common-errors

무료

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.9천2026년 10월 23일 업데이트

abridge-core-workflow-a

무료

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.9천2026년 10월 23일 업데이트

abridge-core-workflow-b

무료

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.9천2026년 10월 23일 업데이트

abridge-cost-tuning

무료

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.9천2026년 10월 23일 업데이트

abridge-debug-bundle

무료

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.9천2026년 10월 23일 업데이트

jeremylongshore의 스킬 모두 보기

이 스킬의 문제 신고