agentsclimarketplace
Sign in

Environment setup doctor

Skill aoli0919/learn-anything-skills/skills/environment-setup-doctor

Diagnose setup problems, separate environment issues from concept issues, and provide fallback learning paths.From its SKILL.md

Install
npx -y skills add aoli0919/learn-anything-skills --skill environment-setup-doctor

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

  • 23 days oldThe repository was created 23 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.

SKILL.md

2.6 KB, 532 tokens by cl100k_base, as published. Nobody here has run it

Environment Setup Doctor

Category: Tools Data

When To Use

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

  • Diagnose setup problems, separate environment issues from concept issues, and provide fallback learning paths.
  • 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.

What ships with it: 1 file

323 B alongside SKILL.md

agents/

Gives 0 of the 12 instructions most project setup skills give in 532 tokens

Counted across 999 of the 1,637 authors here whose files we hold, read 2026-08-07

  • Ask one question at a timein 29 of 999, across 28 files
  • Detect the package manager from lockfilesin 28 of 999, across 9 files
  • Present findings to the userin 26 of 999, across 5 files
  • Explore current repo statein 24 of 999, across 3 files
  • Update the agent skills block in place if it existsin 24 of 999, across 3 files
  • Install husky lint-staged and prettierin 23 of 999, across 4 files
  • Create the lintstagedrc filein 22 of 999, across 3 files
  • Commit all changed filesin 22 of 999, across 3 files
  • Run lint-staged to verify it worksin 22 of 999, across 3 files
  • Create the husky pre-commit filein 21 of 999, across 2 files
  • Create a prettierrc file if missingin 21 of 999, across 2 files
  • Initialize huskyin 21 of 999, across 2 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 to prevent sprawl
  • 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. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,861. 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.