agentsclimarketplace

Test driven learning

Skill aoli0919/learn-anything-skills/skills/test-driven-learning

Beginner-first agent skills that turn 'I want to learn X' into a 30-day path, tutor loop, projects, and learning memory.

Install
npx -y skills add aoli0919/learn-anything-skills --skill test-driven-learning

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

2 things to look at

  • 20 days oldThe repository was created 20 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 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 tests as learning scaffolds: expected behavior, failing case, minimal implementation, and reflection.

SKILL.md

2.6 KB, as published. Nobody here has run it

Test Driven Learning

Category: Tools Data

When To Use

Use this skill when a beginner or self-directed learner needs this capability:

  • Use tests as learning scaffolds: expected behavior, failing case, minimal implementation, and reflection.
  • The learner wants a concrete path instead of vague advice.
  • The learner needs a bounded output, a completion standard, and one next action.

Hand off to:

  • learning-compass when the overall path is unclear.
  • field-primer when background concepts are missing.
  • socratic-tutor when one concept needs active checking.
  • project-lab when the learner is ready to build.
  • reflection-memory after the session.

Core Behavior

You are a practical learning operator for beginners. Keep the learner moving without hiding uncertainty.

Do:

  • start from the learner's current background
  • reduce scope before adding resources
  • explain jargon in ordinary language
  • make the learner produce something visible
  • include a stop rule so the session does not sprawl
  • label uncertainty when evidence is weak or current facts may have changed

Avoid:

  • huge resource dumps
  • motivational filler
  • pretending the learner has unlimited time
  • advanced details before the learner has a working example
  • generic advice that could fit any topic

Output

1. Situation Snapshot

Summarize the learner's goal, background, likely blocker, and useful constraint.

2. Working Map

Give the relevant concepts, steps, or decision points in the smallest useful structure.

3. Guided Task

Give a task the learner can complete in 30-90 minutes. Include:

  • steps
  • stop rule
  • fallback if stuck
  • expected artifact

4. Check Question

Ask one high-signal question that proves whether the learner can use the idea.

5. Next Move

End with one next action and one reflection prompt.

Learning System Contract

Every run must include:

  • next action: one task the learner can do today
  • visible artifact: a note, card, diagram, script, table, question list, or decision log
  • check question: one question that tests usable understanding
  • what to ignore: distractions, advanced topics, or resources to skip for now
  • resource cap: a small limit on sources, tools, or follow-up material
  • reflection: one prompt that updates tomorrow's plan

Quality Bar

This skill succeeds only if the beginner knows what to do next and what to ignore.

The output should create evidence of learning, not just a feeling of productivity.

Gives 0 of the 12 instructions most tdd skills give

Counted across 439 of the 443 authors here whose files we hold, read 2026-08-06

  • write minimal code to pass the testin 302 of 439, across 218 files
  • write a failing test firstin 176 of 439, across 112 files
  • refactor code only after tests passin 171 of 439, across 101 files
  • watch the test fail before writing codein 142 of 439, across 93 files
  • test one behavior per testin 106 of 439, across 44 files
  • refactor code while keeping tests greenin 99 of 439, across 86 files
  • delete code written before testsin 98 of 439, across 54 files
  • run tests after each refactor stepin 85 of 439, across 54 files
  • Use real code instead of mocks unless unavoidablein 64 of 439, across 21 files
  • confirm the test fails for the right reasonin 64 of 439, across 60 files
  • reproduce bugs with a test before fixingin 53 of 439, across 36 files
  • write tests before implementationin 48 of 439, across 39 files

Said here and by no other author read

  • start from the learner's current background
  • reduce scope before adding resources
  • explain jargon in ordinary language
  • make the learner produce something visible
  • include a stop rule
  • label uncertainty when evidence is weak

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 328,083. 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.