postlake-analytics
Skill2 starsChanged 2 months agoMITView on GitHub
Read social media performance from PostLake: per-post results and normalised cross-platform analytics (impressions, reach, engagement, CTR, follower growth). Use to report on results or decide what to post next.
- Reads credentials
In this repository7 other files it gives its agents.
- b2c-marketingSkill
- multi-account-operatorSkill
- postlake-accountsSkill
- postlake-inboxSkill
- postlake-mediaSkill
- postlake-publishSkill
- postlake-scheduleSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 42
When asked "how did X do?", fetch per-post analytics and summarise the strongest metric per platform.
- Distinctive: line 44
When asked "what should I post next?", pull cross-platform analytics, find which network + content type has the best engagement/CTR, and …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
PostLake: analytics
Two views: a single post's performance, and normalised cross-platform analytics over a period so an agent can compare networks and decide what to post next.
Auth
Authorization: Bearer $POSTLAKE_API_KEYBase URL https://api.postlake.dev.
Per-post analytics
curl https://api.postlake.dev/v1/posts/POST_ID/analytics \
-H "Authorization: Bearer $POSTLAKE_API_KEY"Returns per-platform metrics for that post (impressions, likes, comments, shares, saves, clicks (whatever the platform exposes), in one normalised shape.
Cross-platform analytics
curl "https://api.postlake.dev/v1/analytics?period=30d" \
-H "Authorization: Bearer $POSTLAKE_API_KEY"period is 7d, 30d (default), or 90d. Returns totals plus a per-platform
breakdown (impressions, reach, engagement rate, CTR, saves, and follower growth)
already normalised so you can benchmark networks against each other.
How to use it well
- When asked "how did X do?", fetch per-post analytics and summarise the strongest metric per platform.
- When asked "what should I post next?", pull cross-platform analytics, find which network + content type has the best engagement/CTR, and recommend accordingly.
- Metrics are as fresh as each platform reports; some lag a few hours after posting.
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.