framing-ml-problems
/framing-ml-problems
Opisuje problem danych i ML przed modelowaniem: decyzję, koszt błędu, typ zadania, cel i miarę sukcesu.
- Autor
- ras7961 ↗
- Repozytorium
- flyrank-ml-internship-starter ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 11.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 11.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Opisuje problem danych i ML przed modelowaniem: decyzję, koszt błędu, typ zadania, cel i miarę sukcesu.
Oryginalny opis (EN)
Frames a data/ML problem before any modeling — the decision, the action, the cost of a wrong call, task type, target, and success metric. Use when picking a project direction, writing a research question, or mapping a problem onto an ML task type.
Jak działa
- The four questions (answer all four, in writing)
- Map it to a task type
- Write the one-paragraph frame
- How to verify
Podgląd SKILL.md
--- name: framing-ml-problems description: Frames a data/ML problem before any modeling — the decision, the action, the cost of a wrong call, task type, target, and success metric. Use when picking a project direction, writing a research question, or mapping a problem onto an ML task type. --- # Framing ML problems A model is never the goal. A better DECISION is the goal. Frame first, model later. ## The four questions (answer all four, in writing) 1. **What decision does this improve?** Not "predict X" — decisions. "Which page should an editor fix first?" is a decision. "Predict decline" is not, yet. 2. **Who acts on the output, and what do they do?** Name the person and the action. If nobody would act differently, the work has no customer. 3. **What does a wrong answer cost?** Wasted editor hours? A missed decline? The cost of errors decides how careful the method must be, and which errors matter more. 4. **Why does data or ML help at all?** Sometimes a plain rule (an if-statement) is the right answer. Sometimes a dashboard is. ML earns its place only when the pattern is real but too messy to write by hand — many signals, tangled, shifting over time. ## Map it to a task type | If your question sounds like… | Task type | Target | Typical metric | |---|---|---|---| | "Which ones first?" | Ranking / scoring | a priority score | precision@K | | "Will this one decline / recover?" | Classification | a yes/no label from an OBSERVED outcome | ROC-AUC, precision/recall vs base rate | | "What kinds of items exist?" | Clustering | none (unsupervised) | silhouette + human sense-check | | "Which signals travel together?" | Signal analysis | none | effect sizes, grouped comparisons | Two rules that save whole projects: - **The target must be observed, not defined.** A label that comes from someone's rule means your model learns the rule, not the world. Prefer outcomes measured in a later time window. - **Name the metric before training.** "Good" defined after the fact always looks good. ## Write the one-paragraph frame > For [who], deciding [what], we will build [output type] from [data], predicting/scoring > [target] measured by [metric]. A wrong call costs [cost]. A plain rule isn't enough because > [why]. We will claim only [observed / directional / decision-support] results. If you can fill that paragraph honestly, you are framed. If a blank stays blank, that blank IS your next task. ## How to verify - Show your frame to someone (or your assistant) and ask: "what decision does this improve?" If their answer differs from yours, the frame isn't done. - Check the target: is it observed in the data, or defined by a rule? If defined — reframe. - Check the metric exists in your data. Can you compute it today, on a baseline? Do it.
Wersje
W bazie nie ma innych skilli o nazwie framing-ml-problems.
Migawka bazy z 13.11.2026 · wersja paczki 723c929e7667 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 90problem-framing
Zamienia brief biznesowy, PRD lub opis danych w jednostronicowy ANALYSIS_MANIFEST.md przed modelowaniem: cel, metryka, baseline i koszt błędów. - 90ml-problem-framing
Ujmuje problem ML wokół decyzji, mierzalnego celu i uczciwych kosztów błędów, zanim ktokolwiek zacznie pracę z modelami. - 100021-problem-framing
Formułuje problem przed głębszą analizą: opis problemu, stan obecny, stan docelowy, interesariuszy i kryteria sukcesu. - 96problem-framing
Przekształca niejasne wyzwanie projektowe w jasną definicję problemu: kontekst, ograniczenia, metryki sukcesu i założenia rozwiązania. - 100question-framing
Przed analizą danych porządkuje pytanie badawcze w specyfikację projektu analizy z siedmioma polami. - 100question-framing
Układa pytanie analityczne w drabinę pytań: cel, decyzja, metryka i hipoteza, a dopiero potem sięga po dane.