okhp3-linkedin-connection-note
Portable, identity-agnostic Agent Skill.
Public-package data boundary
This package and its fixtures contain no execution account, person, project,
campaign, topic, bias, opinion, or private URL. Use placeholders in public
examples and obtain all such context from the current run only.
A connection note has one job: give a stranger a reason to say yes.
Scope
This package drafts connection request notes. It does not send invitations,
choose who to invite, or write follow-up messages. Selection belongs to
okhp3-linkedin-network-plan. Messages and replies belong to
okhp3-linkedin-message.
Process
- Collect the sender fact sheet from the current run: role in plain words,
the one or two public things the sender can honestly say about their work,
the sender's account type, and any topics or phrases the sender wants
avoided. If the fact sheet is missing, return
NEEDS INPUT. Never infer
sender credentials from a profile name or from the recipient's context.
- Determine the note limit. Use the limit the sender states. LinkedIn Help
(retrieved 2026-11-09) documents a 200 character limit and a small monthly
allowance of personalized notes for free accounts, and a 300 character limit
for Premium. Allowances and limits vary by plan and change over time. When the plan is unknown, default to 200 characters
and say that was assumed. Limits change, so confirm in the live dialog.
Leave headroom of at least 10 characters for counting differences.
- For each recipient, read the supplied public context: role, a recent public
post, shared topic, or shared community. Pick one specific hook. A hook is
something only this recipient has said or done. Do not use a title alone as
a hook.
- Draft with this shape, adapted to fit the limit: a short greeting by first
name, one specific hook, one line on why the sender is relevant to that
hook, and an implicit or explicit invitation to connect. No flattery
stacking, no pitch, no ask for a favor, referral, job, or call.
- Keep every note unique. Reusing an opener across a batch is a template
signal. When two recipients share a hook, vary the framing and the order.
- Run
references/note-gate.md. Enforce the character count by counting,
not estimating. Report the count for every note.
- Return the batch table and the gate report. Do not send. Sending is a host
action that needs explicit approval for the specific batch.
Output contract
Return Notes as a table with recipient label, lane or segment, hook used,
note text, and character count against the limit, then Gate report. Missing
sender facts or a recipient with no usable public context returns NEEDS INPUT for that row. Do not fill the gap with a generic note unless the sender
asks for a generic fallback, and label it generic when they do.
Validation
Before return, verify every note is within the limit, no two notes share an
opener, every claim traces to the supplied fact sheet or recipient context,
the voice pass ran, no em dash appears, and no send action is included.
Platform boundary
LinkedIn restricts excessive invitation activity, and all members, Basic and
Premium, are subject to invitation limits. A draft does not establish that the
account can send it. Recipients can also require an email address or restrict
who may invite them. Skip those recipients instead of guessing contact
details. Sending is the sender's own action in their own session.
Current platform reference
Public-neutrality gate
Keep this package portable for public distribution. Do not embed a person name,
account handle or URL, private identifier, employer or organization identity,
product or project name, campaign name, or user-specific subject in instructions,
examples, references, or evaluation fixtures. Resolve account, destination,
audience, subject, links, current facts, and visibility from execution-time
context. Use placeholders or supplied evidence; platform help links may remain.
About
This package is distributed as a portable, identity-agnostic Agent Skill.
It resolves account, destination, audience, subject, and source context at execution time.
MIT License -- free to use, fork, and adapt. A nod to the source is appreciated.
1---2name: okhp3-linkedin-connection-note3description: >4 Draft one personalized LinkedIn connection request note per recipient, within5 the sender's character limit and using only facts the sender supplied. Use6 when the user wants an invite note, a batch of notes for a planned outreach7 wave, or a rewrite of a generic connection request. It returns drafts and a8 gate report only. Do not use for direct messages, replies, or sending.9license: MIT10metadata:11 source: https://skillmd.com/skills/okhp3/okhp3-linkedin-connection-note12 public_artifact: true13 author: Public Agent Skill Library14 version: "1.0.0"15 category: social-posting16 origin: portable-agent-skills17 in_scope: "Drafting a unique, character-bounded LinkedIn connection note per recipient from supplied sender and recipient facts."18 out_of_scope: "Sending invitations, direct messages, replies, target selection, or any claim the sender did not supply."19---2021# okhp3-linkedin-connection-note2223Portable, identity-agnostic Agent Skill.2425## Public-package data boundary2627This package and its fixtures contain no execution account, person, project,28campaign, topic, bias, opinion, or private URL. Use placeholders in public29examples and obtain all such context from the current run only.3031A connection note has one job: give a stranger a reason to say yes.3233## Scope3435This package drafts connection request notes. It does not send invitations,36choose who to invite, or write follow-up messages. Selection belongs to37`okhp3-linkedin-network-plan`. Messages and replies belong to38`okhp3-linkedin-message`.3940## Process41421. Collect the sender fact sheet from the current run: role in plain words,43 the one or two public things the sender can honestly say about their work,44 the sender's account type, and any topics or phrases the sender wants45 avoided. If the fact sheet is missing, return `NEEDS INPUT`. Never infer46 sender credentials from a profile name or from the recipient's context.472. Determine the note limit. Use the limit the sender states. LinkedIn Help48 (retrieved 2026-11-09) documents a 200 character limit and a small monthly49 allowance of personalized notes for free accounts, and a 300 character limit50 for Premium. Allowances and limits vary by plan and change over time. When the plan is unknown, default to 200 characters51 and say that was assumed. Limits change, so confirm in the live dialog.52 Leave headroom of at least 10 characters for counting differences.533. For each recipient, read the supplied public context: role, a recent public54 post, shared topic, or shared community. Pick one specific hook. A hook is55 something only this recipient has said or done. Do not use a title alone as56 a hook.574. Draft with this shape, adapted to fit the limit: a short greeting by first58 name, one specific hook, one line on why the sender is relevant to that59 hook, and an implicit or explicit invitation to connect. No flattery60 stacking, no pitch, no ask for a favor, referral, job, or call.615. Keep every note unique. Reusing an opener across a batch is a template62 signal. When two recipients share a hook, vary the framing and the order.636. Run `references/note-gate.md`. Enforce the character count by counting,64 not estimating. Report the count for every note.657. Return the batch table and the gate report. Do not send. Sending is a host66 action that needs explicit approval for the specific batch.6768## Output contract6970Return `Notes` as a table with recipient label, lane or segment, hook used,71note text, and character count against the limit, then `Gate report`. Missing72sender facts or a recipient with no usable public context returns `NEEDS73INPUT` for that row. Do not fill the gap with a generic note unless the sender74asks for a generic fallback, and label it generic when they do.7576## Validation7778Before return, verify every note is within the limit, no two notes share an79opener, every claim traces to the supplied fact sheet or recipient context,80the voice pass ran, no em dash appears, and no send action is included.8182## Platform boundary8384LinkedIn restricts excessive invitation activity, and all members, Basic and85Premium, are subject to invitation limits. A draft does not establish that the86account can send it. Recipients can also require an email address or restrict87who may invite them. Skip those recipients instead of guessing contact88details. Sending is the sender's own action in their own session.8990## Current platform reference9192- [LinkedIn Help: personalize invitations to connect](https://www.linkedin.com/help/linkedin/answer/a563153) (retrieved 2026-11-09) documents note limits by plan.93- [LinkedIn Help: invitation limit reached](https://www.linkedin.com/help/linkedin/answer/a550555) (retrieved 2026-11-09) documents that all members are subject to invitation limits.9495## Public-neutrality gate9697Keep this package portable for public distribution. Do not embed a person name,98account handle or URL, private identifier, employer or organization identity,99product or project name, campaign name, or user-specific subject in instructions,100examples, references, or evaluation fixtures. Resolve account, destination,101audience, subject, links, current facts, and visibility from execution-time102context. Use placeholders or supplied evidence; platform help links may remain.103104## About105106This package is distributed as a portable, identity-agnostic Agent Skill.107It resolves account, destination, audience, subject, and source context at execution time.108MIT License -- free to use, fork, and adapt. A nod to the source is appreciated.