new-test-client
Skill2 starsChanged 4 months agoMITView on GitHub
Create a new example client in examples/ from a natural-language description, following TrainFitter's JSON schema, and run the pipeline on it to see how the routine/diet/validator respond. Use it when the trainer wants to test a specific case ("try a client who has...", "what would happen if someone came in with...").
In this repository2 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- update-knowledge-baseSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
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
- Very specific: line 37
If the case reveals a real gap in the rule engine (e.g.
≈ “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
Create and test a new example client
Generates quick test cases for the TrainFitter pipeline without the trainer having to write JSON by hand.
Process
- Read the reference schema in
examples/cliente_ejemplo_1.jsonandexamples/cliente_ejemplo_2.json(andadmission/ficha_cliente_template.mdfor the context behind each field). Don't invent new fields outside that schema unless the trainer explicitly asks for it — if they do, treat it as a real schema change and update the agents that consume it too. - Translate the trainer's description into a complete JSON profile, filling in reasonable assumptions for anything unspecified (age, weight, availability...) — leaving it incomplete breaks the agents, which assume the full schema is present.
- Name the file
examples/cliente_prueba_<short-description>.json(don't overwritecliente_ejemplo_1.json/_2.json, which are the reference cases documented indocs/decisiones.md). - Run the pipeline on that client and show the result:
(run fromimport json from orchestrator import ejecutar_pipeline profile = json.load(open("examples/cliente_prueba_<name>.json", encoding="utf-8")) state = ejecutar_pipeline(profile) print(state.veredicto)agents/, or adapt the import path). - Comment on the result in the trainer's terms, not just raw JSON: which split it picked, which warnings fired and why, whether the verdict makes sense given the described case.
- If the case reveals a real gap in the rule engine (e.g. an injury that isn't
detected, a dietary restriction not covered in
food_bank.py), don't fix it silently — tell the trainer what's missing and ask if they want it added.
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.

