Results for “stat”

Run work as an explicit event-driven state machine executed by subagents. The orchestrator is the runtime from the canonical loop — `state, effects = init(machine); execute(effects); while state is active: event = nextEvent(); state, effects = transition(machine, state, event); execute(effects); return state.output`. All routing judgment is authored ONCE, at plan time, into a machine file (states, event alphabet, transition table, budgets, final states); at runtime the orchestrator does pure table lookups and dispatches effects — it never decides, never authors, never ingests artifacts. Subagent/sync protocol is the timeboxed-iterating one: role prompts scaffolded once to disk and dispatched BY PATH, an initialiser preamble every subagent reads first, a self-populating cheatsheet, per-unit files, tiny structured returns, independent measurement gate. Use when the user says "workmachine", "run this as a state machine", "state-machine this", or when a goal has a small number of clearly named phases with explicit outcomes (built / passed / failed / blocked) and you want the routing to be auditable rather than judged on the fly. For clock-driven loops use timeboxed-iterating; for wide graphs with judged edge criteria use workgraph.

The English summary is being prepared. Showing the original description.

Run flowctl catalog status to check the control-plane state of an Estuary resource, or list catalog specs to see which connectors exist and which are active. Use when checking whether a task is running, disabled, or failing, interpreting status output, or enumerating connectors. Use when user says "check task status", "is my capture running", "catalog status", "flowctl catalog status", "what's wrong with my capture", "task failing", "check catalog status", "collection status", "derivation status", "why is my task disabled", "list my connectors", "show me my connectors", "list captures", "list materializations", "what connectors do I have", or "show me all my active connectors".

The English summary is being prepared. Showing the original description.

Use this skill when the user asks how to determine whether a CMV operation is interstate vs intrastate, why it matters (federal vs state rules apply), the "continuation of journey" rule, state-specific intrastate exemptions, and what happens when an intrastate carrier picks up an interstate load. Cite 49 CFR 390.5 + state-specific exemptions.

The English summary is being prepared. Showing the original description.

Plan how an Angular app stores and updates data used by its screens. Covers local and shared state, choices involving Signals, NgRx, and RxJS, synchronization with server data, debugging, and migration from older patterns.

• Choose an Angular state management approach
• Design state shared across an app
• Manage data within individual components

Connect Table v9 state to Alpine bindings and manage pagination from application code. Explains reactive reads, getter and callback setup, shared state atoms, and why some captured values fail to follow later updates.

• Control pagination from Alpine state
• Display current table state in Alpine bindings
• Investigate stale values after state replacement

Read and control TanStack Table v9 state in Vue while keeping updates synchronized with the interface. Covers reactive reads, externally controlled state, update callbacks, shared state containers, and component boundaries for rendering.

• Controlling pagination with Vue refs
• Displaying table state through computed values
• Investigating state synchronization failures

Helps connect json-render to a writable Jotai atom, a unit that holds application state. Covers adapter setup and sharing a Jotai store so json-render and React components read and update the same values.

• Manage json-render state with a Jotai atom
• Share an existing Jotai store with json-render
• Share state between useAtom() and json-render

Replace C# static calls for time, files, or environment values with existing abstractions that tests can substitute. Update construction and affected tests within a defined scope, while preserving read counts, evaluation order, date-time semantics, and existing static callers.

• Migrating DateTime.UtcNow calls to TimeProvider
• Replacing File calls with an existing IFileSystem
• Replacing disk or environment access in unit tests with fakes

Configure login state and access rules in Blazor Web Apps. Accounts for server and browser rendering, protects pages by role or policy, and helps diagnose missing authentication state or errors on Identity pages.

• Restrict pages by login status, role, or policy
• Show interface elements according to user permissions
• Keep login state available after WebAssembly loads

Turn regression results and summary statistics from Stata, R, or Python into LaTeX tables for academic papers. Format model comparisons, decimal places, statistical significance markers, and notes, with guidance for wide tables and inclusion in a paper.

• Comparing several regression models in one table
• Formatting summary statistics for a paper
• Combining results into a table with multiple panels

Find STATA code examples for empirical accounting research from published replication files. Adapt regression, matching, event study, and table export syntax to your variables, with citations to the papers behind each example.

