reviewing-notification-workflows
Skill0 starsChanged 9 days agoMITView on GitHub
Reviews a Notifly environment's notification setup: workflows with their steps and channels, topics, and recent delivery activity. Use when the user asks 'which workflows do we have and on which channels', 'what does this workflow do', 'what topics exist', 'audit our notification setup', 'which workflows send SMS', or wants an overview of their notification workflows. Read-only; never sends.
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-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
7 rules. About 0 are common, 0 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Every tool in this skill comes from the notifly MCP server, the Notifly connector, and is written here as notifly:<tool>.
- Very specific: line 15
Tools listed by name: call them directly, for example notifly:list_workflows.
- Very specific: line 31
Call notifly:list_workflows.
- Very specific: line 33
Call notifly:list_topics and list the topics by name.
- Very specific: line 34
Call notifly:list_notifications for a recent sample.
- Very specific: line 40
Never call notifly:trigger_workflow from this skill.
- Very specific: line 42
Do not show internal fields such as _id, _environmentId, _organizationId, or _creatorId unless the user asks.
≈ “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/notifly/skills/reviewing-notification-workflows/SKILL.md by scripts/sync-skills.mjs. Edit the plugin copy, then run the script. -->Notifly workflow review
Give the user a clear map of what their Notifly environment sends, on which channels, and how it has been doing.
Connecting and calling the tools
Every tool in this skill comes from the notifly MCP server, the Notifly connector, and is written here as notifly:<tool>.
- Tools listed by name: call them directly, for example
notifly:list_workflows. - Only
notifly:search_toolsandnotifly:execute_typescriptlisted (Code Mode, the default): callnotifly:search_toolsfirst, then call each tool insidenotifly:execute_typescriptasexternal_<tool>(for exampleexternal_list_workflows); 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
notifly:search_toolsdoes not return the tool either, its OAuth scope was not granted; the user reconnects Notifly and approves that scope. - No
notiflytools at all: Notifly is not connected yet. Follow thesetup-notiflyskill.
The Notifly server's default surface lists two tools, notifly:search_tools and notifly:execute_typescript. Call notifly:search_tools for the declarations, then call each operation below as external_<name>(...) inside a notifly:execute_typescript program. Fetch several workflows in one program with Promise.all over external_get_workflow. A denied call throws an Error whose message starts with its code. If the operations are listed as individual tools instead, call them directly.
Tools you will use
notifly:list_workflows: the workflows in the connected environment with identifiers, names, tags, and status.notifly:get_workflow: one workflow's steps, channels, and status.notifly:list_topics: named subscriber groups used for fan-out.notifly:list_notifications: recent send events with channels and delivery status.
Workflow
- Call
notifly:list_workflows. Show a table: name, identifier, status, tags. - For each workflow the user cares about (all of them if there are only a few), call
notifly:get_workflowand add its steps in order and its channels to the table. - Call
notifly:list_topicsand list the topics by name. - Call
notifly:list_notificationsfor a recent sample. Count events per workflow and note any channel with failed or skipped deliveries. - Point out what the data shows plainly, for example: inactive workflows, workflows with no recent sends, a channel that keeps failing, or a workflow that uses a channel with no recent successful delivery.
- For one workflow in depth ("what does password-reset do?"), describe its steps in order, the channel of each step, and the payload fields it uses.
Rules
- Never call
notifly:trigger_workflowfrom this skill. If the user wants to send, offer thesending-notificationsskill. - The review covers only the environment picked on the consent screen. Say which one when it matters.
- Do not show internal fields such as
_id,_environmentId,_organizationId, or_creatorIdunless the user asks. - Report only what the tools return. The activity feed is a list of events, not analytics; do not present rates the data does not support.
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.

