agentleFS
TeqfocusAdminTeqfocusAdmin/ClaudeSkillsRepo/skills/linkedin-post-reviewer/SKILL.md

linkedin-post-reviewer

Skill0 starsChanged 52 days agoNo licenceView on GitHub

Self-review framework for LinkedIn posts that eliminates GTM director bottleneck. Use this skill whenever the user wants to review a LinkedIn post draft, check if a post is ready to publish, validate messaging alignment, or needs feedback on LinkedIn content before it goes live. Also trigger when user mentions "review this post", "is this ready", "check my LinkedIn draft", "will this pass review", "does this align with our messaging", or wants to avoid revision cycles. Runs posts through five mandatory checkpoints (tone/authority, bridge-gap positioning, industry framework alignment, competitive SI differentiation, conversion clarity) and auto-suggests specific rewrites using Teqfocus frameworks. Make sure to use this skill for ALL LinkedIn content review requests, even informal ones.

The file

Show its rules and text

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈21

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “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.

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.