• Implement fixed effects regressions in STATA
• Find published DiD and matching code examples
• Export regression results as formatted tables

End-to-end Stata replication pipeline — scaffolds numbered `.do` files in `scripts/stata/`, executes them via the `stata-mcp` MCP server, captures logs and outputs to `output/`, and produces publication-ready tables (esttab) and figures (graph export). Mirrors `/data-analysis` for R-first projects. Use when user says "stata replication", "set up Stata pipeline", "scaffold the .do files", "run Stata analysis", "AEA replication package in Stata", or when a project's analysis language is Stata not R.

The English summary is being prepared. Showing the original description.

Review and improve statistical reporting in manuscript methods, results, and figure captions. It checks sample definitions, repeated measurements, tests, and uncertainty, then provides revised wording and identifies missing information or issues reviewers may raise.

• Reviewing a manuscript’s statistical methods section
• Checking sample sizes and repeated measurements
• Aligning figure captions with reported statistics

Prepare income statements with prior-period and budget comparisons, highlight significant differences, and explain their drivers. Reference formats for balance sheets and cash flow statements also support financial reporting and period-end adjustments.

• Preparing monthly or quarterly income statements
• Investigating significant differences from budget
• Summarizing financial results for leadership

Manage Table v9 state in Svelte 5, including pagination controlled by application code. Guides reactive reads that update the interface, getter and callback wiring, and the distinction between tracked values and one-time snapshots.

• Control pagination from application state
• Show table state in a Svelte interface
• Investigate values that stop updating

Implement reactive state reads and external control for Table v9 in Solid. Learn where to track changes, how to manage pagination state, and how to handle updater functions or shared state correctly.

• Control pagination with Solid signals
• Investigate table updates that do not appear on screen
• Share table state through external atoms

Manage TanStack Table v9 state in React, including controlled pagination and subscriptions that update the UI when state changes. It also guides narrower rendering boundaries and fixes for React Compiler memoized components.

• Control pagination with React state
• Fix table state changes that do not update the UI
• Limit which components rerender

Manage TanStack Table v9 state in Octane, including controlled pagination and subscriptions that keep the UI updated. It explains component subscription boundaries, stable external atoms for shared state, and how controlled updates reach the store.

• Control pagination with Octane state
• Fix table state changes that do not update the UI
• Set up component subscription boundaries

Read and control Table v9 state in Preact, including pagination. Guides state subscriptions, which keep the interface updated, and externally managed state so table changes and controls stay synchronized while rerenders can be scoped to relevant values.

• Control pagination from Preact state
• Fix table values that fail to update on screen
• Limit rerenders to selected state

Diagnose unresponsive GKE GPU or TPU nodes and pods stuck terminating through read-only checks of node status, logs, serial output, and repair history. Receive documented recovery guidance to apply yourself.

• Investigate nodes stuck in NodeStatusUnknown
• Find kernel panic or hardware failure evidence
• Check node auto-repair settings and failures

Check active PUA agents and teams from Codex CLI using an alias for the Claude Code status command. Review process IDs and record lifetimes when available, alongside stale records.

• Checking active PUA agents and teams
• Reviewing process IDs and record lifetimes
• Finding stale PUA records

Create a temporary workbench for one existing component, using realistic mock data and a grouped state switcher. View loading, empty, error, access, and other implemented states individually, with a link to each state.

• Comparing loading, empty, and error states in a table
• Checking displays for different roles and plans
• Inspecting layouts with realistic amounts of sample data

Create summary tables, treatment and control comparisons, and correlation matrices using Python, R, or Stata. Summarize averages, variation, sample sizes, and missing data to understand a dataset before regression or prepare tables for a research paper.

• Explore a dataset before regression
• Prepare a paper's summary statistics table
• Compare treatment and control groups

Prepare survey and administrative datasets for analysis with Python, R, or Stata. Generate cleaning code to handle missing values, duplicates, outliers, and derived variables, with documented transformations and integrity checks that support reproducible research.

• Clean missing values, duplicates, and outliers in survey data
• Merge multiple data sources for analysis
• Prepare panel datasets that track units over time