data analysis

Design Community

Skill notes

Understand the Question

Before touching the data, clarify: What question are we answering? ("Is our conversion rate improving?" is an answerable question. "Analyze this data" is not — help the user sharpen it.) Who needs the answer? (Engineer debugging an issue? Executive making a budget decision? Researcher testing a hypothesis?) What decisions will this inform? (This determines how precise you need to be and what format the answer should take.)

Reference Materials and Scripts

Execute profile_data.py with a data file path to get a quick profile of any CSV, Excel, or JSON dataset — it reports shape, types, missing values, stats, and value distributions. Run with --help for usage. Load statistical-tests-guide.md when choosing statistical tests — it has a decision matrix for test selection, effect size interpretation tables, and sample size guidelines.

Understand the Data

Before analysis, get your bearings: Source and context: Where did this data come from? How was it collected? What time period does it cover? Schema: What are the columns/fields? What do they represent? What are the data types? Scale: How many rows/records? What's the granularity? (Per user? Per day? Per transaction?) Known issues: Is the data known to be incomplete, biased, or have quality problems?

Step 1: Clean and Validate

Data quality determines analysis quality. Don't skip this. Handle Missing Values Count them first: What percentage of each column is missing? Understand why: Are they random? Systematic? (e.g., optional fields vs data collection failures) Choose a strategy and document it:

Step 2: Explore

Start broad, then focus on what's interesting. Descriptive Statistics Always start here — understand the basics before going deeper. Distributions Understanding shape matters for choosing the right tests.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Design
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@Upsonic · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
Python
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Clean and Validate

Data quality determines analysis quality. Don't skip this. Handle Missing Values Count them first: What percentage of each column is missing? Understand why: Are they random? Systematic? (e.g., optional fields vs data collection failures) Choose a strategy and document it:

02
Step 2: Explore

Start broad, then focus on what's interesting. Descriptive Statistics Always start here — understand the basics before going deeper. Distributions Understanding shape matters for choosing the right tests.

03
Step 3: Analyze

Choose the right method for the question. Comparison Questions ("Is A different from B?") Use the right statistical test: Two groups, continuous outcome: t-test (if normal) or Mann-Whitney U (if not) Multiple groups: ANOVA (if normal) or Kruskal-Wallis (if not)

04
Step 4: Communicate Findings

Structure matters as much as the analysis itself. Lead With the Answer Start with what the user asked. Then support it. Pattern: Visualization Guidelines

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.