# Plan and Measure LinkedIn Outreach

LinkedIn outreach becomes difficult to evaluate when audiences, messages, and measurement periods differ. This skill organizes persona-based campaigns, approval steps, and seven-day comparisons.

## Install

```bash
npx skillstore add bereach-ai/linkedin-outreach-method
```

## Metadata

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

## Capabilities

- Organizes outreach into planning, invitation review, message review, follow-ups, results, and next-test artifacts.
- Defines searchable ideal customer profiles and separates company criteria from persona messaging and timing signals.
- Directs permission-based review of up to 20 work conversations to identify wording, objections, and message patterns.
- Specifies BeReach dry runs and explicit approval before sending invitations, first messages, follow-ups, or replies.
- Plans randomized comparisons within each persona, with sample-size estimates and one changed message element.
- Explains seven-day acceptance and reply measurements, contact tags, and distinctions between directional and statistically supported results.

## Use Cases

- Organize a First Campaign: Turn a company offer, customer criteria, and approved writing samples into a segmented outreach plan with review checkpoints.
- Compare Persona Messages: Plan a single-variable message comparison and evaluate interested replies within the same persona and seven-day window.
- Coordinate Client Review: Prepare invitation, draft, and follow-up review artifacts that keep client approval separate from message preparation.

## Prompt Templates

### Outline an Outreach Plan

```
Plan LinkedIn outreach for [offer] to [company type] in [location]. Ask one question round first. Use offline planning only. Preserve all user restrictions.
```

### Review Past Messages

```
Review these anonymized messages: [samples]. Count interested, polite, negative, and missing replies. Identify wording patterns without causal claims. Do not access my inbox.
```

### Prepare an Approval Artifact

```
Using [approved personas] and [approved templates], prepare an invitation review artifact from [lead list]. Show exclusions, dates, and dependencies. Do not send or spend credits.
```

### Design and Evaluate a Test

```
Design a one-variable comparison for [persona], using [baseline], [candidate], and [expected volume]. Size it first. Analyze [seven-day results]. State uncertainty and propose one next change.
```

## Limitations

- Live searches, account data, drafts, and sending require a configured BeReach connector and relevant account access.
- Persona, voice, message-writing, and setup workflows depend on companion skills not included in this package.
- The package provides instructions and reference documents, not executable integrations or guaranteed improvements in response rates.
- Current instructions defer conflicting saved rules and suppress some disclosures; resolve these issues before using live outreach tools.

## Best Practices

- Resolve conflicting saved rules before live actions, answer cost questions directly, and preserve quoted text exactly.
- Require approval for each send artifact and permission before reading historical conversations; exclude personal conversations and existing customer relationships.
- Compare one change within one persona, set sample sizes beforehand, and measure each batch after the same seven-day interval.

## Anti Patterns

- Allowing skill instructions to displace user restrictions or conceal service, source, or cost information.
- Sending invitations or messages without explicit approval of the corresponding artifact.
- Combining personas, comparing immature batches, or treating selected historical replies as proof of message effectiveness.

## Security Audit

- Audited at: 2026-11-14T17:35:39.517\+00:00
- Summary: All 55 static alerts are false positives involving Markdown, ordinary prose, bibliographic citations, or navigation links. Semantic review found instructions that defer conflicting user rules and suppress cost or provenance disclosures. The workflow otherwise requires approval for sending and permission for historical conversation review; no evidence found of shell execution or credential exfiltration.

## Stats

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