agentleFS
lukashouthoofdlukashouthoofd/cenekathon/.agents/skills/data-ml-quickstart/SKILL.md

data-ml-quickstart

Skill1 starsChanged 12 days agoMITView on GitHub

Use when the challenge involves a dataset, classic machine learning, forecasting, or analytics — fast EDA, baseline model, honest evaluation, and presenting results.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Define the question & metric: before modelling (regression → MAE.

    line 9
  2. Very specific:

    Keep notebooks out of main unless needed.

    line 18

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Data & ML quickstart

  1. Look at the data first (15 min): shape, dtypes, missing values, duplicates, target distribution, 5 raw rows. pandas: df.info(); df.describe(); df.isna().mean(). Write down what each column means and what leaks the answer.
  2. Define the question & metric before modelling (regression → MAE; classification → F1/PR-AUC when imbalanced; ranking → top-k hit rate). Tie it to the user's decision.
  3. Baseline first: majority class / mean / last value / simple rule. Then logistic or linear regression, then gradient boosting (lightgbm/xgboost/sklearn). Stop when it beats baseline meaningfully.
  4. Split correctly: by time for time series, by group/user for repeated entities; no leakage (fit scalers/encoders on train only). Keep a final holdout untouched until the end.
  5. Pre-trained over trained: for text/images/audio use hosted or open models (embeddings, classification, OCR, speech) rather than training from scratch.
  6. Explain: feature importances / SHAP / example errors. Show 3 failure cases honestly.
  7. Ship it: save the model (joblib) or call the API; expose via the backend (backend-api); cache predictions; pin library versions in requirements.txt.
  8. Visualize for the pitch: one clear chart per message (use a plain bar/line, labelled axes, highlighted takeaway).
  9. Scale story: batch vs streaming, retraining schedule, monitoring drift, feature store — talk, don't build.

Keep notebooks out of main unless needed; put reproducible logic in src/ scripts. Large data → don't commit; document the download step in docs/STACK.md.

Done when: a script reproduces the metric from raw data in one command and the number is on a slide with its baseline next to it.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.