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
- pahlevikun/levistacktheir own version, first seen Nov 1, 2026
- rikilamadrid/lorekeeperword for word, first seen Oct 13, 2026
- milistu/agent-skillstheir own version, first seen Mar 2, 2026
Other versions3 projects use a version of this.
Word for word · 1
- rikilamadrid/lorekeeper★ 1100% same
Edited · 0
None found.
Wrote their own version · 2
- milistu/agent-skills★ 8same name
- pahlevikun/levistack★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository53 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- blog-post-redactorSkill
- challenge-meSkill
- debate-meSkill
- debug-issueSkill
- handoffSkill
- hooksmithSkill
- kickstart-pathfinderSkill
- learn-codebaseSkill
- learn-featureSkill
- learning-reviewSkill
- map-systemSkill
- orchestrateSkill
- prototypeSkill
- quiz-meSkill
- reflectSkill
- render-artifactSkill
- reverse-engineerSkill
- roleSkill
- setup-trackerSkill
- skillsmithSkill
- teach-architectureSkill
- teach-featureSkill
- ticketSkill
- to-specsSkill
- to-ticketsSkill
- whereamiSkill
- blog-post-redactorSkill
- debate-meSkill
- debug-issueSkill
- handoffSkill
- hooksmithSkill
- kickstart-pathfinderSkill
- learn-codebaseSkill
- learn-featureSkill
- learning-reviewSkill
- map-systemSkill
- orchestrateSkill
- prototypeSkill
- quiz-meSkill
- reflectSkill
- render-artifactSkill
- reverse-engineerSkill
- roleSkill
- setup-trackerSkill
- skillsmithSkill
- teach-architectureSkill
- teach-featureSkill
- ticketSkill
- to-specsSkill
- to-ticketsSkill
- whereamiSkill
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
- Distinctive: line 9
Use this skill after a lesson or quiz when the user wants to apply the concept rather than merely recall it.
- Distinctive: line 43
Keep it small enough for one focused session.
- Distinctive: line 47
Do not simply ask the learner to reproduce the same feature.
- Distinctive: line 68
Do not edit code until the user explicitly approves implementation.
- Distinctive: line 69
Use a feature branch.
- Distinctive: line 70
Do not merge or commit without permission.
- Distinctive: line 71
Keep challenge code separate from production work when appropriate.
- Distinctive: line 75
After the learner responds:
- Very specific: line 81
Update context/learning/progress.md, using the confidence scale defined in its ## Confidence Scale section.
≈ “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.
Files
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
- The relevant lesson
context/learning/progress.md- The feature spec and focused implementation when needed
- 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 constraintsdebug— diagnose a realistic defectrefactor— improve structure while preserving behaviorimplement— 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 Scalesection. If the file does not exist,quiz-mecarries the header to create it with. - Mark
transferableonly when the concept was applied correctly in the changed context, and never using the example that introduced it.
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
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.

