reviewing-social-performance
Skill0 starsChanged 9 days agoMITView on GitHub
Reports how social posts performed in Postify: posts delivered, delivery rate, failures, per-channel stats, and the best times to post on each platform. Use when the user asks 'how did last month go', 'which channel performs best', 'show my social media analytics', 'how many posts went out', 'why did posts fail', 'when should I post on Instagram', or wants a social media performance report. Read-only.
In this repository66 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- adding-uptime-monitorsSkill
- analyzing-page-performanceSkill
- booking-meetingsSkill
- building-onboarding-workflowsSkill
- building-study-guidesSkill
- capturing-tasksSkill
- capturing-web-pagesSkill
- chasing-unpaid-invoicesSkill
- checking-domain-connectionsSkill
- checking-email-deliverabilitySkill
- checking-notification-deliverySkill
- checking-uptime-statusSkill
- cleaning-up-bookkeepingSkill
- connecting-customer-domainsSkill
- discussing-buildsSkill
- drafting-invoicesSkill
- drafting-social-postsSkill
- editing-demosSkill
- editing-page-draftsSkill
- extracting-document-textSkill
- finding-meeting-timesSkill
- handling-flaky-changesSkill
- investigating-tasksSkill
- making-demo-videosSkill
- managing-bookingsSkill
- managing-content-calendarSkill
- managing-demosSkill
- managing-voice-librarySkill
- planning-revisionSkill
- preflighting-domainsSkill
- publishing-pagesSkill
- reading-financial-reportsSkill
- reading-text-aloudSkill
- reading-web-pagesSkill
- reporting-snapvisor-usageSkill
- researching-course-materialSkill
- researching-summary-librarySkill
- responding-to-incidentsSkill
- reviewing-email-performanceSkill
- reviewing-notification-workflowsSkill
- reviewing-visual-buildsSkill
- reviewing-workloadSkill
- searching-getitdone-api-docsSkill
- sending-email-campaignsSkill
- sending-notificationsSkill
- setup-bioflowSkill
- setup-calySkill
- setup-demofySkill
- setup-dodomainSkill
- setup-getitdoneSkill
- setup-notiflySkill
- setup-postifySkill
- setup-sendlySkill
- setup-shortySkill
- setup-snapvisorSkill
- setup-superbooksSkill
- setup-unotesSkill
- setup-upapiSkill
- setup-uptimelySkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Read the workspace's delivery analytics and turn them into a short, honest report.
- Very specific: line 13
Every tool in this skill comes from the postify MCP server, the Postify connector, and is written here as postify:<tool>.
- Very specific: line 15
Tools listed by name: call them directly, for example postify:list_posts.
- Very specific: line 30
If there were failures, call postify:list_posts filtered to failed for the window and list them with their channel and datetime so the user …
- Very specific: line 31
Call postify:suggest_optimal_time for each platform the user publishes on and give the top suggestion per platform.
- Distinctive: line 36
Only report numbers the tools returned.
- Distinctive: line 37
Do not compare the user to industry benchmarks.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
<!-- Generated from plugins/postify/skills/reviewing-social-performance/SKILL.md by scripts/sync-skills.mjs. Edit the plugin copy, then run the script. -->Postify performance review
Read the workspace's delivery analytics and turn them into a short, honest report.
Connecting and calling the tools
Every tool in this skill comes from the postify MCP server, the Postify connector, and is written here as postify:<tool>.
- Tools listed by name: call them directly, for example
postify:list_posts. - Only
postify:search_toolsandpostify:execute_typescriptlisted (Code Mode, the default): callpostify:search_toolsfirst, then call each tool insidepostify:execute_typescriptasexternal_<tool>(for exampleexternal_list_posts); the program mustreturnits result. Scopes, confirmations and gates are identical on both surfaces. - "Tool not found": switch to the Code Mode route instead of retrying the direct call. If
postify:search_toolsdoes not return the tool either, its OAuth scope was not granted; the user reconnects Postify and approves that scope. - No
postifytools at all: Postify is not connected yet. Follow thesetup-postifyskill.
Tools you will use
postify:get_analytics: workspace analytics for delivered posts: post counts, delivery rate, per-channel stats, for a date range.postify:suggest_optimal_time: suggested posting times per platform from the workspace's own publish history. No model call, no external data.postify:list_posts: to name the specific posts behind a number when the user asks "which ones".
Workflow
- Agree the window (default: the last 30 days). Call
postify:get_analyticsfor it. - Report in this order: total posts delivered, delivery rate, failed posts, then a per-channel table sorted by volume.
- If there were failures, call
postify:list_postsfiltered tofailedfor the window and list them with their channel and datetime so the user can act. - Call
postify:suggest_optimal_timefor each platform the user publishes on and give the top suggestion per platform. - Close with at most three concrete next steps drawn from the numbers.
Rules
- Only report numbers the tools returned. If a metric is missing, say it is not available in Postify analytics.
- Do not compare the user to industry benchmarks; there are none in the data.
- This skill only reads. Never call
postify:create_draft,postify:reschedule_post,postify:publish_now, orpostify:delete_postfrom it.
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.

