Results for “stata”

Fetch and display stored r(), e(), and s() results from the last Stata command.

Tail, read, or search a Stata log file from a previous command or background task.

Install, configure, update, or verify mcp-stata across Claude Code, Codex, Gemini CLI, Cursor, Windsurf, and VS Code. Activate when users ask to set up the Stata toolkit or troubleshoot the installation.

Run static analysis on a Stata .do or .ado file and report style and best-practice issues.

Improve, modernize, and optimize existing Stata code for performance, portability, and maintainability. Use when legacy patterns such as preserve/restore, cd,

Comprehensive Stata reference for writing correct .do files. Covers syntax, options, gotchas, and idiomatic patterns. Use this skill whenever the user asks you to write, debug, or explain Stata code. Generates ready-to-run .do files for the user to execute manually.

Describe and summarize the current dataset in memory. Optionally inspect a specific variable with codebook.

Build and review paper-ready regression, balance, and summary tables from Stata outputs. Use when the user needs a clean table for a draft, appendix, or coauthor share-out.

STATA code pattern library for empirical archival accounting research. Provides tested syntax from 126 peer-reviewed JAR (Journal of Accounting Research) replication files (2017-2025). Use when the user asks procedural questions like "How do I implement [method]?" or "Show me code for [technique]" — including: entropy balancing, propensity score matching (PSM), difference-in-differences (DiD), regression discontinuity (RDD), instrumental variables (IV), event studies (CAR/BHAR), survival analysis, Fama-MacBeth regressions, bootstrap, quantile regression, reghdfe/xtreg/areg, clustering standard errors, fixed effects, esttab/outreg2 table formatting, winsorization, leads/lags. Users can specify their variables (e.g., treatment, outcomes, controls) and receive adapted syntax. NOTE: This skill provides code patterns from published papers, not research design advice.

Standardized Python & Stata coding practices for empirical research projects

Provides React state management patterns and code examples for useState, Context, Zustand, Redux Toolkit, and TanStack Query.

Use when STAAD integration, API development, or data synchronization is needed. This agent specializes in STAAD connectivity within the IntegrateForge AI ecosystem.

Run replication, robustness, and specification-sensitivity workflows for Stata projects. Use when a researcher wants to reproduce a result, rerun a pipeline, compare specifications, audit a do-file sequence, or check whether a claim is stable.

Manages SST applications by discovering project config, checking stack status, and inspecting bound resources. Supports deployment, live Lambda debugging, secret management, and multi-stage environments.

Use when ASTA Powerproject integration, API development, or data synchronization is needed. This agent specializes in ASTA Powerproject connectivity within the IntegrateForge AI ecosystem.

last_updated: 2026-03-02T14:30:00Z

Master modern React state management with Redux Toolkit, Zustand, Jotai, and React Query. Use when setting up global state, managing server state, or choosing between state management solutions.

Creates a structured, queryable snapshot of a domain's current state, capturing entities, relationships, and properties with confidence scores and evidence anchors.

Assists with building and deploying full-stack serverless applications on AWS using SST. Use when defining Lambda functions, API Gateway routes, DynamoDB tables, S3 buckets, or deploying Next.js/Remix/Astro with SSR on AWS. Trigger words: sst, serverless stack, sst dev, sst deploy, aws lambda, sst ion, resource linking.

Classical end-to-end empirical analysis workflow in the traditional Stata ecosystem — native Stata + reghdfe + ivreg2 + csdid + did_imputation + eventstudyinteract + sdid + rdrobust + rddensity + synth + synth_runner + psmatch2 + teffects + ebalance + coefplot + esttab + asdoc + binscatter. **Defaults to economics empirical-paper style** (AER / QJE / AEJ) — every run produces a publication-ready output set with a multi-column regression table (M1→M6 progressive controls/FE) as the centerpiece, plus Table 1 (descriptives), mechanism / heterogeneity / robustness tables, and event-study + coefficient + trend figures. Covers the full 8-step Stata pipeline an applied economist runs on every paper — (1) data import & cleaning (use/import, destring, misstable, duplicates, merge assert), (2) variable construction (gen/egen/winsor2/xtile/xtset with L./F./D.), (3) descriptive statistics & Table 1 (tabstat/balancetable/asdoc), (4) classical diagnostic tests (sktest/swilk/hettest/imtest/xtserial/xttest3/vif/dfuller/kpss/

Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state/action separation for React state management.

JS State Pattern

PHPStan static analysis in Sage/Acorn projects — lando composer phpstan, phpstan.neon configuration, PHPStan level 0-9, WordPress PHP stubs, szepeviktor/phpstan-wordpress, baseline generation, CI phpstan, suppress errors, type errors, return type mismatch, nullable types, WordPress function stubs, WP_Post WP_Query WP_User types

Stacks: Bitcoin smart contract layer with Clarity language, sBTC for native peg, Nakamoto upgrade for fast finality, PoX (Proof of Transfer) consensus. USE WHEN: building Bitcoin smart contracts, integrating sBTC, evaluating Stacks vs RSK / EVM alternatives.

GOF State Pattern

Clean and transform messy data for analysis in Python, R, or Stata

Live-device iOS QA for SwiftUI apps. (gstack)

Verificar o status atual do projeto Railway para este diretório. Use quando o usuário perguntar "status railway", "está rodando", "o que está deployado", "status de deployment" ou sobre uptime. NÃO para queries de variáveis ou configuração - use a skill railway-environment para isso.

State-Based Button Display Skill

Upgrade gstack to the latest version. Detects global vs vendored install, runs the upgrade, and shows what's new. Use when asked to "upgrade gstack", "update gstack", or "get latest version". Voice triggers (speech-to-text aliases): "upgrade the tools", "update the tools", "gee stack upgrade", "g stack upgrade".