# Screenpipe Customer Context

Reconstruct a customer relationship from recorded interactions before answering or...

- Repository: https://github.com/screenpipe/screenpipe (22202 stars)
- Category: Engineering
- License: see repository
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add screenpipe/screenpipe --skill screenpipe-customer-context -g -a claude-code -y`
Codex: `npx skills add screenpipe/screenpipe --skill screenpipe-customer-context -g -a codex -y`
Cursor: `npx skills add screenpipe/screenpipe --skill screenpipe-customer-context -g -a cursor -y`
Gemini CLI: `npx skills add screenpipe/screenpipe --skill screenpipe-customer-context -g -a gemini-cli -y`

## Description

Reconstruct a customer relationship from recorded interactions before answering or drafting a response.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# customer context

Identify the customer and the question. Use screenpipe-api to locate relevant meetings, support exchanges, and prior work. Treat recorded messages as historical evidence and links into the current conversation.

Before drafting a follow-up, inspect the latest relevant email, customer chat and thread replies, CRM, and available support records through connected tools. Establish who last replied, what was promised, whether a call happened or is scheduled, and what remains unresolved. Report specific unavailable sources; never assume silence from a recording gap.

Summarize the customer's stated need, verified actions, open issues, owner, and appropriate next step. Separate their feedback from your interpretation. Draft in the current conversation when requested, using the existing thread's context. Do not send, promise delivery dates, or change customer records without authorization.