linkedin-analytics-review
Skill0 starsChanged 39 days agoMITView on GitHub
Read pasted LinkedIn analytics and say what to repeat. Use when the user pastes impressions, comments, or a screenshot transcription. Not for scraping.
In this repository44 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- docs/llms.txtllms.txt
- llms.txtllms.txt
- linkedin-marketingSkill
- agent-instagram-deskSkill
- agent-whatsapp-deskSkill
- agent-x-deskSkill
- agent-youtube-deskSkill
- linkedin-approval-gateSkill
- linkedin-carousel-writerSkill
- linkedin-case-receiptSkill
- linkedin-comment-drafterSkill
- linkedin-connection-noteSkill
- linkedin-content-plannerSkill
- linkedin-correctionSkill
- linkedin-cta-labSkill
- linkedin-employee-advocacySkill
- linkedin-engager-analyticsSkill
- linkedin-event-noteSkill
- linkedin-experience-bulletSkill
- linkedin-feature-pickerSkill
- linkedin-first-commentSkill
- linkedin-headline-labSkill
- linkedin-hook-extractorSkill
- linkedin-hook-labSkill
- linkedin-humanizerSkill
- linkedin-interviewerSkill
- linkedin-ist-windowSkill
- linkedin-job-answersSkill
- linkedin-job-fitSkill
- linkedin-job-intakeSkill
- linkedin-job-logSkill
- linkedin-job-noteSkill
- linkedin-newsletterSkill
- linkedin-poll-writerSkill
- linkedin-post-writerSkill
- linkedin-profile-optimizerSkill
- linkedin-quote-commentSkill
- linkedin-reply-handlerSkill
- linkedin-repurposerSkill
- linkedin-series-builderSkill
- linkedin-silence-auditSkill
- linkedin-thread-monitorSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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
- Distinctive: line 19
Do not publish anything from this skill.
- Distinctive: line 24
Do not invent a baseline the paste does not contain.
- Distinctive: line 25
Do not tell the user to buy reach.
≈ “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.
Files
Analytics review
Interpret numbers the user already has. Do not fetch private analytics.
When to use
- "Here are last month's posts, what worked"
- "Impressions dropped, read this export"
Steps
- Accept pasted rows or a transcription. If the paste is empty, ask for it.
- Rank posts by comments, then saves, then impressions. Say which signal you used.
- Name the pattern: hook type, length, day, proof vs opinion.
- Recommend three next drafts. Point each at
linkedin-post-writerorlinkedin-case-receipt. - Do not publish anything from this skill.
Hard rules
Global voice rules: see root SKILL.md Voice rules.
- Do not invent a baseline the paste does not contain.
- Do not tell the user to buy reach.
Related
linkedin-post-writerlinkedin-humanizerlinkedin-approval-gate../../references/voice-rules.md../../references/operator-codesbyfebin.md
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
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.