Build an Evidence-Led LinkedIn Agent

A useful LinkedIn agent should help with strategy, research, post drafting, comment preparation, and scheduled reviews. It should not publish, comment, react, message, scrape, or bypass platform controls on its own.

The operating boundary is simple: the system prepares review-ready work, while a human applies editorial judgement and separately approves each public action at the time it occurs.

The guide separates project architecture, source knowledge, positioning, post generation, comment preparation, scheduling, and human approval. Each layer produces a durable artifact that another operator can inspect and explain.

Captured evidence stays separate from maintained synthesis. Positioning is written as an audience, problem, earned proof, and boundary statement before a drafting skill is allowed to turn research into content.

A post package should include its objective, intended audience, hook, copy, claims requiring verification, image direction, alt text, hashtags, call to action, and publication checklist. This makes review more precise than approving copy in isolation.

A comment package should include the source, relationship context, fit score, contribution type, claims to verify, and a recommendation. The agent should return no draft when it has nothing credible or useful to add.

Comment opportunities can be scored on audience fit, subject fit, relationship value, credible contribution, and timeliness. Generic praise, summary-only replies, self-promotion, and unverifiable claims should fail the selection step.

Useful review looks beyond impressions. Audience fit, saves and sends, substantive comments, profile actions, and qualified outcomes provide better feedback for the next drafting cycle.

Recurring tasks can gather permitted context and prepare drafts after the skills have passed manual tests. A schedule does not grant standing permission to engage publicly, and an earlier approval should not be reused for a later action.

The living Gist contains the seven-layer model, eight-step build sequence, required outputs, safety rules, an exact configurable implementation prompt, completion check, and links to current platform guidance that should be rechecked as policies change.