exploration
Skill2 starsChanged 41 days agoMITView on GitHub
Develop independently reasoned mathematical-modeling candidates and fixed comparison material for an approved case.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- hajekim/agentic-design-patterns-extensiontheir own version, first seen Apr 1, 2026
- hajekim/agentic-design-patterns-skillstheir own version, first seen Apr 1, 2026
- rongarede/claude-skills-orchestrationtheir own version, first seen Mar 27, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- hajekim/agentic-design-patterns-skills★ 4same name
- hajekim/agentic-design-patterns-extension★ 1same name
- rongarede/claude-skills-orchestration★ 1same 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 repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- coordinatorSkill
- evidenceSkill
- executionSkill
- publicationSkill
- reviewSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Use a Variant only for implementation/configuration changes within a Candidate.
- Distinctive: line 14
Before formal scoring, fix data/split, metric formulas and units, constraints, meaningful baseline, fair budget, failure denominator, and …
≈ “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
Exploration
Produce a Candidate as a readable mathematical route: subproblem, origin, variables/objective/constraints, derivation, pseudocode, sources, assumptions, limitations, and a structural difference from known routes. An algorithm name, prompt persona, or parameter setting is not a distinct Candidate.
First-round authors receive only the problem contract, selected data/material, and reliable shared sources. Do not inject another first-round draft or recommendation. A human suggestion remains one candidate or a challenge target unless the human explicitly fixed a base route and its conditions independently hold.
Use a Variant only for implementation/configuration changes within a Candidate. A changed mathematical structure, stage composition, objective, or error propagation is a new Candidate; a fusion records parents but begins unreviewed.
Before formal scoring, fix data/split, metric formulas and units, constraints, meaningful baseline, fair budget, failure denominator, and stopping condition in a ComparisonContract. Preserve evidence, uncertainty, and tradeoffs in comparison packs. Do not manufacture aggregate scores, benchmarks, totals, or experimental conclusions.
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.