agentleFS
rikilamadridrikilamadrid/pathfinder/skills/challenge-me/SKILL.md

challenge-me

Skill1 starsChanged 44 days agoMITView on GitHub

Create a small transfer exercise that applies a learned feature concept in a changed context.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    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
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Use this skill after a lesson or quiz when the user wants to apply the concept rather than merely recall it.

    line 9
  2. Distinctive:

    Keep it small enough for one focused session.

    line 43
  3. Distinctive:

    Do not simply ask the learner to reproduce the same feature.

    line 47
  4. Distinctive:

    Do not edit code until the user explicitly approves implementation.

    line 68
  5. Distinctive:

    Use a feature branch.

    line 69
  6. Distinctive:

    Do not merge or commit without permission.

    line 70
  7. Distinctive:

    Keep challenge code separate from production work when appropriate.

    line 71
  8. Distinctive:

    After the learner responds:

    line 75
  9. Very specific:

    Update context/learning/progress.md, using the confidence scale defined in its ## Confidence Scale section.

    line 81

≈ “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

Challenge Me

Use this skill after a lesson or quiz when the user wants to apply the concept rather than merely recall it.

A good challenge changes the context while preserving the underlying concept.

Read First

  1. The relevant lesson
  2. context/learning/progress.md
  3. The feature spec and focused implementation when needed
  4. Current git status if the challenge may involve code

Skip any of these that does not exist. Pathfinder creates these files only when a workflow first needs them, so their absence is normal and is not an error. Do not create them just to satisfy this list.

Challenge Types

Choose one, or honor the requested argument:

  • design — propose an architecture or API under new constraints
  • debug — diagnose a realistic defect
  • refactor — improve structure while preserving behavior
  • implement — build a small extension in a sandboxed or explicit feature branch

Challenge Requirements

The challenge must include:

  • Scenario
  • Learning objective
  • Constraints
  • Definition of done
  • Evidence expected from the learner
  • Hints, hidden initially
  • Evaluation rubric

Keep it small enough for one focused session.

Transfer Rule

Do not simply ask the learner to reproduce the same feature.

Change at least one meaningful dimension:

  • data volume
  • asynchronous behavior
  • user role
  • accessibility requirement
  • failure mode
  • state ownership
  • real-time updates
  • backend contract
  • performance constraint
  • mobile interaction
  • team or package boundary

Coding Safety

For implement or refactor:

  • Explain the proposed scope first.
  • Do not edit code until the user explicitly approves implementation.
  • Use a feature branch.
  • Do not merge or commit without permission.
  • Keep challenge code separate from production work when appropriate.

Evaluation

After the learner responds:

  • Evaluate against the rubric.
  • Identify the strongest decision.
  • Identify the most important weakness.
  • Explain a stronger solution.
  • Update context/learning/progress.md, using the confidence scale defined in its ## Confidence Scale section. If the file does not exist, quiz-me carries the header to create it with.
  • Mark transferable only when the concept was applied correctly in the changed context, and never using the example that introduced 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.