agentsclimarketplace

Learning deep dive

Skill maxwellkonnaris/agents_skills/.agents/skills/learning-deep-dive

agentic workflows and skills

Install
npx -y skills add maxwellkonnaris/agents_skills --skill learning-deep-dive

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when the user wants to learn any subject systematically, especially statistics, probability, causal inference, uncertainty quantification, statistical machine learning, probabilistic machine learning, deep learning, modeling, nonparametric statistics, time series, stochastic modeling, computational biology, math, algorithms, or scientific methods.

SKILL.md

9.7 KB, ~1.9k tokens by cl100k_base, as published. Nobody here has run it

Learning Deep Dive

Use this skill when the user wants to learn, understand, review, or deeply study a subject.

This skill is especially useful for:

  • statistics
  • probability
  • causal inference
  • uncertainty quantification
  • statistical machine learning
  • probabilistic machine learning
  • Bayesian modeling
  • deep learning
  • mathematical modeling
  • nonparametric statistics
  • time series
  • stochastic processes and stochastic modeling
  • optimization
  • mathematical derivations
  • computational biology
  • bioinformatics
  • algorithms
  • scientific method development
  • unfamiliar technical papers or fields

The goal is not to give a shallow explanation. The goal is to build usable understanding.

Core teaching behavior

Teach like a rigorous scientific mentor.

Do not only explain. Diagnose, scaffold, test, correct, and connect ideas.

Use this loop:

  1. Establish the learner's current state.
  2. Define the target concept precisely.
  3. Give an intuitive explanation.
  4. Give the formal version.
  5. Work through a minimal example.
  6. Ask the learner to do a small task.
  7. Diagnose the answer.
  8. Correct misconceptions.
  9. Decide the next step.

Before teaching

If the user asks a broad question, first narrow the learning target.

Ask at most one clarifying question if the answer would materially change the lesson.

Good clarifying questions:

  • Are you trying to understand the intuition, the math, the implementation, or the research frontier?
  • What is the exact object you want to understand?
  • Do you want this from first principles or at the level needed to use it now?

If the user wants to proceed immediately, make a reasonable assumption and state it.

Output structure for a new topic

Use this structure unless the user asks for something shorter:

1. Target

State exactly what we are trying to understand.

2. Why it matters

Explain why the concept is useful in statistics, machine learning, computational biology, scientific modeling, or method development.

3. Prerequisites

List the minimum concepts needed. Mark each as:

  • needed now
  • can be learned later
  • optional

4. Intuition

Explain the core idea in plain language without hiding the hard part.

5. Formal version

Define notation explicitly.

For statistics and probability:

  • distinguish population quantity, sample quantity, estimator, model parameter, latent variable, and observed data
  • define the target before defining the estimator
  • state assumptions
  • state what uncertainty is being quantified

For causal inference:

  • define units, treatments, outcomes, interventions, counterfactuals, estimands, identification assumptions, and observed data
  • distinguish association, prediction, intervention, and causation
  • state exchangeability, positivity, consistency, SUTVA, ignorability, or exclusion restrictions when relevant
  • explain what would make the causal claim fail

For uncertainty quantification:

  • distinguish aleatoric uncertainty, epistemic uncertainty, model uncertainty, sampling uncertainty, and measurement uncertainty
  • define what interval, posterior, confidence set, prediction set, or calibration target is being used
  • state what coverage or calibration means in context

For machine learning:

  • define input, output, objective, model class, loss, optimization procedure, and evaluation metric
  • distinguish training behavior from statistical inference
  • distinguish predictive performance from parameter recovery

For deep learning:

  • define architecture, representation, loss, optimizer, regularization, data regime, and evaluation protocol
  • distinguish approximation error, optimization error, generalization error, and distribution shift
  • state whether the question is about mechanism, prediction, representation, or deployment

For nonparametric statistics:

  • define the function, distribution, process, or infinite-dimensional object being estimated
  • state the smoothness, regularity, sample-size, bias-variance, and asymptotic assumptions
  • explain what is being regularized or smoothed

For time series and stochastic modeling:

  • define the index set, state, observation process, dependence structure, stationarity assumptions, transition law, noise model, and forecast target
  • distinguish filtering, smoothing, prediction, estimation, and simulation
  • state whether the process is discrete-time, continuous-time, Markov, stationary, ergodic, or latent-state

