Individual skill

weekly-report

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.

plugins/posteverywhere/codex-plugin/skills/weekly-report/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,530
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Weekly report

A short report the user can paste into an email without editing. Numbers come only from PostEverywhere.

## Steps

1. **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.
2. **Get the totals.** Call `get_analytics_summary` with `period: "week"` or `"month"`, or `period: "custom"` with `from` and `to`. It gives posts published and failed, engagement totals, a per-platform breakdown and follower change per account.
3. **Get the posts.** Call `list_posts_advanced` with `status: "published"`, `published_after` and `published_before`, `sort: "published_at"`. Pick the top three posts by engagement. Use `get_post_results` for their links.
4. **Check for problems.** Call `list_posts_advanced` with `status: "failed,partially_failed"`, and `scheduled_after` and `scheduled_before` for the same period. Note what failed and whether it is fixed (see `fix-failed-posts`).
5. **See what's next.** Call `list_posts_advanced` with `status: "scheduled"` and `scheduled_after` set to now, to list what goes out next period.
6. **Write the report.** Use `references/email-template.md`. Keep it to one screen.
7. **Offer changes.** Ask if they want it shorter, in a different tone, or with a section removed.