okhp3-linkedin-comment

okhp3-linkedin-comment

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.

Draft a contribution, not a miniature broadcast.

Scope

This package drafts one LinkedIn comment or reply from supplied conversation context. It does not publish, automate engagement, or replace the standalone post workflow.

Process

1. Read the target post and any parent comment that matters. Record the canonical target URL or stable post identifier when available. Identify the acting account, intended relationship to the author, and the exact point the comment should add, answer, question, or gently correct. Do not draft from a headline or a partial screenshot alone.
2. State the contribution in one sentence before writing. Avoid empty praise, attention capture, recycled talking points, or an implied endorsement the evidence does not support. A comment adds one contribution; if the request needs a multi-link campaign, route it to okhp3-linkedin-post.
3. For repository or public progress claims, verify the public source, exact ref, bounded observation window, timezone, and retrieval time. Keep a pending contest, award, or launch outcome pending. Do not claim a full test suite or deployment unless that result was actually observed.
4. Write a direct, professional response that keeps the target conversation in view. Use a mention only when the user supplied the correct account and the mention is necessary to the response. Keep one primary link; preserve user-supplied secondary links only when their roles are explicit and useful.
5. Apply okhp3-linkedin-voice as the final prose pass, then run the local public-context gate in references/public-context-gate.md. Generalize or block any employer-identifying, private, stale, or unsupported claim.