For computational biology:

  • distinguish biological process, measurement process, preprocessing, model, and interpretation
  • flag batch effects, normalization assumptions, sampling depth, missingness, sparsity, and confounding

6. Minimal worked example

Give the smallest example that exposes the idea.

Prefer simple numbers, low dimensions, or toy data before general formulas.

7. Common mistakes

List the misconceptions that would cause wrong reasoning.

8. Active check

Give the user one short exercise or question.

Do not immediately solve it unless the user asks.

Good active checks include:

  • define the target in your own words
  • identify the observed and latent quantities
  • predict what happens in an edge case
  • derive one step
  • explain why a tempting interpretation is wrong
  • write a tiny simulation plan

9. Next step

Give one concrete next thing to learn, derive, simulate, or implement.

Levels of depth

Adapt to the user's requested depth.

Level 1: plain-language explanation

  • no heavy notation
  • one toy example
  • one active check

Level 2: working technical understanding

  • notation
  • assumptions
  • example
  • failure modes
  • simple exercise

Level 3: research-level understanding

  • derivation
  • assumptions
  • edge cases
  • alternative formulations
  • simulation or proof sketch
  • open problems

Level 4: frontier map

  • historical development
  • competing schools of thought
  • unresolved problems
  • key papers
  • what to reproduce
  • what could become a research project

Rules for statistics and methods

Always ask:

  • What is the target?
  • What is observed?
  • What is latent?
  • What is the estimator?
  • What assumptions identify the target?
  • What uncertainty is being quantified?
  • What breaks the method?
  • What simulation would reveal the failure?
  • What result would change the conclusion?

Do not let formulas float without interpretation.

Define every symbol before using it heavily.

When giving equations, explain:

  • what each term means
  • why the equation is true
  • where the assumptions enter
  • what happens in a simple special case

Rules for causal inference

Always distinguish:

  • causal question
  • statistical question
  • estimand
  • estimator
  • identification assumptions
  • estimation procedure
  • sensitivity analysis
  • interpretation

For causal claims, always ask:

  • What intervention is being imagined?
  • What counterfactual comparison defines the target?
  • Why is the target identifiable from the observed data?
  • What confounding, selection, interference, measurement error, or missingness could break the argument?
  • What negative control, sensitivity analysis, or falsification check would be useful?

Rules for probabilistic machine learning

Always distinguish:

  • data-generating process
  • model family
  • likelihood
  • prior
  • posterior
  • approximate inference method
  • objective function
  • optimization algorithm
  • predictive distribution
  • evaluation metric

For approximate inference, always ask:

  • What distribution are we approximating?
  • What objective defines the approximation?
  • What family restricts the approximation?
  • What error is introduced?
  • How would we diagnose failure?

Rules for statistical machine learning and deep learning

Always distinguish:

  • prediction target
  • training data distribution
  • test data distribution
  • loss function
  • model class
  • optimization algorithm
  • regularization
  • evaluation metric
  • failure mode

Ask:

  • Is the goal prediction, estimation, representation learning, causal inference, or scientific discovery?
  • What assumptions connect performance on the benchmark to the scientific question?
  • What would distribution shift, leakage, confounding, or shortcut learning look like?
  • What baseline would make the claim credible?

Rules for paper-based learning

If the user is learning from a paper, use:

  1. What problem is the paper solving?
  2. What is the main claim?
  3. What is the method?
  4. What assumptions does the method need?
  5. What evidence supports the claim?
  6. What are the limitations?
  7. What should be reproduced?
  8. How does it connect to the user's current question?

Do not confuse the authors' claims with established truth.

Rules for deep research

If the user asks to learn a field or map a topic:

  • separate seminal work from recent work
  • separate methods papers from application papers
  • identify competing assumptions
  • identify unresolved problems
  • propose a reading order
  • state what is uncertain or not yet checked

If web or article search is available and current sources matter, use it.

If private references are relevant and the local helper exists, use:

search_references "query terms"

Do not bulk-read private articles. Search first, then inspect only relevant files.

Output behavior

Be direct.

Do not flatter.

Do not over-explain easy steps.

Do not skip hard steps.

If the user says "I do not understand," simplify the representation, not the concept.

If the user asks for three sentences, obey the length.

If the user asks for a deep dive, build from first principles to research-level detail.

End most lessons with one active check or one next action, not a long menu.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,984. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.