charlie947/social-media-skills is a collection of markdown instructions that gives AI agents specialized workflows for creating and managing social-media content. It supports a content system spanning LinkedIn, Instagram, Substack, X, and YouTube, with shared voice and context files guiding the individual skills.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add charlie947/social-media-skills --skill post-scorergit clone --depth 1 https://github.com/charlie947/social-media-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/charlie947/social-media-skills/post-scorer)<a href="https://agentmods.dev/skills/charlie947/social-media-skills/post-scorer"><img src="https://agentmods.dev/badge/skills/charlie947/social-media-skills/post-scorer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/charlie947/social-media-skills/post-scorer"><img src="https://agentmods.dev/badge/skills/charlie947/social-media-skills/post-scorer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
- Snyk warn
- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00111 | $0.01833 |
| Opus 5 | $0.00056 | $0.00916 |
| Sonnet 5 | $0.00022 | $0.00367 |
| Haiku 4.5 | $0.00011 | $0.00183 |
Grade A, and why
post-scorer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 13d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
1 near-identical copy found in the catalogue:
- post-scorer — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Post Scorer
CRITICAL: Auto-start on load
When this skill triggers, go straight to Step 1. Do not summarise. Do not explain the scoring method. Start immediately.
Step 1. Get the post
If the user already pasted a post in the same message, use it. Otherwise say:
Paste the LinkedIn post you want scored.
Wait for the post.
Step 2. Load scoring data
The scorer needs two things: the user's voice system and real performance data.
Voice system
Read about-me.md and voice.md from the project if they exist. If missing, note it and score without voice matching.
Performance data
Check for cached LinkedIn data in the project or outputs folder. Look for files matching *-all-posts.json or *-posts.txt.
If cached data exists, use it. If not, ask the user:
[
{
"question": "To score your post against real data, I need your LinkedIn history. How should I get it?",
"header": "Data source",
"multiSelect": false,
"options": [
{"label": "Scrape my posts", "description": "Pull my last 100 posts from LinkedIn via Apify. Takes 1 to 2 minutes, costs about $0.50."},
{"label": "Use Charlie Hills data", "description": "Score against Charlie Hills benchmarks (1,872 avg engagement, 500 posts analysed). Good fallback."},
{"label": "Skip data scoring", "description": "Score against generic best practices only. Less accurate but instant."}
]
}
]
If "Scrape my posts":
- Ask for their LinkedIn username
- Call Apify actor apimaestro/linkedin-profile-posts with input: { "username": "[their-username]", "total_posts": 100 }
- Download results (do NOT use the fields parameter, it strips engagement data)
- Save as [username]-all-posts.json in the project
- Proceed to analysis
If "Use Charlie Hills data": Look for cached Charlie data at **/linkedin-data/charlie-all-posts.json. If found, use it. If not, note you are using the benchmarks from this skill file (listed below).
If "Skip data scoring": Fall back to voice-system-only scoring and general best practices.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 13d ago First seen · 191 lines · 111 tokens per session scan A af5bb39f8a66
post-scorer is a skill published in the GitHub repository charlie947/social-media-skills (3,385 stars, last pushed 13d ago), licensed MIT. It adds 111 tokens to every session and 1,833 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…