linkedin-skills

Topics in the source

• LinkedIn — Organic Presence Orchestrator
• Step 1 — Gate, before anything is drafted
• Step 2 — Route
• Step 3 — Forcing questions
• Hard rules
• Scripts
• References and assets
• Distinct from

Portability + safety: 17 stdlib-only Python scripts. No LinkedIn credentials, no API calls, no scraping, nothing auto-sent. Every output is text the account holder posts themselves — automated posting, connecting, and commenting are prohibited by LinkedIn's User Agreement §8.2, and a restricted account ends the whole project. Building an authentic presence over months, not generating a post. The five lanes cover what actually moves: who you are (profile), what you stand for (strategy), what you publish (content), who you talk to (engagement), and what any of it did (analytics). exit 4 REFUSE — a named rule is broken (automation, scraping, pods, bulk DMs, fake identity, fabricated proof, a prohibited automation platform). Do not draft it: name the rule, offer the substitute the gate prints, and route there instead. A REFUSE outranks any route below. exit 3 CONSTRAIN — proceed, and state the constraint out loud in your reply. exit 0 ALLOW — proceed. Exit 0 routes — invoke that lane, surfacing any prerequisite as a question first. Exit 2 is ambiguous — ask one question naming both candidates, with a recommendation. Exit 3 has no signal — ask what they want to walk away with, rather th

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