reviewing-email-performance
Skill0 starsChanged 9 days agoMITView on GitHub
Reports how the user's Sendly email performed: sends, opens, bounces, campaign stats, a single email's history, and how close the project is to its sending limits. Use when the user asks 'how did my emails do this week', 'did anything bounce', 'what is my open rate', 'how did the newsletter perform', 'what happened to this email', 'how close are we to our sending limit', or wants an email analytics 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-notification-workflowsSkill
- reviewing-social-performanceSkill
- 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
8 rules. About 0 are common, 3 are distinctive, and 5 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.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Read Sendly's analytics and delivery history and turn them into a short, honest report.
- Very specific: line 13
Every tool in this skill comes from the sendly MCP server, the Sendly connector, and is written here as sendly:<tool>.
- Very specific: line 15
Tools listed by name: call them directly, for example sendly:list_contacts.
- Very specific: line 32
If anything bounced, call sendly:list_emails for the window and list the bounced emails with recipient and time.
- Very specific: line 33
If the user asks about a campaign, call sendly:list_campaigns to find it, then sendly:get_campaign_stats.
- Very specific: line 34
Call sendly:get_usage and state how much of today's and this month's sending cap is used.
- Distinctive: line 39
Only report numbers the tools returned.
- Distinctive: line 40
Do not compare against 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/sendly/skills/reviewing-email-performance/SKILL.md by scripts/sync-skills.mjs. Edit the plugin copy, then run the script. -->Sendly email performance
Read Sendly's analytics and delivery history and turn them into a short, honest report. Read only.
Connecting and calling the tools
Every tool in this skill comes from the sendly MCP server, the Sendly connector, and is written here as sendly:<tool>.
- Tools listed by name: call them directly, for example
sendly:list_contacts. - Only
sendly:search_toolsandsendly:execute_typescriptlisted (Code Mode, the default): callsendly:search_toolsfirst, then call each tool insidesendly:execute_typescriptasexternal_<tool>(for exampleexternal_list_contacts); 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
sendly:search_toolsdoes not return the tool either, its OAuth scope was not granted; the user reconnects Sendly and approves that scope. - No
sendlytools at all: Sendly is not connected yet. Follow thesetup-sendlyskill.
Tools you will use
sendly:view_analytics: sent, delivered, opened, and bounced counts for a time window.sendly:list_emails: individual emails with status. Use it to name the emails behind a number.sendly:get_email: one email's delivery history (for example queued, then sent).sendly:list_campaigns,sendly:get_campaign_stats: the list of campaigns and the stats for one campaign.sendly:get_usage: the project's sending counters against its daily and monthly caps.
Workflow
- Agree the window (default: the last 7 days). Call
sendly:view_analyticsfor it. - Report sent, delivered, opened, and bounced, with the bounce rate.
- If anything bounced, call
sendly:list_emailsfor the window and list the bounced emails with recipient and time. For one the user picks, callsendly:get_emailand show its delivery history. - If the user asks about a campaign, call
sendly:list_campaignsto find it, thensendly:get_campaign_stats. - Call
sendly:get_usageand state how much of today's and this month's sending cap is used. - Close with at most three concrete next steps drawn from the numbers. For bounces or low delivery, offer the
checking-email-deliverabilityskill.
Rules
- Only report numbers the tools returned. If a metric is not in the response, say it is not available.
- Do not compare against industry benchmarks; there are none in the data.
- This skill only reads. Never call a send, create, update, or delete tool from it, such as
sendly:send_email,sendly:send_campaign,sendly:update_campaign, orsendly:delete_campaign.
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.

