agentleFS
Sign inStart free
styfinitystyfinity/linkedin-engine/skills/linkedin-booking-closer/SKILL.md

linkedin-booking-closer

Skill9 starsChanged 4 months agoMITView on GitHub

Write the shortest possible booking message once a prospect has said yes, stripping every extra sentence so nothing talks them out of it. Use the moment a thread reaches "yes / show me".

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 thread. Confirm it is a real yes, not a soft maybe.

    line 16
  2. Distinctive:

    Write one warm line plus the booking link.

    line 17
  3. Distinctive:

    After a yes, stop selling and book.

    line 25
  4. Distinctive:

    No em-dashes, no exclamation marks, no "looking forward to it".

    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 Booking Closer

Setter discipline: once they have said yes, stop selling and book the call. After a yes, every extra word is downside.

Inputs

  • The thread at the "yes / show me" moment, and the booking link: $ARGUMENTS
  • The brief (offer, the one result they want) loads automatically.

Do this

  1. Read the thread. Confirm it is a real yes, not a soft maybe. If it is a maybe, say so and stop - this is not the moment to book.
  2. Write one warm line plus the booking link. Nothing more.
  3. Tease one result, never the mechanism. The mechanism is the demo's job, so do not explain how it works here.
  4. Strip every extra sentence. No recap, no "as I mentioned", no second pitch. Once they have said yes, more words only risk talking them out of it.

Output

The one-line booking message with the link, labelled "Booking message". If the draft runs longer than one warm line plus the link, flag it: "Over-selling - this is too long, cut to one line."

Rules

  • After a yes, stop selling and book. That is the whole job.
  • One result-hook max. No mechanism dump, no feature list.
  • No em-dashes, no exclamation marks, no "looking forward to it".
  • Draft only. Nothing sends without BOTH the connected CLI/MCP layer AND explicit approval. Sending runs through that layer on the user's own LinkedIn session or provider key, and the 20 actions/day cap applies to new accounts. A calendar link is the one message you never want auto-sent.

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.

Check your setup, free