linkedin-skills
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.
- License 许可
- MIT
- 最近更新
- 2026-11-08
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- linkedin-skills
- context
- fork
- license
- MIT
- metadata
- { "author": "Alireza Rezvani", "updated": 1787616000000, "version": "1.0.0", "category": "marketing", "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)" }
- 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.
03 SKILL.md 正文
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
04 同仓库更多 Skills
youtube-full
Use when the user needs YouTube transcripts, video search, channel browsing, playlist extraction, or content monitoring. Trigger phrases: 'get the transcript for', 'search YouTube for', 'what are the latest videos on', 'list this playlist', 'monitor this channel', or any request involving a YouTube URL, video ID, or @handle. Do NOT use for downloading video or audio files, YouTube engagement data (likes, comments), or private/age-restricted videos.
x-twitter-growth
X/Twitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X/Twitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.
write-a-skill
Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, build, or author a new skill.
wrap-up
Close out a launched Claude Managed Agent — recap every primitive the founder now owns, regenerate the single-file overview page, and suggest the next 1-2 upgrades. Use when the user says "wrap up", "close this out", "what do I own now", "give me the summary", "recap the agent", or when the orchestrator routes phase=wrap-up. primitives_inventory.py tables everything owned (agent, environment, session, memory, outcome, deployment); overview_page.py regenerates a self-contained ./my-agent/agent-overview.html; upgrade_suggester.py ranks the next moves from recorded deferrals plus standing hardening steps. Companion to run-without-you; the last stop before phase=done.
workflow-builder
Design and write deterministic multi-agent workflow scripts (.js files in .claude/workflows/) for Claude Code's Workflow tool. Use when a user wants to build, create, author, scaffold, or run a custom Claude Code workflow, orchestrate sub-agents (fan-out, pipeline, loop, judge-panel), or automate a repeatable multi-step task across fresh-context agents.
weekly-review
Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says "/cs:weekly-review". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.