LinkedIn — Organic Presence Orchestrator
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).
Step 1 — Gate, before anything is drafted
python3 scripts/linkedin_policy_gate.py --text "<the user's own words>" --output human
- 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.
Step 2 — Route
python3 scripts/linkedin_goal_router.py --text "<the goal>" --output human
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 than guessing.
| Lane |
Typical ask |
linkedin-profile |
"fix my headline", "my profile gets views but nothing happens" |
linkedin-strategy |
"what should I post about", "how often", "should I start a newsletter" |
linkedin-content |
"write this post", "turn my talk into posts", "is this hook any good" |
linkedin-engagement |
"who should I comment on", "write a connection note" |
linkedin-analytics |
"why did reach drop", "what's working", "should I test this" |
Step 3 — Forcing questions
One at a time, each with a recommended answer. Stop as soon as the lane can run honestly.
/cs-grill-linkedin walks all five with the recommendation and the canon behind each.
- What has to be true in 90 days for this to have been worth it? (Not a follower count.)
- Who is this for, specifically enough that someone is excluded?
- How many minutes a week will you protect — measured from a bad week?
- What proof already exists? (If none, the first pillar is process, not results.)
- What will you not post about?
Hard rules
- Nothing is automated and nothing is sent. No credentials, no API, no scraping.
- Refuse, then substitute. Every REFUSE names the compliant alternative.
- The account holder is the author of record. They read every line before it ships.
- No claim they cannot substantiate. A real number, a bounded range, or nothing.
- Never silently chain lanes. Offer the next one as a question.
- Cite the confidence level. LinkedIn-official is 🟢, third-party studies are 🟡,
folklore is 🔴 and gets named as folklore.
Scripts
| Script |
Role |
scripts/linkedin_policy_gate.py |
ALLOW / CONSTRAIN / REFUSE against User Agreement §8.2 + Community Policies. 7 refusal rules, each with a substitute. |
scripts/linkedin_goal_router.py |
Deterministic five-lane classifier: route (0) / ask (2) / no-signal (3), with cross-lane prerequisites. |
References and assets
references/linkedin_platform_canon.md — how the feed ranks, evidence-graded (7 sources)
references/policy_and_account_safety.md — §8.2, prohibited software, restriction triggers (7 sources)
assets/linkedin_operating_agreement.md — the standing rules in one page, agreed before work starts
Distinct from
marketing-skill/x-twitter-growth — X/Twitter mechanics. Different platform and rules.
marketing-skill/social-content / social-media-manager — multi-platform brand
calendars. This is one person's presence on one platform, in depth.
marketing-skill/social-media-analyzer — cross-platform campaign reporting.
Version: 1.0.0 · 5 lanes · 17 stdlib scripts · nothing auto-sent
1---2name: linkedin-skills3description: "Use for any organic LinkedIn growth request (strategy, profile, posts, cadence, outreach, analytics). Checks it against LinkedIn's rules with linkedin_policy_gate.py and routes with linkedin_goal_router.py. No automation or scraping."4context: fork5license: MIT6metadata:7 source: https://skillmd.com/skills/alirezarezvani/linkedin-skills8 version: 1.0.09 author: Alireza Rezvani10 category: marketing11 updated: 2026-08-2512 build_pattern: "Domain orchestrator — deterministic lane router + policy gate, five managed sub-skills"13 distinct_from: "marketing-skill/x-twitter-growth (X/Twitter-specific); marketing-skill/social-content (multi-platform calendars); marketing-skill/social-media-analyzer (cross-platform reporting); productivity/andreessen (venture judgement, not audience building)"14---1516# LinkedIn — Organic Presence Orchestrator1718> **Portability + safety:** 17 stdlib-only Python scripts. **No LinkedIn credentials, no API19> calls, no scraping, nothing auto-sent.** Every output is text the account holder posts20> themselves — automated posting, connecting, and commenting are prohibited by LinkedIn's21> User Agreement §8.2, and a restricted account ends the whole project.2223Building an authentic presence over months, not generating a post. The five lanes cover what24actually moves: who you are (profile), what you stand for (strategy), what you publish25(content), who you talk to (engagement), and what any of it did (analytics).2627## Step 1 — Gate, before anything is drafted2829```bash30python3 scripts/linkedin_policy_gate.py --text "<the user's own words>" --output human31```3233- **exit 4 REFUSE** — a named rule is broken (automation, scraping, pods, bulk DMs, fake34 identity, fabricated proof, a prohibited automation platform). Do not draft it: name the35 rule, offer the substitute the gate prints, and route there instead. A REFUSE outranks any36 route below.37- **exit 3 CONSTRAIN** — proceed, and state the constraint out loud in your reply.38- **exit 0 ALLOW** — proceed.3940## Step 2 — Route4142```bash43python3 scripts/linkedin_goal_router.py --text "<the goal>" --output human44```4546Exit 0 routes — invoke that lane, surfacing any `prerequisite` as a question first.47Exit 2 is ambiguous — ask **one** question naming both candidates, with a recommendation.48Exit 3 has no signal — ask what they want to walk away with, rather than guessing.4950| Lane | Typical ask |51|---|---|52| `linkedin-profile` | "fix my headline", "my profile gets views but nothing happens" |53| `linkedin-strategy` | "what should I post about", "how often", "should I start a newsletter" |54| `linkedin-content` | "write this post", "turn my talk into posts", "is this hook any good" |55| `linkedin-engagement` | "who should I comment on", "write a connection note" |56| `linkedin-analytics` | "why did reach drop", "what's working", "should I test this" |5758## Step 3 — Forcing questions5960One at a time, each with a recommended answer. Stop as soon as the lane can run honestly.61`/cs-grill-linkedin` walks all five with the recommendation and the canon behind each.62631. What has to be true in 90 days for this to have been worth it? *(Not a follower count.)*642. Who is this for, specifically enough that someone is excluded?653. How many minutes a week will you protect — measured from a bad week?664. What proof already exists? *(If none, the first pillar is process, not results.)*675. What will you not post about?6869## Hard rules7071- **Nothing is automated and nothing is sent.** No credentials, no API, no scraping.72- **Refuse, then substitute.** Every REFUSE names the compliant alternative.73- **The account holder is the author of record.** They read every line before it ships.74- **No claim they cannot substantiate.** A real number, a bounded range, or nothing.75- **Never silently chain lanes.** Offer the next one as a question.76- **Cite the confidence level.** LinkedIn-official is 🟢, third-party studies are 🟡,77 folklore is 🔴 and gets named as folklore.7879## Scripts8081| Script | Role |82|---|---|83| [`scripts/linkedin_policy_gate.py`](scripts/linkedin_policy_gate.py) | ALLOW / CONSTRAIN / REFUSE against User Agreement §8.2 + Community Policies. 7 refusal rules, each with a substitute. |84| [`scripts/linkedin_goal_router.py`](scripts/linkedin_goal_router.py) | Deterministic five-lane classifier: route (0) / ask (2) / no-signal (3), with cross-lane prerequisites. |8586## References and assets8788- [`references/linkedin_platform_canon.md`](references/linkedin_platform_canon.md) — how the feed ranks, evidence-graded (7 sources)89- [`references/policy_and_account_safety.md`](references/policy_and_account_safety.md) — §8.2, prohibited software, restriction triggers (7 sources)90- [`assets/linkedin_operating_agreement.md`](assets/linkedin_operating_agreement.md) — the standing rules in one page, agreed before work starts9192## Distinct from9394- **`marketing-skill/x-twitter-growth`** — X/Twitter mechanics. Different platform and rules.95- **`marketing-skill/social-content` / `social-media-manager`** — multi-platform brand96 calendars. This is one person's presence on one platform, in depth.97- **`marketing-skill/social-media-analyzer`** — cross-platform campaign reporting.9899---100101**Version:** 1.0.0 · 5 lanes · 17 stdlib scripts · nothing auto-sent