okhp3-linkedin-connection-note

Topics in the source

• okhp3-linkedin-connection-note
• Public-package data boundary
• Scope
• Process
• Output contract
• Validation
• Platform boundary
• Current platform reference

Portable, identity-agnostic Agent Skill. 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. 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. 1. 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. 2. 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

This is an excerpt. Refer to the complete source and its current requirements.