deal-context-builder

Construct a source-attributed deal context from Attio CRM, Fireflies, and Google Drive.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/notmehul/mia --skill deal-context-builder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deal-context-builder
Source: https://github.com/notmehul/mia/tree/main/mia/skills/deal-context-builder
Command: npx skills add https://github.com/notmehul/mia --skill deal-context-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Fragmented deal-context data from Attio CRM, Fireflies transcripts, Google Drive, and analyst notes leads downstream analytics to run on incomplete or inconsistent inputs. This skill unifies sources into a single, source-attributed deal-context.json that downstream skills can consume reliably.

Core Features & Use Cases

  • Ingests Attio CRM records, Fireflies transcripts, Google Drive documents, and analyst input to produce deal-context.json.
  • Reconciles conflicting information across sources and attributes evidence.
  • Writes a structured, source-attributed context envelope ready for downstream skills.

Quick Start

Provide the company name and sources (Attio, Drive, transcripts) to generate the deal-context.json in the workspace.

Frequently Asked Questions about deal-context-builder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I unify Attio CRM records and Fireflies transcripts into a single deal context?

A deal context is a structured, source-attributed dataset that reconciles fragmented information from Attio CRM, Fireflies transcripts, and Google Drive into a single validated envelope for reliable downstream analytics.

What is a deal context and why do I need to reconcile conflicting deal data?

A deal context is a structured, source-attributed dataset that reconciles fragmented information from Attio CRM, Fireflies transcripts, and Google Drive into a single validated envelope for reliable downstream analytics.

How do I generate a deal-context.json file from scattered Google Drive documents and analyst notes?

You generate a deal-context.json file by providing the company name and your scattered sources, which triggers inline conflict resolution and evidence attribution to produce the validated context envelope.

Can I use the unified deal context for downstream value chain and competitive landscape analysis?

Yes, the unified deal context exposes a validated envelope specifically designed for downstream skills such as value-chain-mapper, competitive-landscape, trends-analyzer, and feature-comparison.

Does this data unification approach handle conflicting information across Attio and Fireflies sources?

Yes, the data unification process enforces inline conflict resolution across Attio and Fireflies sources, attributing evidence to ensure downstream analytics run on consistent inputs.

What are the limitations of manual deal data unification versus a structured context builder?

Manual deal data unification leads to incomplete or inconsistent inputs for downstream analytics, whereas a structured context builder enforces inline conflict resolution and writes a validated deal-context.json.