Collect evidence for reproducible Algolia search or indexing failures, including client versions, reproduction steps, and redacted request details. Package the findings with a file manifest and secret scan results for review before a support handoff.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Collect a bounded, secret-safe Algolia diagnostic bundle for an incident or support escalation. Use when a reproducible search or indexing failure needs portable evidence. Trigger with "Algolia debug bundle", "collect Algolia diagnostics", or "Algolia support evidence".
실행 점수 미검증
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
This skill assembles code, configuration shape, client versions, redacted request evidence, task IDs, and reproduction steps without copying API keys, full records, or unrestricted account data.
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.
Do not fetch, print, validate, or transmit secret values. If a support workflow needs account evidence, use a separately approved read-only credential and preserve only redacted results.
Do not use an Admin key for diagnosis, archive an entire environment, collect production records wholesale, or send the bundle automatically.
Return the reproduction, dependency versions, redacted evidence, artifact manifest, secret-scan result, omitted evidence, and a human-approved handoff path.
| Condition | Response |
|---|---|
| Potential secret found | Remove the artifact or redact it, then rescan. |
| Reproduction mutates production | Stop and move to a disposable target. |
| Bundle exceeds limit | Narrow the time window and fields. |
| Required evidence is sensitive | Describe the gap and request an approved channel. |
Use this compact input and expected handoff to calibrate scope and evidence quality.
Input:
incident=ALG-42; window=10m; target=products_readonly; bundle-limit=5MB
Expected handoff:
artifacts=7; secret-scan=pass; production-records=0; transfer=pending-review
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
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.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.