data-explorer
Skill99 starsChanged 6 months agoApache-2.0View on GitHub
General-purpose data profiling and exploration. Use when first encountering any dataset to understand its structure, quality, and analysis potential.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- MAGA2010/data-mastertheir own version, first seen Oct 25, 2026
- liangdabiao/claudesdk-data-chattheir own version, first seen May 24, 2026
- liangdabiao/claude-data-analysis-ultra-maintheir own version, first seen May 9, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- liangdabiao/claude-data-analysis-ultra-main★ 282same name
- MAGA2010/data-master★ 78same name
- liangdabiao/claudesdk-data-chat★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository27 other files it gives its agents.
- ai-radio/AGENTS.mdAGENTS.md
- customer-support/AGENTS.mdAGENTS.md
- data-analyst/AGENTS.mdAGENTS.md
- document-processor/AGENTS.mdAGENTS.md
- news-curator/AGENTS.mdAGENTS.md
- repo-maintainer/AGENTS.mdAGENTS.md
- seo-auditor/AGENTS.mdAGENTS.md
- audio-mixingSkill
- cover-image-generationSkill
- metadata-generationSkill
- music-generationSkill
- researchSkill
- script-writingSkill
- tts-generationSkill
- memorySkill
- scannerSkill
- python-dataSkill
- pdf-parsingSkill
- reconciliationSkill
- slide-creatorSkill
- vendor-verificationSkill
- briefingSkill
- curationSkill
- deliverSkill
- fetch-newsSkill
- github-researcherSkill
- git-workflowSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 59
Never assume a specific dataset.
- Distinctive: line 60
If no data files are found, inform the user and ask them to upload.
- Very specific: line 61
Use pandas for profiling. It is pre-installed in the sandbox.
- Very specific: line 62
Use select_dtypes(include=["object", "str"]) for categorical columns.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Data explorer skill
Profile any tabular dataset (CSV, JSON, Parquet) and produce a structured summary the other skills can consume.
Workflow
- Scan workspace: list all data files in the workspace directory.
- Load and profile each file:
- Row count, column count
- Column names, data types, null counts, unique counts
- Basic statistics (min, max, mean, median, std for numerics)
- Value counts for categorical columns (top 10)
- Correlation matrix for numeric columns
- Assess data quality:
- Missing value percentage per column
- Potential data type issues (e.g., numbers stored as strings)
- Duplicate row detection
- Outlier detection (IQR method)
- Output a structured profile as JSON for downstream skills.
- Recommend analysis directions based on what you found.
Output format
{
"files": [
{
"filename": "customers.csv",
"rows": 91,
"columns": 7,
"schema": [
{"name": "CustomerID", "dtype": "object", "nulls": 0, "unique": 91},
{"name": "CompanyName", "dtype": "object", "nulls": 0, "unique": 91}
],
"quality": {
"missing_pct": {"Region": 0.60},
"duplicates": 0
},
"recommendations": [
"CustomerID is a unique string identifier",
"Region column has a high missing percentage (60%)",
"Can be joined with orders.csv on CustomerID to analyze customer behavior"
]
}
]
}Key rules
- Never assume a specific dataset. Profile whatever is present.
- If no data files are found, inform the user and ask them to upload.
- Use
pandasfor profiling. It is pre-installed in the sandbox. - Use
select_dtypes(include=["object", "str"])for categorical columns. - For large files (>100K rows), profile a sample first and note the sampling.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

