summary
Skill0 starsChanged 2 months agoMITView on GitHub
Show an account activity summary via Postproxy. Use when the user asks "what's the status?", wants an overview of recent posting/engagement, or wants to know what comments, reviews, or DMs are awaiting a reply.
11 other projects use a version of this.
Adopted by
Most recently taken up by
- geneontology/go-skillstheir own version, first seen Nov 1, 2026
- saksham10arora-dotcom/everything-claude-codextheir own version, first seen Nov 1, 2026
- robo311/devflowtheir own version, first seen Oct 20, 2026
- Dev-PGVAA/skillstheir own version, first seen Oct 16, 2026
- finos/git-proxytheir own version, first seen Oct 9, 2026
- isas1/skillstheir own version, first seen Sep 21, 2026
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- finos/git-proxy★ 263same name
- isas1/skills★ 210same name
- saksham10arora-dotcom/everything-claude-codex★ 74same name
- yarikleto/claude-teacher-plugin★ 9same name
- geneontology/go-skills★ 1same name
- robo311/devflow★ 1same name
- timsvoice/skills★ 1same name
- Dev-PGVAA/skills★ 0same name
- kys42/claude-skills★ 0same name
- TechHU-GS/cc-discipline★ 0same name
1 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.
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 17
Prefer this over separate history_list / comments / DM calls.
“Common” is measured: kept by at least 6 in 10 of the 9 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
Answer "what's happening across my accounts?" in one call.
- Choose the window:
24h(default),7d, or30d— or pass explicitfrom/todates. - Optionally scope to one profile group via
profile_groups_list→profile_group_id; omit to cover everything the key can reach. - Call
summary_get.
Render a per-network dashboard:
- Published / failed / next scheduled posts (a multi-network post counts once;
by_platformcounts per-network deliveries). - Engagement totals — lifetime-to-date for posts published in the window, not engagement earned during it;
nullwhen insights are off. - Received: comments, reviews, DM volume (
dmsisnullwhen DMs are off). - Awaiting reply: unanswered comments/reviews and DM chats whose newest message is inbound, plus how many are near the 24h Meta window. Backlog counts always look back 30 days regardless of window (
window.backlog_from).
Prefer this over separate history_list / comments / DM calls. Route follow-ups to /postproxy:comments, /postproxy:google-business (reviews), or /postproxy:dm.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.