跳到正文
FunCoding

搜索

搜索文档、Skill 和 MCP

li-plan

Build the week on LinkedIn - what to post, when to post it, and who to engage with. Use when the user says "plan my week", "what should I post", "content calendar", "I have nothing to post about", or wants a posting schedule and an engagement list.

AI 与智能体1.5kskills/li-plan/SKILL.md

安装

把这段话发给 Claude Code、Codex 或 Cursor。智能体会先检查安全性,你确认后才安装。

读取 https://funcoding.ai/skills/jakeschincariol/linkedin-agent-skill/li-plan/install.md ,按里面的步骤帮我安装这个 Skill。

SKILL.md

li-plan

The control room. Everything else in this pack executes; this decides what gets executed. Run it once a week, on the same day.

Input

If ~/.claude/linkedin/voice.md and log.md exist, read them - the plan should not repeat a theme from the last fortnight. If they do not exist, ask for four things and write them down:

  1. What the user sells, and to whom.
  2. The three or four themes they want to be known for.
  3. What actually happened this week - a client call, a number, a mistake, a thing they built, an argument they had. This is where posts come from.
  4. Ten to twenty people or companies worth being visible to.

What to post

Four posts a week beats seven. Consistency is a floor, not a target, and the fifth post of a week is almost always the weak one that drags the average.

Mix across the week, never two of the same type back to back:

typesharejob
Proof1 per weeksomething that happened, with a number
Opinion1 per weeka position that could lose you followers
Teach1 per weekone thing the reader can do today
Story1 per fortnighta scene with dialogue and a cost
Offer1 per fortnightwhat you sell, said plainly, no apology

For each slot give: the theme, the specific angle drawn from what actually happened this week, and the hook formula number from li-post/hooks.json that fits it. Not a topic - an angle. "AI" is not a plan. "The proposal we lost because our AI draft had an em dash in it" is a post.

When to post

Post when the user's audience is at a desk. For a B2B audience in one timezone, Tuesday to Thursday, 7:30-9:30am local, is the working default, with Monday afternoon and Friday morning as the second tier. Weekends are for personal-story posts or nothing.

But state this plainly: the day and hour matter far less than whether the first line is good. If the user is optimising posting times before their hooks work, they are polishing the wrong thing, and you should say so.

Anchor the times to their audience's timezone, not the user's, if those differ.

Who to engage with

Build a list of 10, split three ways:

  • 5 reach - people with an audience the user wants, whose posts they can genuinely add to. Comment before they have 20 comments or nobody sees it.
  • 3 peers - same level, same field. This is the group that reciprocates.
  • 2 buyers - people who could actually buy. Comment on their posts for weeks before any DM, and never pitch in a comment.

20 minutes a day, before posting, not after. Comments on other people's posts are what makes the user's own post land.

Output

WEEK OF SEP 8

MON  engage only  (20 min, list below)
TUE  8:15am  PROOF    #17 Time Anchor   - the 5hr -> 20min proposal rebuild
WED  engage only
THU  8:00am  OPINION  #1  Contrarian    - why we killed the discovery call
FRI  8:30am  TEACH    #21 Direct Value  - the 4-line reopen email, given away
SAT  -
SUN  4:00pm  STORY    #9  Cold Open     - the "going with someone cheaper" email

ENGAGE  (5 reach / 3 peers / 2 buyers)
  ...

Say "write Tuesday" and I will draft it.

Write the plan to ~/.claude/linkedin/plan.md so the other skills can read it. Nothing is scheduled or posted anywhere - this is a plan, and the user runs it.

相似的 Skill

brand-guidelines
anthropics/skills180k

brand-guidelines

Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.

AI 与智能体

internal-comms
anthropics/skills180k

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

AI 与智能体

template-skill
anthropics/skills180k

template-skill

Replace with description of the skill and when Claude should use it.

AI 与智能体

mcp-builder
anthropics/skills180k

mcp-builder

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

AI 与智能体

algorithmic-art
anthropics/skills180k

algorithmic-art

Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.

AI 与智能体

academy-guide
anthropics/skills180k

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.

AI 与智能体