Check a CSV before modeling
Point the Skill at an approved CSV in a dedicated folder. Review detected column types and missingness in the redacted summary, then ask the data owner to verify any ambiguous field before selecting features.
Use the Exploratory Data Analysis Skill to profile approved local data before modeling. Its core tools summarize supported files without network access and flag limits the reviewer needs to see.
Record the allowed input and check aggregate structure and missingness before choosing an analysis.
Provide the approved folder, filename, and the decision this inspection will inform.
Copy the request into a new Floatboat conversation and provide the required material.
Download FloatboatPreview and copy the request. It is not sent automatically from this page.
Reference: Exploratory Data Analysis https://github.com/K-Dense-AI/scientific-agent-skills/blob/main/skills/exploratory-data-analysis/SKILL.md Read the original documentation and check the current environment and dependencies. Propose any new installation or tool connection before proceeding. My task: Use K-Dense AI’s exploratory-data-analysis Skill to profile my approved local CSV with the bundled core script. Show the file and allowed directory before running. Report aggregate missingness, sampling limits and follow-up checks without exporting rows or modifying the source. Expected deliverable: A redacted aggregate report with explicit coverage and data-quality checks.
K-Dense AI’s MIT-licensed Skill supplies bounded Python inspectors and analysis instructions. Its standard-library core handles CSV, TSV and strict JSON with redacted aggregate reporting. Optional formats have separate dependencies. Use the results to decide what to verify before modeling, and keep unsupported files outside the inspection.
Use the same boundaries when comparing files, but vary what you inspect according to the next research decision. Keep the original data and its aggregate review separate.
Point the Skill at an approved CSV in a dedicated folder. Review detected column types and missingness in the redacted summary, then ask the data owner to verify any ambiguous field before selecting features.
Profile both approved exports with comparable limits. Compare their column counts and aggregate missingness, noting sampling and schema differences before asking for a corrected delivery.
Provide a local JSON file and the expected record structure. Use the bounded inspection to identify unexpected structure, then record which checks need an approved follow-up.
Provide the prediction target and data split rules alongside the approved data. Review candidate leakage signals separately from confirmed defects and ask for source evidence before removing a field.
Choose an explicit local directory and supported format. Review the aggregate profile and its coverage before relying on any suggested data-quality finding.
Name the allowed local root and list the exact files. Keep inputs outside the task scope out of the run.
Use the Skill’s bundled script for the file type with Python 3.11 or later and preserve the aggregate output.
Compare the report with the file type, limits and next analysis decision. Keep the source files intact.
Read another Skill guide and check its original source before using it.