building-onboarding-workflows
Skill0 starsChanged 9 days agoMITView on GitHub
Builds, reviews, and troubleshoots Sendly workflow automations such as welcome, drip, and onboarding email series; new workflows are created disabled. Use when the user asks to 'build a welcome series for new signups', 'create a drip campaign', 'set up an onboarding email sequence', 'what does this workflow do', 'why isn't my onboarding workflow running', 'change the delay before the second email', or wants to automate lifecycle emails.
In this repository66 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- adding-uptime-monitorsSkill
- analyzing-page-performanceSkill
- booking-meetingsSkill
- 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-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
6 rules. About 0 are common, 1 is distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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
- 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 36
Call sendly:list_templates and map each email step to a template.
- Very specific: line 37
Call sendly:create_workflow (or sendly:clone_workflow from a similar one).
- Very specific: line 39
If it is not sending: check it is enabled, call sendly:list_events to see whether the trigger event is arriving, and call …
- Distinctive: line 45
Never enable a workflow, or change one that is already enabled, without an explicit yes in this turn.
≈ “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/building-onboarding-workflows/SKILL.md by scripts/sync-skills.mjs. Edit the plugin copy, then run the script. -->Sendly onboarding workflow
Turn a plain-language brief into a multi-step workflow, and explain or fix existing ones. A live workflow sends real email to every contact who triggers it, so turning one on needs the user's explicit yes.
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:list_workflows,sendly:get_workflow: existing workflows and their full definition (trigger and steps).sendly:get_workflow_status: whether a workflow is enabled, its step count, and its execution count.sendly:list_workflow_executions: individual runs, to see where contacts stopped.sendly:list_events: recent events, to check the trigger event actually arrives.sendly:list_templates: templates the email steps can use.sendly:create_workflow: create a workflow from a structured spec. Created withenabled: falseby default.sendly:clone_workflow: copy an existing workflow as a starting point.sendly:edit_workflow: change a workflow's step graph.sendly:update_workflow: change a workflow's settings. Step changes go throughsendly:edit_workflow.sendly:manage_workflow: change a workflow's state. Read its description for the actions it accepts.
Workflow
- For a new workflow, restate the brief as a trigger and a numbered list of steps (for example: on
member.signupsend Welcome, wait 3 days, send Nudge). Confirm it with the user. - Call
sendly:list_templatesand map each email step to a template. Point out steps that have no template yet. - Call
sendly:create_workflow(orsendly:clone_workflowfrom a similar one). Leave it disabled. Report its id and steps. - For an existing workflow, call
sendly:get_workflow_statusandsendly:get_workflow, and describe the trigger and each step in plain words. - If it is not sending: check it is enabled, call
sendly:list_eventsto see whether the trigger event is arriving, and callsendly:list_workflow_executionsto see where runs stop. Report the first cause you find. - To change steps, show the before and after, get an explicit yes, then call
sendly:edit_workflow. - To turn a workflow on, say that it will start sending real email to every contact who triggers it from now on, get an explicit yes, then make the change.
Rules
- Never enable a workflow, or change one that is already enabled, without an explicit yes in this turn.
- Workflows refuse a
fromaddress that is not on a verified domain. If that happens, offer thechecking-email-deliverabilityskill. sendly:edit_workflow,sendly:manage_workflow, andsendly:delete_workfloware annotated destructive, andsendly:update_workflowcan change what a live workflow sends. Call each only after an explicit yes naming the workflow.- Confirm the workflow by name before
sendly:delete_workflow.
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.

