AGENT SKILL

linkedin-strategy

Use when someone needs a LinkedIn plan rather than a post — content pillars, positioning for a career change or consulting or thought leadership, a sustainable posting cadence, or a newsletter decision. Triggers on "what should I post about", "how often should I post", "LinkedIn content strategy", "should I start a LinkedIn newsletter", "grow my following", "90-day plan". Validates the positioning brief, sizes the week against real hours and refuses a plan that will not survive week five, and gates a newsletter against eligibility and a six-month cadence commitment.

License 许可
MIT
最近更新
2026-10-15
Stars
★ 0
Forks
0

01 前言 Front Matter

name
linkedin-strategy
license
MIT
metadata
{ "author": "Alireza Rezvani", "updated": 1787616000000, "version": "1.0.0", "category": "marketing" }
description
Use when someone needs a LinkedIn plan rather than a post — content pillars, positioning for a career change or consulting or thought leadership, a sustainable posting cadence, or a newsletter decision. Triggers on "what should I post about", "how often should I post", "LinkedIn content strategy", "should I start a LinkedIn newsletter", "grow my following", "90-day plan". Validates the positioning brief, sizes the week against real hours and refuses a plan that will not survive week five, and gates a newsletter against eligibility and a six-month cadence commitment.

02 资源文件 8

03 SKILL.md 正文

LinkedIn Strategy — brief, cadence, newsletter

Three decisions, in this order. Out of order is why most LinkedIn efforts produce a feed of unrelated observations and stop in week five.

Workflow

1. The brief — an editorial constitution, not a wish. Walk the five questions one at a time, each with a recommended answer, then validate:

python3 scripts/positioning_brief.py --input brief.json --output human

It refuses on the two things that make everything downstream impossible: an objective that is not one of the six real ones (career-change, consulting, thought-leadership, hiring, fundraising, community), and an audience too broad to exclude anyone. It also refuses fewer than two exclusions — a positioning that excludes nothing is availability.

Pillars: two to four, shares summing to 100, at least one backed by proof that already exists, at least one at 10-20% as the experimental slot. Every pillar needs a "why you"; if anyone could post it, cut it.

The script emits observable 90-day criteria. Follower count is deliberately absent — it moves for reasons unrelated to whether the objective is being met.

2. The cadence — priced against a bad week.

python3 scripts/cadence_planner.py --minutes 240 --stage starting --target-posts 3 --output human

Exit 0 fits / 2 below the 90-minute floor / 3 over budget with the overage named. Every activity is priced in minutes including the reply window, which is part of the post and not an extra. Allocation shifts with stage: from a standing start 60% of the budget belongs in other people's comment sections, because a post published to nobody reaches nobody.

Below 90 minutes a week it refuses to plan a posting schedule and returns a comment-only week: a cadence abandoned in week five is worse than one never started, because the abandonment is visible on the profile. Every plan ships with a minimum viable week.

3. The newsletter — only if the promise can be paid.

python3 scripts/newsletter_planner.py --followers 1800 --cadence biweekly \
  --minutes-per-month 420 --pillar "..." --output human

Refuses below LinkedIn's published 150-follower evaluation floor, and refuses a cadence whose six-month cost exceeds the budget. Emits a 12-issue arc rotating issue types across pillars, and a stop rule written before issue one.

Rules

  • One objective. Two objectives serve neither; the audiences overlap less than they look.
  • The exclusion list is the positioning. Refuse to skip it.
  • Price the week from a bad week, not a good one.
  • Consistency over volume. A skipped week is fine; a skipped month resets you.
  • Review the brief quarterly, not weekly. A brief revised monthly is a mood.

Scripts

Script Role
scripts/positioning_brief.py Validates objective, audience, 2-4 proof-backed pillars, and the exclusion list; emits observable 90-day criteria.
scripts/cadence_planner.py Prices the week in minutes, allocates by stage, refuses over-budget targets, emits the minimum viable week.
scripts/newsletter_planner.py Eligibility + six-month sustainability gate, 12-issue arc across pillars, stop rule.

References and assets

Distinct from

  • linkedin-content — drafts and lints individual posts. This decides what they are about and how many there are. Posts without pillars are noise; offer this first, never chain silently.
  • linkedin-analytics — tells you what happened. This decides what to do next.
  • marketing-skill/content-strategy — company-level content marketing. This is one person's own presence.

Version: 1.0.0

04 同仓库更多 Skills

ibada0410
ibada0410/CLAUDE-SKILLS

internal-comms

A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).

★ 0
ibada0410
ibada0410/CLAUDE-SKILLS

eu-ai-act-reviewer

Review user journeys, public content, and codebases for potentially relevant EU AI Act provisions, with exact official citations, evidence gaps, application dates, and plain-language next actions. Use for EU AI Act issue-spotting, not final legal or compliance decisions.

★ 0
ibada0410
ibada0410/CLAUDE-SKILLS

discernment-nudge

After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.

★ 0
ibada0410
ibada0410/CLAUDE-SKILLS

academy-guide

Stop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.

★ 0
ibada0410
ibada0410/CLAUDE-SKILLS

webapp-testing

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

★ 0
ibada0410
ibada0410/CLAUDE-SKILLS

web-artifacts-builder

Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.

★ 0