Suggest modules when you notice: 2+ checks that share login logic Same selectors used across multiple checks (page objects) Helper functions reused across check
Modules And Alerting streamlines monitoring workflows by identifying reusable code patterns across checks and suggesting modularization to reduce duplication. It also facilitates setting up alert policies that notify teams through Slack, email, or webhooks when checks fail, with configurations to minimize noise from transient issues. This skill helps enforce consistent login logic, shared page selectors, and helper functions via modules while integrating robust alerting to catch critical failures early.
This skill is designed for performance marketers and growth leads managing complex CRO monitoring setups who need reliable, maintainable checks across multiple web properties. SEO and PPC operators running multiple scripts with overlapping logic benefit by consolidating shared code into modules for easier updates. Agency strategists overseeing client monitoring workflows will appreciate the ability to configure multi-channel alerting to ensure timely responses without alert fatigue.
Practitioners start by identifying 2 or more checks that share login steps, selectors, or helper functions and write these shared components into modules stored locally following strict naming and import rules. Next, they push suggested modules to the platform after confirming with stakeholders, then import them into relevant scripts to replace duplicated code. For alerting, users create alert policies via CLI specifying channels like Slack or email, link these policies to specific checks, and configure failure thresholds to avoid false positives. Finally, they deploy checks with multi-region scheduling to ensure broad coverage and timely notifications.
How do I know when to create a module? When multiple checks share login logic, selectors, or helper functions, modularizing reduces maintenance overhead. Can I customize alert channels? Yes, alerts can be sent to Slack, email, or webhooks, allowing tailored notification strategies. What’s a good alert threshold? Setting consecutiveFailuresRequired to 2 helps avoid alerts from transient glitches without missing real issues.
Attach this skill to a Metaflow agent task by linking the Modules And Alerting skill, which will prompt suggestions for modularizing shared logic and offer alert policy setup after deploying checks. Expect the agent to guide you through writing and pushing modules, importing them into scripts, and configuring alert channels with recommended failure thresholds. This skill integrates with scheduling and regional deployment features to provide comprehensive monitoring and notification workflows.
For broader context, see our roundup of marketing skills claude, and read Claude Code workflows for marketing agencies for related setup guidance.