Prepare a small, redacted evidence bundle for an Attio integration failure. It captures request details, relevant schema context, retry behavior, and environment metadata while screening out CRM records, personal data, and secrets.
中文简介正在准备中。当前显示英语简介。
Assemble a minimal redacted Attio diagnostic bundle with request fingerprints, schema context, retry evidence, and environment metadata. Use when escalating an Attio integration failure without leaking CRM data or secrets. Trigger with "Attio debug bundle", "Attio support evidence", or "collect Attio diagnostics".
实测评分 未实测
查看安装方法安装前可以查看交给 AI 代理的指令内容。
This skill collects the smallest evidence needed to reproduce or escalate an Attio API problem. Redaction and content review happen before a bundle is written or shared.
Use Read, Glob, and Grep to inspect configuration names, client code, existing logs, and tests without opening secret files unnecessarily. Use WebFetch only for current official Attio documentation. Use Write or Edit only for a reviewed redacted artifact in the approved path.
If a bounded reproduction is approved, use the existing Bearer credential in process memory. The bundle may state credential type, workspace alias, and granted scopes; it must not contain the credential or reusable signature material.
Do not run broad workspace enumeration for diagnostics, collect raw CRM responses, or transmit a bundle until its exact contents and destination are reviewed.
Return a bundle manifest, redaction report, request fingerprint, observed-versus-expected contract, reproduction result, checksum, and sharing disposition.
| Condition | Response |
|---|---|
| Secret pattern is found | Stop, redact, and rescan from the beginning. |
| Evidence contains personal data | Replace it with typed placeholders or counts. |
| Reproduction would mutate data | Use fixtures or request explicit disposable-target approval. |
| Bundle does not answer the incident question | Remove noise and collect only the missing field. |
Input:
incident=attio-query-429; endpoint=/v2/objects/:object/records/query
Expected handoff:
bundle=redacted; secrets=0; fingerprint=complete; sharing=approved
This result makes the escalation artifact useful without exporting customer records.
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
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.
中文简介正在准备中。当前显示英语简介。