agentleFS
styfinitystyfinity/linkedin-engine/skills/linkedin-story-miner/SKILL.md

linkedin-story-miner

Skill9 starsChanged 5 months agoMITView on GitHub

Mine a description of recent work into ranked, anonymised proof stories ready to become posts. Use when you have wins or builds but no idea what to post about.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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:

    Read the raw work and pull out every candidate that carries proof.

    line 16
  2. Distinctive:

    Keep numbers, drop names. This is for public posts, so no real person, company, or client is identifiable.

    line 26
  3. Distinctive:

    Never fabricate a result or round a number up.

    line 27
  4. Distinctive:

    No em-dashes. This is a seed list, not a finished draft.

    line 29

≈ “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 Story Miner

Your work is full of posts you haven't written yet. This skill pulls the proof stories out of what you just did, strips the identifying details, and ranks them by how hard they prove you can do the job.

Inputs

  • A description of recent work, wins, or builds: $ARGUMENTS
  • The brief (persona, offer, the operator's positioning as a Revenue Partner) loads automatically.

Do this

  1. Read the raw work and pull out every candidate that carries proof. A proof story has one of: a before/after number, a hard-won lesson, or a contrarian result that goes against the obvious play.
  2. Anonymise each one. Strip names, company names, and any detail that identifies a person or client. Keep the real numbers. "Took a client from X to Y" stays as a number with no name attached.
  3. Score each story on proof strength: how strongly it shows the operator can produce the outcome the ICP wants. A measured before/after outranks a vague lesson.
  4. Rank them strongest proof first.
  5. For each, name the angle (the single point it makes) and suggest the hook formula that fits: the contrarian take, the before/after, the mistake-I-made, the counterintuitive number, or the behind-the-build.

Output

A ranked list of story seeds. For each: the anonymised proof (one or two lines, numbers intact), the angle, and the suggested hook formula. Top seed first. End with a one-line note on which seed to turn into a post next, and a pointer to draft it.

Rules

  • Keep numbers, drop names. This is for public posts, so no real person, company, or client is identifiable.
  • Never fabricate a result or round a number up. If a story has no real proof, mark it as a softer "lesson" seed, do not invent a metric.
  • Attribute every number to "a post", "a client", or "an operator", never a named entity.
  • No em-dashes. This is a seed list, not a finished draft. Hand the chosen seed to a drafting skill, then run /linkedin-humanizer before it goes live.

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.