linkedin-skills

$npx mdskill add alirezarezvani/claude-skills/linkedin-skills

> **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.

SKILL.md

.github/skills/linkedin-skillsView on GitHub ↗
---
name: linkedin-skills
description: Use when someone wants to grow an organic LinkedIn presence — a content strategy for a career change or consulting or thought leadership, a rewritten profile or headline, post drafts and hooks, a posting cadence or newsletter plan, connection notes and outreach, a commenting strategy, repurposing an article or talk into posts, or a read on why their reach dropped. Triggers on "grow my LinkedIn", "fix my headline", "write a LinkedIn post", "what should I post about", "LinkedIn strategy", "connection request", "my reach dropped". Forks context to route to one of five sub-skills, and refuses automation, scraping, pods, and bulk DMs before any drafting starts.
context: fork
license: MIT
metadata:
  version: 1.0.0
  author: Alireza Rezvani
  category: marketing
  updated: 2026-08-25
  build_pattern: "Domain orchestrator — deterministic lane router + policy gate, five managed sub-skills"
  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)"
---

# 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

```bash
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

```bash
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.

1. What has to be true in 90 days for this to have been worth it? *(Not a follower count.)*
2. Who is this for, specifically enough that someone is excluded?
3. How many minutes a week will you protect — measured from a bad week?
4. What proof already exists? *(If none, the first pillar is process, not results.)*
5. 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`](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`](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`](references/linkedin_platform_canon.md) — how the feed ranks, evidence-graded (7 sources)
- [`references/policy_and_account_safety.md`](references/policy_and_account_safety.md) — §8.2, prohibited software, restriction triggers (7 sources)
- [`assets/linkedin_operating_agreement.md`](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

More from alirezarezvani/claude-skills

SkillDescription
a11y-auditAccessibility audit skill for scanning, fixing, and verifying WCAG 2.2 Level A and AA compliance across React, Next.js, Vue, Angular, Svelte, and plain HTML codebases. Use when auditing accessibility, fixing a11y violations, checking color contrast, generating compliance reports, or integrating accessibility checks into CI/CD pipelines.
ab-test-setupWhen the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "conversion experiment," "statistical significance," or "test this." For tracking implementation, see analytics-tracking.
ad-creativeWhen the user needs to generate, iterate, or scale ad creative for paid advertising. Use when they say 'write ad copy,' 'generate headlines,' 'create ad variations,' 'bulk creative,' 'iterate on ads,' 'ad copy validation,' 'RSA headlines,' 'Meta ad copy,' 'LinkedIn ad,' or 'creative testing.' This is pure creative production — distinct from paid-ads (campaign strategy). Use ad-creative when you need the copy, not the campaign plan.
adversarial-reviewerAdversarial code review that breaks the self-review monoculture. Use when you want a genuinely critical review of recent changes, before merging a PR, or when you suspect Claude is being too agreeable about code quality. Forces perspective shifts through hostile reviewer personas that catch blind spots the author's mental model shares with the reviewer.
aeoAnswer Engine Optimization (AEO) skill — optimize content to be cited by AI language models (ChatGPT, Perplexity, Claude, Gemini, Mistral) as authoritative sources. Distinct from SEO — AEO optimizes for citation in LLM-generated responses, not search rankings. Use when planning content for AI-first search audiences, auditing existing content for E-E-A-T signals, tracking which pages get cited by which LLMs, or building a citation-friendly content strategy. Triggers — 'AEO audit', 'optimize for ChatGPT', 'get cited by Perplexity', 'LLM citation strategy', 'answer engine optimization', 'content for AI search', 'E-E-A-T audit'. Output is a markdown audit report (default) or JSON for pipeline integration. Stdlib-only Python tools.
agent-decision-receiptsMint a tamper-evident, post-quantum-signed receipt for a consequential agent action (deploy, delete, pay, grant-access, model decision) so it can be verified later from the certificate alone. Use when an autonomous agent takes a side-effecting action that may need to be proven later, or when satisfying EU AI Act Article 12 record-keeping. Three decisions: whether an action needs a receipt, minting it, verifying it. Signing is delegated to the open-source OpenAgentOntology package. Not after-the-fact log analysis; not a hosted notary; not a legal opinion.
agent-designerUse when the user asks to design a multi-agent system, pick an orchestration pattern (supervisor/swarm/pipeline), generate tool schemas for agents, or evaluate agent execution logs for cost, latency, and failure bottlenecks. Examples: 'design an agent architecture for research automation', 'generate Anthropic tool schemas from these tool descriptions', 'analyze these agent run logs for bottlenecks'. NOT for Claude Code workflow files (use workflow-builder) or single-agent prompt design (use agent-workflow-designer).
agent-harnessTurn any domain folder of skills into a bounded agentic loop: compile a goal into a verifiable task plan, execute tasks with the domain's own tools, verify every task with machine-run checks, retry with caps, escalate to a human when budgets exhaust, and refuse to close until everything is verified or explicitly waived. Use when you want an agent or subagent to pick up a goal and drive it to a verified close across one of this repo's 18 domains ('run this goal through the engineering harness', 'set up an agentic loop for marketing work', 'make the finance domain self-verifying'). NOT for authoring Claude Code Workflow-tool .js scripts (workflow-builder), N-agent tournaments on one task (agenthub), single-file metric optimization (autoresearch-agent), or discovering published loop recipes (loop-library).
agent-launcher-orchestratorUse when a user wants to build, launch, grade, or schedule a Claude Managed Agent (CMA) in their own Anthropic account — "build me an agent", "launch this as a managed agent", "run this on a schedule", "grade my agent against a rubric", "set up a nightly worker". Reads the per-session goal (./my-agent/goal.json), routes deterministically to one of five phase sub-skills (interview → stage-launch → grade-iterate → run-without-you → wrap-up) via goal_router.py, and compiles the goal+phase into an execution shape (single-pass workflow / bounded grade→iterate loop / recurring cron deployment loop) via loop_compiler.py. Forks context so heavy intake (build sheets, payloads, eval cases) stays out of the parent thread. All launches are emitted as BYOK curl the user runs with their own key; no tool makes API calls. Inspired by anthropics/launch-your-agent (Apache-2.0). Distinct from engineering/agent-harness (generic domain loop) and engineering/write-a-skill (authors Claude Code skills, not CMAs).
agent-memoryUse when a project's CLAUDE.md has grown past what anyone reads and you want the agent to learn durable facts from its own sessions instead — or when asking why the agent keeps re-learning the same correction, why a remembered rule is wrong, or where a memory line came from. Implements a four-tier store (L0 transcripts / L1 candidates / L2 project context / L3 stable persona) where promotion is earned by recurrence across sessions and days, never by one confident statement, and nothing reaches a committed file without a human adopting it.