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

attio-debug-bundle

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

실행 점수 미검증

설치 방법 보기

이럴 때 유용합니다

  • Prepare evidence for an Attio support request
  • Investigate a failed API operation
  • Share diagnostics without CRM data

포함된 파일(2)

  • SKILL.md3.9 KB
  • references/official-docs.md2.1 KB

SKILL.md(원문)

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

Redacted Attio Diagnostic Bundle

Overview

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.

Prerequisites

  • A named incident, repository, and failing operation
  • Redaction rules for tokens, webhook secrets, IDs, and personal data
  • The exact endpoint reference and expected request shape
  • An approved destination for the final bundle

Tool Discipline

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.

Current Contract

  • Collect path templates, not customer-bearing URLs.
  • Preserve status, content type, documented error fields, retry timing, and pagination mode.
  • Record scope names but never token values.
  • Do not dump entire records, attribute values, environment variables, headers, or webhook payloads.

Authentication

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.

Instructions

  1. Define the incident question and minimum evidence fields before collection.
  2. Inventory the local caller, endpoint path template, method, timeout, retry policy, and pagination mode.
  3. Capture one redacted failure fingerprint and one bounded control request if safe.
  4. Add object or list schema identifiers only when needed to explain validation behavior.
  5. Scan the candidate bundle for token patterns, authorization headers, webhook secrets, record values, emails, phone numbers, and full IDs.
  6. Review the redacted output manually, then write the approved bundle and checksum.

Approval Boundaries

Do not run broad workspace enumeration for diagnostics, collect raw CRM responses, or transmit a bundle until its exact contents and destination are reviewed.

Output

Return a bundle manifest, redaction report, request fingerprint, observed-versus-expected contract, reproduction result, checksum, and sharing disposition.

Error Handling

ConditionResponse
Secret pattern is foundStop, redact, and rescan from the beginning.
Evidence contains personal dataReplace it with typed placeholders or counts.
Reproduction would mutate dataUse fixtures or request explicit disposable-target approval.
Bundle does not answer the incident questionRemove noise and collect only the missing field.

Examples

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.

Resources

리뷰

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

댓글

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

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

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

0 / 1,000자

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

같은 저장소의 스킬

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월 25일 업데이트

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월 25일 업데이트

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월 25일 업데이트

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월 25일 업데이트

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월 25일 업데이트

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월 25일 업데이트

jeremylongshore의 스킬 모두 보기

이 스킬의 문제 신고