weekly-what-worked

weekly-what-worked is a skill for Claude Code from JackVitick/socialync-mcp. It costs 93 tokens per session (888 once invoked), scanned A, original, MIT.

A weekly report that reads Socialync's social-media data to compare platform growth, post performance, failed posts, and empty spaces in the next week's calendar. It can also suggest posts for the following week.

In plain words
What is it for?
Use it to see what worked last week, identify patterns in strong or weak posts, and plan the next week's social content.
Why use it?
It turns scattered platform results into one review and separates measured results from areas where Socialync has no data. The review itself only reads data; publishing suggestions still requires approval.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the socialync plugin — 6 skills, 1 MCP server shipped together

Good fit Use it to see what worked last week, identify patterns in strong or weak posts, and plan the next week's social content.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jackvitick/socialync-mcp/weekly-what-worked
Install

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.

Any agent
npx skills add JackVitick/socialync-mcp --skill weekly-what-worked
Clone the repo
git clone --depth 1 https://github.com/JackVitick/socialync-mcp

Made for: Claude Code.

Or install socialync, the plugin that ships this one along with the rest of its 6 skills, 1 MCP server.

Wrote 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.

agentmods badge for weekly-what-worked

README.md
[![agentmods](https://agentmods.dev/badge/skills/jackvitick/socialync-mcp/weekly-what-worked/github.svg)](https://agentmods.dev/skills/jackvitick/socialync-mcp/weekly-what-worked)
Your own site
<a href="https://agentmods.dev/skills/jackvitick/socialync-mcp/weekly-what-worked"><img src="https://agentmods.dev/badge/skills/jackvitick/socialync-mcp/weekly-what-worked/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.

agentmods 80×15 button for weekly-what-worked

Your own site · 80×15
<a href="https://agentmods.dev/skills/jackvitick/socialync-mcp/weekly-what-worked"><img src="https://agentmods.dev/badge/skills/jackvitick/socialync-mcp/weekly-what-worked.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 93 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 888 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00093 $0.00888
Opus 5.5 $0.00037 $0.00355
Sonnet 5.5 $0.00019 $0.00178
Haiku 4.5 $0.00009 $0.00089

Measured 3d ago against content hash ec25a01aa834, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

weekly-what-worked 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 3d 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.

skills/weekly-what-worked/SKILL.md · 57 lines

How it starts

The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Weekly review: what worked, what to post next

The review only reads data, so it needs no approval. Anything it leads to that publishes goes through the consent rule in the schedule-social-post skill.

Before you start

  • list_profiles. If the user has several profiles, ask which one, or review each separately.
  • Analytics are on paid Socialync plans. If get_analytics returns a plan error or no data, say so in one line and offer the parts that still work: failed posts and next week's calendar.
  • Socialync collects analytics for TikTok, YouTube, Instagram, Facebook, Threads and Bluesky. X and LinkedIn have no numbers here, and Bluesky reports engagement without views. Say this when those platforms matter to the user.

Pull the data

  1. get_analytics with period: "week" and breakdown: "by_platform". Use period: "month" if the user asks for a monthly view. The response compares against the previous period of the same length.
  2. get_top_posts with sort: "engagement" and limit: 10. Use each post's date to keep to the period you are reviewing.
  3. get_top_posts with sort: "recent" and limit: 20 to see every recent post, including the weak ones.
  4. get_post_history for anything that failed this week, with its reason.
  5. get_scheduled_posts for what is already queued for the next 7 days.

Write the review

Keep it short enough to read in a minute.

  1. The week in three lines: total views, engagement and followers with the change against last week, and the platform that moved most in each direction.
  2. Top 3 posts: platform, first line, views, engagement rate, status. Then what they share. Look at format (video, image, text), the type of hook, length, topic, day and time posted. Name the pattern only if at least two of the three show it.
  3. Bottom 3 posts with the same fields. A post with status no_data has no numbers yet. Leave it out of this list.
  4. Failures: each failed post with its plain reason and the fix. For reconnect, name the account to reconnect in Socialync Settings.
  5. Next week: days with nothing scheduled.
  6. Three to five ideas for next week, each tied to a top post: "Your Tuesday how-to clip got 4 times your usual views. Make another how-to on [topic]."

Read the full file on GitHub · 57 lines

Changes

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.

  1. 3d ago First seen · 57 lines · 93 tokens per session scan A ec25a01aa834

Subscribe to this mod's changes

weekly-what-worked is a skill published in the GitHub repository JackVitick/socialync-mcp (0 stars, last pushed 4d ago), licensed MIT. It adds 93 tokens to every session and 888 once invoked, about $0.0004 per session on Opus 5.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-10-13.