Set up a repeatable local workflow for testing Attio data mappings and API responses. Use sanitized test data and offline checks by default, with explicit controls for live writes and records of test resource cleanup.
Establish a repeatable local Attio development loop with sanitized fixtures, a non-production workspace, explicit mutation switches, and cleanup receipts. Use when iterating on Attio mappings or API behavior. Trigger with "Attio local development", "Attio dev loop", or "test Attio locally".
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
This skill makes local iteration fast without turning a shared CRM into a test fixture. Offline contracts are the default; live writes are explicit and disposable.
Use Read, Glob, and Grep to inspect environment loading, client boundaries, fixtures, and tests. Use WebFetch only for current official Attio documentation. Use Write or Edit after confirming the repository path and test-data policy.
Use a least-privilege development workspace token from local secret injection. Do not place the token in a committed environment file, fixture, command transcript, or snapshot.
Live writes, schema changes, bulk operations, and cleanup deletes require an approved non-production target. If workspace identity cannot be proved, remain offline.
Return the fixture matrix, local commands, workspace guard, offline results, live-test disposition, created-resource ledger, and cleanup evidence.
| Condition | Response |
|---|---|
| Fixture contains real CRM data | Remove and regenerate it from synthetic values. |
| Workspace allowlist fails | Keep writes disabled. |
| Live response drifts | Update the contract deliberately after documentation review. |
| Cleanup fails | Stop further writes and report exact disposable IDs. |
Input:
mode=offline-first; workspace=development; live-writes=disabled
Expected handoff:
fixtures=pass; guard=pass; live-test=not-needed; leaked-data=0
This result demonstrates a repeatable development cycle without production data or mutations.
No reviews yet. Tell others what you thought.
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.
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.