DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to find which of your past posts actually worked with Linkedin Agent Skill

Rank your published posts by engagement rate and reach multiple, not raw impressions.

Who it is forA creator who has posted for months and wants to know which topics and formats are worth repeating.

The problemImpressions alone hide which posts earned real engagement, so it is easy to repeat the wrong formats.

The outcomeA ranked post-mortem of what you already published, judged by engagement rate and reach multiple.

What you need first

  • Claude access, either Claude Code for installing the skills or a chat where you can paste a SKILL.md
  • A LinkedIn account you will post from yourself, since the skills never post for you
  • Python 3 for the humanizer scripts, which need no extra dependencies
  • Three of your own past posts, or a filled-in templates/voice.md, so drafts match your voice

Steps

  1. Run git clone https://github.com/Jakeschincariol/linkedin-agent-skill.git in a terminal.
  2. Run cp -r linkedin-agent-skill/skills/li-* ~/.claude/skills/ to install the skills.
  3. Paste the text and the engagement numbers you can see for your recent posts into Claude Code.
  4. Type /li-audit and ask for the ranking.
  5. Use the top-ranked formats as input for your next /li-post run.

Prompt for your agent

Use the li-audit skill from https://github.com/Jakeschincariol/linkedin-agent-skill on the post data I paste from <source of post data>. Expect a ranking by engagement rate and reach multiple, with a short note on each. Verify that every number in the output comes from the data I supplied.

Caveat. The audit can only rank the numbers you paste in, and the README does not say where those numbers should come from.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page