agentleFS
aditya-jaiswaladitya-jaiswal/compound-os/.claude/skills/linkedin-voice/SKILL.md

linkedin-voice

Skill3 starsChanged 57 days agoMITView on GitHub

Write LinkedIn posts in the current user's voice. Use when drafting personal-brand content.

3 other projects use 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. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No buzzword soup, no humblebrag, no fabricated metrics.

    line 13
  2. Very specific:

    After each post, log what hook/angle was tested in personal-brand/hypotheses.md so we learn what lands.

    line 16
  3. Distinctive:

    No em dashes (-) ever: Use commas, periods, or parentheses.

    line 18

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “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 Voice

Whose voice: the current user's. Resolve their name and role from me.local.md; frame posts from their actual role and work, never another teammate's. Their personal guide at personal-brand/voice/guide.md (private, per user) overrides the defaults below.

Until a personal guide is filled in, default to:

  • First-person, specific, grounded in the user's real work - show, don't claim.
  • Lead with a concrete moment or result; teach one idea; end with a light invitation to engage.
  • No buzzword soup, no humblebrag, no fabricated metrics.
  • Confidentiality first: no private customer names or people/ content.

After each post, log what hook/angle was tested in personal-brand/hypotheses.md so we learn what lands.

  • No em dashes (-) ever. Use commas, periods, or parentheses; "to" for ranges. This is a hard rule.

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.