agentleFS
styfinitystyfinity/linkedin-engine/skills/linkedin-content-calendar/SKILL.md

linkedin-content-calendar

Skill9 starsChanged 4 months agoMITView on GitHub

Plan a week of five LinkedIn posts, one per revenue lane, with the locked variety mix and five different hook formulas. Use to set the week's content slate before drafting.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check the last six weeks. Do not repeat a framework angle that has run in that window.

    line 19
  2. Distinctive:

    Every post must prove a competence the buyer buys.

    line 26
  3. Distinctive:

    No angle and no hook formula repeated inside the week.

    line 27

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

LinkedIn Content Calendar

One week, five posts, five lanes. This skill sets the slate so every post proves a competence the buyer actually pays for, with enough variety that the feed never feels like the same post twice.

Inputs

  • The week's theme or the proof on hand, plus which lane needs weight: $ARGUMENTS
  • The brief (lanes, voice profile, offer, pains, and what has run recently) loads automatically.

Do this

  1. Assign one post to each of the five revenue lanes: Get Found, Get Chosen, Get the Meeting, Close the Deal, Operating System.
  2. Apply the locked variety mix across the five, one type each: a deep operator-playbook post, an ultra-short screenshot-and-share, a second deep post, a proof / business-case post, a punchy mid-length opinion.
  3. Pick five DIFFERENT hook formulas, one per post. No formula repeats inside the week.
  4. Check the last six weeks. Do not repeat a framework angle that has run in that window. If the theme forces a repeat, rotate the angle or swap the proof.
  5. For each post, set the comment keyword (one word, easy to type, tied to the lane's lead magnet or follow-up).

Output

A five-row table with columns: Day, Type, Lane, Hook formula, Angle (one line), Keyword. Then one line naming the through-line that ties the five posts into a single week.

Rules

  • Every post must prove a competence the buyer buys. If a post only entertains, cut it and reassign the lane.
  • No angle and no hook formula repeated inside the week; no framework angle repeated inside six weeks.
  • This skill plans only. It does not write the posts. Hand each row to the drafting skills, then run /linkedin-humanizer on the drafts before anything is scheduled.
  • No em-dashes.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.