linkedin-voice
Build Your LinkedIn Writing Voice
Generic outreach drafts often lose the sender's writing style. This skill builds a voice card from real messages and checks new drafts against approved examples.
Stop for confirmation before installing.
Review the plan and obtain explicit user consent before changing files.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "linkedin-voice" from https://skillstore.io/skills/bereach-ai-linkedin-voice.md and its manifest at https://skillstore.io/api/skills/bereach-ai-linkedin-voice/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.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-voice". Three supplied messages begin with Hi and a first name, use we, contain no exclamation marks, and omit a sign-off.
Expected outcome:
Voice card: English, draft.
Greeting: Hi plus first name, observed in all three messages.
Pronoun: we, observed in all three messages.
Exclamation marks: none observed.
Sign-off: none observed.
Tone for replies: not established.
Using "linkedin-voice". The approved card forbids the word seamless and exclamation marks. The draft reads: Hi Maya! We build seamless scheduling tools. Is scheduling still manual?
Expected outcome:
Hi Maya, we build scheduling tools. Is scheduling still manual?
Changes: removed the exclamation mark and the forbidden word.
Security Audit
High RiskAll 36 static findings are false positives involving Markdown formatting or ordinary prose. No evidence found of shell execution, weak cryptography, or system reconnaissance. A separate instruction suppresses user-requested cost information while requiring full briefing, creating a budget-control and transparency risk.
Confirmed security concerns (1)
Risk Factors
⚙️ External commands (30)
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-voice/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/bereach-ai-linkedin-voice?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/bereach-ai-linkedin-voice?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/bereach-ai-linkedin-voice/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/bereach-ai-linkedin-voice.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-voice security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/bereach-ai-linkedin-voice/audits/1BibTeX citation
@techreport{bereach-ai-bereach-ai-linkedin-voice-2026,
author = {bereach-ai},
title = {linkedin-voice security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/bereach-ai-linkedin-voice/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-voice 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-voice/audits/1"
identifiers:
- type: other
value: "skillstore:bereach-ai-linkedin-voice:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Keep founder outreach personal
Turn a founder's own successful conversations into a reusable writing profile for new prospect drafts.
Standardize individual seller profiles
Create separate evidence-based voice cards so representatives retain their own greetings, vocabulary, and message tone.
Maintain language-specific client voices
Build approved cards for each client's language and review drafts against their address forms and forbidden wording.
Try These Prompts
Build a draft voice card from these three messages I wrote: [paste messages]. Quote evidence for each field and leave unsupported fields empty.
Compare this draft with my approved voice card: [paste both]. Fix mismatches in greeting, address form, punctuation, and forbidden wording.
Use my samples, a real recipient, and verified facts: [paste inputs]. Apply the available companion frameworks and explain revisions. Draft only; do not send.
Review my saved playbook and these repeated corrections: [paste corrections]. Propose scoped changes and request approval before saving. Ask before any chargeable tool use.
Best Practices
- Provide varied messages you wrote and identify which received substantive replies.
- Review quoted evidence and approve revised samples before saving a playbook containing conversation text.
- Confirm tool costs, data access, and save scope before approving BeReach operations.
Avoid
- Using unedited generated messages as proof of your personal writing style.
- Treating a few positive replies as proof that a message framework improves response rates.
- Approving tool usage without understanding costs or which conversation excerpts will be stored.
Frequently Asked Questions
How many writing samples are needed?
Can I start without answered messages?
What does the voice card record?
Does the skill send LinkedIn messages?
Where are approved writing examples saved?
Are BeReach tool costs addressed safely?
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