Individual skill

data-analyzer

Inspect datasets, calculate trustworthy summaries, identify patterns and anomalies, and explain decision-relevant findings with explicit assumptions.

skills/data-analyzer/SKILL.md

Read pinned source

Source commit e53892cdaf8babc0ccc7c376c7ce3bd1998c2694

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Not checked yet
Last checked: Nov 7, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 63
Repository last updated: Aug 13, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

agent-skills Repository topic
ai-agents Repository topic
automation Repository topic
codex Repository topic
hermes Repository topic
productivity Repository topic
skill-library Repository topic
vietnamese Repository topic
claude Repository topic
claude-code Repository topic
data Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 3,051 bytes
agents/openai.yamlasset · 319 bytes

Read excerpt


# Rylai Data Analyzer

Turn supplied data into supported conclusions. Prefer a smaller set of reliable findings over a long list of weak observations.

## Analysis Workflow

1. **Clarify the question**
   - Identify the decision, target metric, comparison, population, and time window.
   - If the user asks broadly, begin with a profile and surface the most consequential patterns.

2. **Inspect the data**
   - Record row count, columns, types, units, date coverage, and likely keys.
   - Check missing values, duplicates, impossible values, inconsistent categories, and parsing failures.
   - Preserve the original data and make exclusions visible.