- Home
- Skills
- Workflow Automation
- AI Meeting Planning & Action Tracker
Works with the AI Agents you already use
AI Meeting Planning & Action Tracker
Architect technical email automation specifications with precise logic, workflow maps, and implementation requirements.
$4.99
AI Meeting Planning & Action Tracker
Example session with this skill installed
Design a welcome workflow for a B2B SaaS trial. Trigger: Account Created. Goal: Feature activation of the dashboard and invite team members. Exclude current paying customers.
- Read your context and instructions
- Compiled the ai meeting planning
I have designed a trial onboarding workflow focused on dashboard activation and team collaboration. This specification ensures that current customers are excluded and that the flow exits once the primary goals are met.
B2B SaaS Trial Activation Workflow
| Step | Type | Delay | Detail | Branch/Condition |
|---|---|---|---|---|
| 1.0 | Trigger | Instant | Account Created | If 'Customer_Status' is NOT 'Active' |
| 2.0 | Email 1 | 0 mins | Welcome & Dashboard Setup | Link to /setup-wizard |
| 3.0 | Wait | 2 days | - | Check: Dashboard_Initialized (True/False) |
| 4.0 | Logic | - | Branching | IF False -> Go to 4.1; IF True -> Go to 5.0 |
| 4.1 | Email 2a | 0 mins | Dashboard Help / Tutorial | CTA: Book Onboarding Call |
| 5.0 | Email 2b | 0 mins | Invite Your Team | CTA: /settings/team |
| 6.0 | Wait | 3 days | - | Check: Team_Size > 1 |
| 7.0 | Exit | - | Goal Met | Remove from flow |
Workflow Map
[ENTRY: Account Created]
|
[CHECK: Status == 'Active'?] -- YES --> [EXIT]
|
NO
|
[EMAIL: Welcome & Setup]
|
[WAIT: 2 Days]
|
[CONDITION: Dashboard Configured?]
/
NO YES
/
[EMAIL: Tutorial] [EMAIL: Invite Team]
\ /
[WAIT: 3 Days]
|
[CONDITION: Team Invited?]
/
NO YES
/
[REMIND] [EXIT: Success]
Email Step Briefs
Email 1: Welcome & Setup
- Purpose: Immediate value delivery.
- Subject: Welcome to [Platform] - Let's get your dashboard ready.
- CTA: Finish Setup.
- Personalization: {first_name}, {company_name}.
Email 2a: Dashboard Help
- Purpose: Assist users who haven't performed the core action.
- Subject: Need a hand with your setup?
- CTA: Watch Video Guide.
Next steps
- Verify the 'Dashboard_Initialized' event is firing correctly from your app to your CRM.
- Confirm the 'Customer_Status' tag is updated in real-time to ensure exclusion logic works.
- Build the two conditional branches in your automation builder using these wait periods.
Connects securely to your tools. The creator never sees your data.
About this skill
Drafting lifecycle marketing sequences often leads to logic errors, messy branching, or missed edge cases like duplicate enrollments. This skill generates implementation-ready automation specifications, ensuring your triggers, delays, and conditional logic are technically sound before you touch your ESP.
What it does
- Architects sequences by defining precise triggers, entry criteria, and suppression rules for any lifecycle stage.
- Maps conditional logic using explicit IF/THEN branches to handle different subscriber behaviors and data points.
- Generates workflow maps providing a text-based flowchart that visualizes every path, delay, and exit point.
- Defines data requirements by listing the exact events, tags, and custom fields needed for implementation.
- Creates testing protocols including checklists for enrollment, branch firing, and fallback behavior.
How it works
- Provide your business model, the specific workflow goal, and the primary trigger event.
- Define your audience segments, available customer data, and any specific platform constraints.
- Review the generated sequence outline, logic branches, and text-based workflow map.
- Use the implementation handoff and data requirements list to build the automation in your CRM or ESP.
Frameworks & tools
This skill is platform-agnostic but uses terminology compatible with Klaviyo, HubSpot, Mailchimp, ActiveCampaign, and Braze. It focuses on logical architecture rather than platform-specific API calls.
Why this beats prompting it yourself
Generic prompts often overlook critical safety features like exit rules, re-entry policies, and quiet-hour considerations. This skill enforces a structured logic audit, ensuring every branch has a destination and every data dependency is identified.
Use cases
- Design a high-intent abandoned cart recovery sequence with discount laddering.
- Map a multi-day SaaS trial onboarding flow that branches based on feature adoption.
- Architect a re-activation campaign for customers who have hit an inactivity threshold.
- Define a post-purchase cross-sell sequence that excludes users with open support tickets.
Known limitations
This skill does not execute code, send emails, or connect to external APIs. It produces documentation and maps, not live automation scripts or direct ESP configurations.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Workflow Automation.
Does not connect to email platforms, send messages, or access live subscriber data. Limited to text-based documentation and logical mapping.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 8 days ago
Permissions
No special permissions declared or detected