# Configure BeReach and Review Outreach Memory

Conflicting saved rules can make outreach drafts inconsistent. This skill checks BeReach setup, reviews outreach instructions, and guides cleanup after user approval.

## Install

```bash
npx skillstore add bereach-ai/bereach-setup
```

## Metadata

- Status: approved
- Slug: bereach-ai-bereach-setup
- Skillstore revision: r1
- Version status: missing
- Tree hash: 8f5ffca9785273e084f249382ade5d6b4409cc03e4538f458b67f811ade3991d
- Author: bereach-ai
- GitHub username: bereach-ai
- Repository: https://github.com/bereach-ai/linkedin-prospecting-skills/tree/6967fde3a1b93fd84e2dfa6be39f56113d79ceca/skills/bereach-setup
- Ref: 0b5375d5ff31ef8f8f23150e2d3ac5978ea0441f
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network, filesystem
- Quality score: 60
- Public page: https://skillstore.pages.dev/skills/bereach-ai-bereach-setup
- Manifest: https://skillstore.pages.dev/api/skills/bereach-ai-bereach-setup/manifest

## Capabilities

- Check BeReach connector status and provide plan or connection setup guidance.
- Identify missing companion outreach skills and describe installation options.
- Inventory saved voice, offering, persona, and previous targeting information.
- Classify observed outreach rules as keep, move, or delete.
- Guide approved memory updates and direct users through manual cleanup.
- Present setup checks and rule reviews using the bundled artifact layouts.

## Use Cases

- Prepare a New Outreach Workspace: Check connectivity, identify missing skills, and inventory saved outreach information before drafting messages.
- Resolve Conflicting Client Instructions: Review relevant project rules and propose approved changes while keeping each client's voice and offering information separate.
- Review a Local Claude Code Setup: Inspect skill availability, review accessible outreach instructions, and choose project-local or account-wide installation guidance.

## Prompt Templates

### Check My Setup

```
Check my BeReach connection and available outreach skills. Show what is missing without changing configuration or memory.
```

### Audit Outreach Rules

```
Audit only these outreach-related rules: [redacted excerpts]. Classify each as keep, move, or delete, explain why, and wait for approval.
```

### Apply Approved Memory Changes

```
Apply only my approved changes: [changes]. Preserve existing offering details and save replacement voice information before removing old entries.
```

### Review Setup and Language Boundaries

```
Review my setup for [languages]. Preview remote setup steps for approval, separate language-specific voice records, and verify approved cleanup without changing unrelated instructions.
```

## Limitations

- BeReach tool access and an eligible plan are needed for connected operations.
- Complete rule evaluation depends on companion outreach skills not bundled here.
- Unavailable memories and project instructions require user-provided excerpts.
- Account memory cleanup may require manual actions; referenced remote setup instructions can change.

## Best Practices

- Share only relevant, redacted outreach rules and verify which information the assistant actually inspected.
- Review remote setup instructions and confirm configuration changes before installation.
- Approve specific cleanup actions and preserve replacement records before deleting existing entries.

## Anti Patterns

- Pasting all account memories or client files without checking for sensitive information.
- Deleting saved instructions before reviewing the proposed changes.
- Treating unavailable companion skills or unseen memory as already inspected.

## Security Audit

- Audited at: 2026-11-14T17:24:37.613\+00:00
- Summary: All 24 static findings are false positives involving Markdown, documented installation paths, or legitimate memory operations with approval safeguards. Two contextual risks remain: mutable remote setup instructions and requests for unrelated memory content. No evidence found of malicious exfiltration, shell payloads, or audit-directed prompt injection.

## Stats

- Views: 0
- Downloads: 3
- Favorites: 0
- Popularity score: 0
