operating-mhealth-services

Deploy and operate a reproducible mHealth ETL platform with standardized runbooks.

Updated Jun 7, 2025
One-click install
npx skills add https://github.com/rikunisikawa/data-flow --skill operating-mhealth-services
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: operating-mhealth-services
Source: https://github.com/rikunisikawa/data-flow/tree/main/agent-skills/skills/operating-mhealth-services
Command: npx skills add https://github.com/rikunisikawa/data-flow --skill operating-mhealth-services

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a standardized, repeatable set of operational procedures for deploying and running the mHealth ETL platform. It helps teams achieve safe, auditable deployments, consistent runbooks, and streamlined execution of Terraform, dbt/Elementary, and related operational tasks.

Core Features & Use Cases

  • Deployment automation: Build artifacts, upload to S3, and apply Terraform for consistent environments.
  • Operational runbook governance: Centralized procedures for day-to-day operations and rollback notes.
  • dbt/Elementary execution readiness: Clear guidance to run analytics transformations and validation steps in a controlled manner.

Quick Start

Follow the standard runbook: review the deployment strategy and Terraform design docs, consult the operations checklist, and perform the deployment steps for your target environment (dev or prod). If dbt is involved, use the provided scripts or docker setup per the guide.

Frequently Asked Questions about operating-mhealth-services

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy and operate a reproducible mHealth ETL platform?

To deploy an mHealth ETL platform, you follow a standardized operational runbook that covers building artifacts, uploading to S3, applying Terraform, and executing dbt transformations across dev and prod environments.

What is the best way to manage dbt and Elementary execution in production ETL workflows?

Managing dbt and Elementary execution requires standardized runbook governance that provides clear guidance to run analytics transformations and validation steps in a controlled, auditable manner for production environments.

How do you apply Terraform consistently across dev and prod environments for ETL deployment?

Applying Terraform consistently requires environment-specific variables and documented procedures within an operational runbook, ensuring reproducible infrastructure provisioning and safe, auditable deployments across dev and prod.

Can I use this runbook approach for mHealth ETL rollback procedures?

Yes, the runbook approach supports mHealth ETL rollback procedures by providing centralized operational references and clear checks, ensuring operational readiness and auditable governance during day-to-day operations.

Why do I need documented procedures and runbooks for mHealth ETL operations?

Documented procedures and runbooks are required for mHealth ETL operations to satisfy auditable deployment demands, enforce runbook governance, and guarantee step-by-step execution guidelines that ensure operational readiness.