okhp3-linkedin-message
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 good message is short enough to answer on a phone and specific enough to be
worth answering.
Scope
This package drafts a direct message or counter reply, or a small set of
related messages about one subject with a send order. It does not send,
batch, or schedule messages. For first-touch invite text use
okhp3-linkedin-connection-note. For public conversation use
okhp3-linkedin-comment.
Process
- Gather inputs: the sender's raw intent in their own words, the inbound
message when replying, whatever the sender supplied about the recipient, and
any standing constraints the sender wants honored. A dictated thought is
source material, not a finished draft. Do not invent history between the
parties.
- Tier the recipient using supplied evidence only: peer, senior or high-reach
contact, recruiter or sales sender, or unknown. The tier sets tone and
length. Senior contacts get shorter and more specific. Recruiter and sales
senders get a verification-minded reply, not instant enthusiasm. Unknown
senders get no personal data.
Then set relationship temperature with
references/relationship-tiers.md:
active, dormant, distant, or cold. Temperature sets candor,
attachments, and how the gap or lack of history is acknowledged. Do not
infer warmth the sender did not state.
- Verify recipient facts before using them. A statement about the
recipient's current role, employer, or recent change needs a source from
this run, preferably the recipient's own current profile. Flag a press
release or third-party page as
needs-confirmation; it may be stale.
Describe a role change neutrally.
- Run the recipient-conflict check. If the recipient works for a party the
message or an attachment treats as a competitor, counterparty, or target,
remove that material or return
needs-decision. Attachments follow
temperature: active may carry working files; dormant and cold carry
none in the first message; distant carries at most one that previews
inline when the host supports it.
- Match length to the inbound. A two-line message gets a two- or three-line
reply. A long thoughtful message earns a proportionate answer. Cap first-
touch messages at a few short sentences.
- State the single purpose in one sentence before drafting. Include at most
one small, easy-to-grant ask, such as a viewpoint, a resource pointer, or a
short call later. Do not stack asks. Do not pitch in a first message.
- Draft in the sender's voice by applying
okhp3-linkedin-voice, which
covers contractions, no em dashes, and preserved uncertainty. Keep the
sender's real phrasing where it works. Do not sand it into corporate paste.
- Run
references/message-gate.md. Scrub employer-identifying, confidential,
or agreement-restricted content and any statement about employment status
the sender did not supply. Do not include the sender's phone, email, or
private links unless the sender asked.
- When several messages concern one subject, order them with
references/sequencing.md (ally, then target, then mutuals who might tell
the target), make every cross-reference true on arrival, and read each
draft as if it will be forwarded to every other recipient.
- Return the draft, a one-line rationale, and the gate report. If the
inbound message looks like a scam, phishing, or mass-mail pitch, say so and offer a
verification reply instead of an engaged one.
- Do not send. Show the final text for approval. Sending is a separate host
action that needs explicit approval for that message.
Output contract
Return Draft, Why this shape in one line, and Gate report naming the
role tier, temperature, sourced recipient facts, conflict-check result, and
attachments. For related messages, add Send order with the condition each
step waits on. When the sender intent is unclear in a way that changes the message, ask at most one
question. Otherwise assume, label the assumption, and draft.
Validation
Before return, verify the length fits the tier, there is one ask or none, no
unsupplied fact appears, the voice gates ran, no sensitive contact data leaked,
and no sending action is included.
Platform boundary
LinkedIn can restrict messaging volume, limit messages to connections, and
flag automated or repetitive messaging. A draft does not establish that the
message can be sent or that the recipient allows it.
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-message3description: >4 Draft a LinkedIn direct message or a counter reply to an inbound message from5 raw dictation, notes, or the received text. Use when the user wants to write6 a DM, reconnect after a long gap, answer a new connection's message, follow7 up after an accepted invite, reply to a recruiter or peer, or coordinate8 several related messages about one subject. It tiers the recipient by role9 and relationship temperature, verifies recipient facts, matches length,10 keeps one small ask, scrubs risk, and returns drafts only. Do not use for11 comments, posts, connection notes, or sending.12license: MIT13metadata:14 source: https://skillmd.com/skills/okhp3/okhp3-linkedin-message15 public_artifact: true16 author: Public Agent Skill Library17 version: "1.1.0"18 category: social-posting19 origin: portable-agent-skills20 in_scope: "Drafting LinkedIn direct messages or counter replies from supplied sender intent and recipient context, including related messages with a send order, with a risk scrub."21 out_of_scope: "Sending, comment or post drafting, connection notes, bulk messaging, or inventing facts about either party."22---2324# okhp3-linkedin-message2526Portable, identity-agnostic Agent Skill.2728## Public-package data boundary2930This package and its fixtures contain no execution account, person, project,31campaign, topic, bias, opinion, or private URL. Use placeholders in public32examples and obtain all such context from the current run only.3334A good message is short enough to answer on a phone and specific enough to be35worth answering.3637## Scope3839This package drafts a direct message or counter reply, or a small set of40related messages about one subject with a send order. It does not send,41batch, or schedule messages. For first-touch invite text use42`okhp3-linkedin-connection-note`. For public conversation use43`okhp3-linkedin-comment`.4445## Process46471. Gather inputs: the sender's raw intent in their own words, the inbound48 message when replying, whatever the sender supplied about the recipient, and49 any standing constraints the sender wants honored. A dictated thought is50 source material, not a finished draft. Do not invent history between the51 parties.522. Tier the recipient using supplied evidence only: peer, senior or high-reach53 contact, recruiter or sales sender, or unknown. The tier sets tone and54 length. Senior contacts get shorter and more specific. Recruiter and sales55 senders get a verification-minded reply, not instant enthusiasm. Unknown56 senders get no personal data.57 Then set relationship temperature with `references/relationship-tiers.md`:58 `active`, `dormant`, `distant`, or `cold`. Temperature sets candor,59 attachments, and how the gap or lack of history is acknowledged. Do not60 infer warmth the sender did not state.613. Verify recipient facts before using them. A statement about the62 recipient's current role, employer, or recent change needs a source from63 this run, preferably the recipient's own current profile. Flag a press64 release or third-party page as `needs-confirmation`; it may be stale.65 Describe a role change neutrally.664. Run the recipient-conflict check. If the recipient works for a party the67 message or an attachment treats as a competitor, counterparty, or target,68 remove that material or return `needs-decision`. Attachments follow69 temperature: `active` may carry working files; `dormant` and `cold` carry70 none in the first message; `distant` carries at most one that previews71 inline when the host supports it.725. Match length to the inbound. A two-line message gets a two- or three-line73 reply. A long thoughtful message earns a proportionate answer. Cap first-74 touch messages at a few short sentences.756. State the single purpose in one sentence before drafting. Include at most76 one small, easy-to-grant ask, such as a viewpoint, a resource pointer, or a77 short call later. Do not stack asks. Do not pitch in a first message.787. Draft in the sender's voice by applying `okhp3-linkedin-voice`, which79 covers contractions, no em dashes, and preserved uncertainty. Keep the80 sender's real phrasing where it works. Do not sand it into corporate paste.818. Run `references/message-gate.md`. Scrub employer-identifying, confidential,82 or agreement-restricted content and any statement about employment status83 the sender did not supply. Do not include the sender's phone, email, or84 private links unless the sender asked.859. When several messages concern one subject, order them with86 `references/sequencing.md` (ally, then target, then mutuals who might tell87 the target), make every cross-reference true on arrival, and read each88 draft as if it will be forwarded to every other recipient.8910. Return the draft, a one-line rationale, and the gate report. If the90 inbound message looks like a scam, phishing, or mass-mail pitch, say so and offer a91 verification reply instead of an engaged one.9211. Do not send. Show the final text for approval. Sending is a separate host93 action that needs explicit approval for that message.9495## Output contract9697Return `Draft`, `Why this shape` in one line, and `Gate report` naming the98role tier, temperature, sourced recipient facts, conflict-check result, and99attachments. For related messages, add `Send order` with the condition each100step waits on. When the sender intent is unclear in a way that changes the message, ask at most one101question. Otherwise assume, label the assumption, and draft.102103## Validation104105Before return, verify the length fits the tier, there is one ask or none, no106unsupplied fact appears, the voice gates ran, no sensitive contact data leaked,107and no sending action is included.108109## Platform boundary110111LinkedIn can restrict messaging volume, limit messages to connections, and112flag automated or repetitive messaging. A draft does not establish that the113message can be sent or that the recipient allows it.114115## Public-neutrality gate116117Keep this package portable for public distribution. Do not embed a person name,118account handle or URL, private identifier, employer or organization identity,119product or project name, campaign name, or user-specific subject in instructions,120examples, references, or evaluation fixtures. Resolve account, destination,121audience, subject, links, current facts, and visibility from execution-time122context. Use placeholders or supplied evidence; platform help links may remain.123124## About125126This package is distributed as a portable, identity-agnostic Agent Skill.127It resolves account, destination, audience, subject, and source context at execution time.128MIT License -- free to use, fork, and adapt. A nod to the source is appreciated.