stata

Standardize Stata data cleaning workflows with coding standards and documentation.

7|5|Updated Sep 16, 2025
One-click install
npx skills add https://github.com/PovertyAction/ipa-stata-template --skill stata-povertyaction
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stata
Source: https://github.com/PovertyAction/ipa-stata-template/tree/main/.claude/skills/stata
Command: npx skills add https://github.com/PovertyAction/ipa-stata-template --skill stata-povertyaction

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Stata data cleaning and analysis skill addresses the need for reproducible, well-documented workflows by standardizing how researchers import data, manage variables, apply IPA/DIME Analytics coding standards, and document decisions across Stata projects.

Core Features & Use Cases

  • Core Principles: Reproducible code, defensive checks, and thorough documentation aligned with no-PII practices.
  • Data Cleaning Workflow: Import, deidentify, clean, and construct analysis variables following a structured pipeline.
  • Use Cases: Cleaning survey data, preparing analysis-ready datasets, and maintaining project-wide documentation and codebooks.

Quick Start

Apply the Stata data cleaning and analysis standards to your dataset by following the guidelines in this guide.

Frequently Asked Questions about stata

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

FAQPage Schema
How do I create reproducible Stata data cleaning workflows for survey datasets?

Reproducible Stata data cleaning workflows are created by standardizing data import, variable management, and documentation. This approach enforces IPA/DIME analytics coding standards and defensive checks to ensure reliable analyses across survey and administrative datasets.

What is the best way to structure Stata projects for reliable analysis?

The best way to structure Stata projects for reliable analysis is by applying a clear project structure with defensible reviews. This standardizes how researchers import data, manage variables, and document decisions across Stata projects to maintain project-wide documentation.

How do I enforce coding standards and defensible reviews in Stata?

Coding standards and defensible reviews in Stata are enforced by applying IPA/DIME Analytics guidelines. This ensures reproducible code, thorough documentation, and defensive checks aligned with no-PII practices throughout the data cleaning pipeline.

Can I use this Stata workflow for both survey and administrative datasets?

Yes, this Stata workflow applies to both survey and administrative datasets. It covers the complete data cleaning pipeline, including importing, deidentifying, cleaning, and constructing analysis variables for reliable analyses.

How do I handle missing values and quality checks during Stata data management?

Missing values and quality checks are handled during Stata data management by applying defensive checks throughout the cleaning pipeline. This ensures data quality and reliability when preparing analysis-ready datasets and maintaining project-wide codebooks.

Does this Stata data management approach support deidentification and no-PII practices?

Yes, this Stata data management approach supports deidentification and no-PII practices. It integrates core principles of reproducible code and thorough documentation to safely deidentify survey data before constructing analysis variables.