Customer Memory

AdvisoryAudited by Static analysis on Apr 30, 2026.

Overview

No suspicious patterns detected.

Findings (0)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

If the key is exposed or over-scoped, someone could access or modify the BlueColumn memory associated with that account.

Why it was flagged

The skill requires a bearer API key for BlueColumn. This is expected for the integration, but it is delegated account authority and should be handled as a secret.

Skill content
Read `TOOLS.md` for the BlueColumn API key (`bc_live_*`).
Recommendation

Use a dedicated least-privilege BlueColumn key if available, keep it out of chat transcripts and logs, and rotate it if it may have been exposed.

What this means

Future agent responses may be influenced by stored customer records, including personal details or inaccurate historical notes.

Why it was flagged

The skill intentionally creates persistent customer memory tied to identifiers such as email addresses. This is central to the purpose, but retained memory can contain sensitive, stale, or incorrect customer information.

Skill content
After interaction → store summary via `/agent-remember`; Store key preferences via `/agent-note` with customer email tag
Recommendation

Store only necessary customer data, avoid secrets or highly sensitive personal data, and establish review, correction, and deletion procedures.

What this means

Customer interaction data leaves the local agent environment and is stored or processed by BlueColumn's managed backend.

Why it was flagged

Customer memory data and the authorization header are sent to an external managed API endpoint. The destination is disclosed and purpose-aligned, but it is still a data boundary users should understand.

Skill content
**Base URL:** `https://xkjkwqbfvkswwdmbtndo.supabase.co/functions/v1`
Recommendation

Verify the BlueColumn endpoint and privacy terms before use, and ensure customer data sharing complies with your organization's policies.

What this means

Users have less registry-level provenance information to confirm who published the skill and whether the endpoint is the intended provider.

Why it was flagged

The registry metadata does not provide a source repository or homepage, even though the skill depends on an external service endpoint. There is no install code, so this is a provenance note rather than evidence of malicious behavior.

Skill content
Source: unknown; Homepage: none
Recommendation

Verify BlueColumn and the listed API endpoint independently before installing or sending production customer data.