linkedin-personas
Build Buyer Personas for LinkedIn Outreach
Generic outreach often ignores the buying situation behind a job title. Build evidence-based persona cards and classify leads before preparing targeted messages.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "linkedin-personas" from https://skillstore.io/skills/bereach-ai-linkedin-personas.md and its manifest at https://skillstore.io/api/skills/bereach-ai-linkedin-personas/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "linkedin-personas". Illustrative seller input: water utilities hire us before meter renewals. We offer a district drift check. No customer result is supplied.
Expected outcome:
- Persona: water utility preparing meter renewal; network manager.
- Found by: Network Manager, Head of Water Networks, Distribution Manager.
- Why now: meter renewal approaching; exact window requires confirmation.
- Pain: uncertainty about meter accuracy before renewal (guess).
- Offer: a district drift check, supplied by the seller.
- Proof: None yet.
- Objection answer: awaiting the seller.
Using "linkedin-personas". Illustrative review: two approved cards cover utility network managers and consultancy directors. Three leads have clear, ambiguous, and student titles.
Expected outcome:
- Sami L., Network Manager at a matching utility: Sure by title; network-manager persona.
- Paul V., Project Lead with insufficient company context: To check; persona remains unassigned.
- Lea R., Student: No message; hold for user review.
- Review totals: one sure, one to check, one held.
- Preview only; no contact updates applied.
Security Audit
Medium RiskAll 42 static findings are false positives involving Markdown formatting, French example text, or ordinary research prose. No evidence found of shell execution, weak cryptography, system reconnaissance, or audit-directed prompt injection. A separate transparency concern involves instructions to conceal data provenance while using connected business data.
Confirmed security concerns (1)
Risk Factors
⚙️ External commands (31)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/bereach-ai-linkedin-personas/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/bereach-ai-linkedin-personas?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/bereach-ai-linkedin-personas?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/bereach-ai-linkedin-personas/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/bereach-ai-linkedin-personas.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
bereach-ai. (2026). linkedin-personas security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/bereach-ai-linkedin-personas/audits/1BibTeX citation
@techreport{bereach-ai-bereach-ai-linkedin-personas-2026,
author = {bereach-ai},
title = {linkedin-personas security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/bereach-ai-linkedin-personas/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "linkedin-personas security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "bereach-ai"
date-released: "2026-11-14"
url: "https://skillstore.io/skills/bereach-ai-linkedin-personas/audits/1"
identifiers:
- type: other
value: "skillstore:bereach-ai-linkedin-personas:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Prepare Initial Buyer Personas
Turn known customer situations and real offers into provisional cards before starting a new prospect list.
Review Lead Assignments
Group leads by persona, isolate ambiguous matches, and review proposed tag changes before campaign preparation.
Refine Personas From Replies
Compare repeated objections and buying signals across replies, then propose documented changes for the next outreach test.
Try These Prompts
Build two provisional buyer personas from these customer examples and my existing offer: [details]. Ask only about missing information. Mark assumptions explicitly.
Draft two to four personas using this website and these approved documents: [sources]. Keep sources visible and identify missing proof, offers, and objection answers.
Match these leads to these approved personas: [leads and cards]. Explain assignments using titles, company fit, and dated signals. Hold ambiguous matches. Preview changes without saving.
Review these approved reply excerpts and invitation totals by persona: [data]. Apply the evidence thresholds. Quote supporting replies and propose changed lines only. Do not edit live campaigns.
Best Practices
- Supply real customer situations, existing offers, and your own objection answers before treating cards as validated.
- Keep source details accessible and review permissions before reusing connected records, conversation excerpts, or named customer references.
- Resolve ambiguous assignments and review repeated reply evidence before approving persona changes.
Avoid
- Treating guessed pains, website statistics, or fictional examples as verified customer proof.
- Sorting prospects by age, gender, hobbies, school, personality type, or photographs.
- Sending messages to unresolved leads or changing live campaigns without reviewing the proposed test.
Frequently Asked Questions
What does this skill produce?
Can I use it without Bereach?
Does it write and send LinkedIn messages?
How are uncertain lead matches handled?
When can a persona assumption become confirmed?
What data handling concerns should I review?
Developer Details
Author
bereach-aiLicense
Unknown
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
0b5375d5ff31ef8f8f23150e2d3ac5978ea0441f
Maintenance freshness
11/14/2026
Usage
0 downloads · 0 views
File structure