weekly-report
Skill0 starsChanged 28 days agoMITView on GitHub
Write a short weekly or monthly social media report from PostEverywhere data, ready to paste into an email. Use when the user asks for a weekly report, a monthly recap, a client report, a summary to send their boss or team, or "how did this week go" in a form they can share.
49 other projects use a version of this.
Adopted by
Most recently taken up by
- Adonis0123/adonis-skillstheir own version, first seen Nov 7, 2026
- CatCatUncle/openworkbuddytheir own version, first seen Nov 5, 2026
- kudeerliu48-web/CloseCodetheir own version, first seen Nov 1, 2026
- Srltas/claude-skillstheir own version, first seen Oct 31, 2026
- Gahotx/skillstheir own version, first seen Oct 29, 2026
- 14790897/my-skillstheir own version, first seen Oct 28, 2026
Other versions49 projects use a version of this.
Word for word · 2
- posteverywhere/claude-plugin★ 1100% same
- posteverywhere/cursor-plugin★ 0100% same
Edited · 0
None found.
Wrote their own version · 47
- genspark-ai/genoffice★ 12ksame name
- anthropics/cwc-workshops★ 2.3ksame name
- yunshu0909/yunshu_skillshub★ 760same name
- Azure/azure-dev★ 573same name
- claude-office-skills/skills★ 433same name
- CatCatUncle/openworkbuddy★ 398same name
- logly/mureo★ 64same name
- Itsokay-co/bio-vibing★ 17same name
- kudeerliu48-web/CloseCode★ 14same name
- calven-ai/marketing-as-code★ 10same name
37 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- agency-clientsSkill
- approval-workflowSkill
- brand-voiceSkill
- connect-social-accountsSkill
- cross-post-videoSkill
- fix-failed-postsSkill
- launch-announcementSkill
- plan-content-calendarSkill
- recycle-top-postsSkill
- repurpose-contentSkill
- review-post-performanceSkill
- schedule-social-postsSkill
- write-blog-postSkill
- write-x-thread-or-articleSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 3 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 23 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Pick the period: Default to the last 7 days for a weekly report and the last calendar month for a monthly one.
- Very specific: line 13
Get the totals: Call get_analytics_summary with period: "week" or "month", or period: "custom" with from and to.
- Very specific: line 14
Get the posts: Call list_posts_advanced with status: "published", published_after and published_before, sort: "published_at".
- Very specific: line 15
Check for problems: Call list_posts_advanced with status: "failed,partially_failed", and scheduled_after and scheduled_before for the same …
- Very specific: line 16
See what's next: Call list_posts_advanced with status: "scheduled" and scheduled_after set to now, to list what goes out next period.
- Very specific: line 17
Write the report: Use references/email-template.md.
- Distinctive: line 18
Offer changes: Ask if they want it shorter, in a different tone, or with a section removed.
- Distinctive: line 24
Don't compare with other companies or invent benchmarks.
“Common” is measured: kept by at least 6 in 10 of the 23 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Weekly report
A short report the user can paste into an email without editing. Numbers come only from PostEverywhere.
Steps
- Pick the period. Default to the last 7 days for a weekly report and the last calendar month for a monthly one. Ask who will read it: the user, their team, or a client.
- Get the totals. Call
get_analytics_summarywithperiod: "week"or"month", orperiod: "custom"withfromandto. It gives posts published and failed, engagement totals, a per-platform breakdown and follower change per account. - Get the posts. Call
list_posts_advancedwithstatus: "published",published_afterandpublished_before,sort: "published_at". Pick the top three posts by engagement. Useget_post_resultsfor their links. - Check for problems. Call
list_posts_advancedwithstatus: "failed,partially_failed", andscheduled_afterandscheduled_beforefor the same period. Note what failed and whether it is fixed (seefix-failed-posts). - See what's next. Call
list_posts_advancedwithstatus: "scheduled"andscheduled_afterset to now, to list what goes out next period. - Write the report. Use
references/email-template.md. Keep it to one screen. - Offer changes. Ask if they want it shorter, in a different tone, or with a section removed.
Be accurate
- Say "not available" when a platform doesn't report a number. Never show a missing number as zero.
- Follower change needs two readings. If
change_in_periodis null, say the change isn't available yet. - Don't compare with other companies or invent benchmarks. Compare only with the user's own earlier period, and only if you fetched it.
- For a client report, leave out internal notes, failures that were fixed, and anything the user says to keep private. Ask before including failures.
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.