diet — Claude Code skill: diet planning and installation
This Claude Code skill builds a nutrition plan around health goals, medical conditions, allergies, and food preferences. It activates for requests about diet, weight, or eating with high cholesterol or glucose.
MIT ★ 93 updated 2026-11-15
npx skills add Insilico-org/plsi --skill diet -a claude-codeWhat diet does
The skill gathers weight and metabolic markers, digestive conditions, allergies, and preferences through PLSI commands. If weight data is incomplete, it asks for height, weight, and waist measurements; it never calculates BMI itself.
It then sets one to three nutrition goals and drafts plan actions with predictions and intervals. The skill writes the proposal to work/<thread>/proposal-nutritionist.json. PLSI Nostradamus merges it into the plan, screens for conditions and allergies, and sends it for review. The skill does not check, record, or adopt the plan.
If a request shows restriction, purging, or fear of weight gain, the skill declines and routes it to orchestrator/urgent without setting a weight goal. It requires PLSI, PLSI Nostradamus, and PLSI Data Processor.
What it helps with
- build a nutrition plan that accounts for allergies and food preferences
- set goals tied to weight or metabolic markers
- prepare plan actions and predictions for PLSI review
- decline diet planning when the request signals unsafe eating behavior
Example prompts for the agent
- Help me plan meals around my allergies and food preferences.
- Check whether my weight is healthy and set nutrition goals.
- What should I eat if my cholesterol or glucose is high?
How to install diet
1Skills CLI (Vercel)
npx skills add Insilico-org/plsi --skill diet -a claude-code2Manually: put the files in place
~/.claude/skills/diet/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/diet/
1Skills CLI (Vercel)
npx skills add Insilico-org/plsi --skill diet -a codex2Manually: put the files in place
.agents/skills/diet/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Insilico-org/plsi --skill diet -a cursor2Manually: put the files in place
.cursor/skills/diet/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Insilico-org/plsi skills/nutritionist/diet2Manually: put the files in place
.github/skills/diet/SKILL.md1Skills CLI (Vercel)
npx skills add Insilico-org/plsi --skill diet -a gemini-cli2Platform CLI
gemini skills install https://github.com/Insilico-org/plsi --path skills/nutritionist/dietManually: put the files in place
.devin/skills/diet/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about diet
How do I install diet in Claude Code?
Run npx skills add Insilico-org/plsi --skill diet -a claude-code. The skill file is at ~/.claude/skills/diet/SKILL.md.
What does diet do?
It gathers health and food-preference details, sets nutrition goals, and sends proposed actions and predictions to PLSI Nostradamus for the plan. It does not check or adopt the plan itself.
What does diet need to work?
It requires PLSI, PLSI Nostradamus, and PLSI Data Processor. It reads the user's state and uses PLSI tools to find and verify research evidence.
Source text
SKILL.md · MIT
--- name: diet description: Use as PLSI Nutritionist when the user wants help planning their diet - nutrition goals, whether their weight is healthy, meals that respect digestive conditions, allergies and food preferences - so the plan is grounded in their state and scored like any other plan. --- # PLSI plan my diet **Status: placeholder**. ## When to use - "Help me plan my diet", "is my weight OK", "what should I eat for my cholesterol / glucose". - A goal in `personal_context` is about weight or nutrition. - Not when the request `summary` names a `scope:` line (`orchestrator/urgent`) or any input shows restriction, purging or fear of weight gain: return a `result` that declines, names the care (`orchestrator/urgent`) and sets no weight goal. ## Steps 1. Read the state: weight-related and metabolic markers, conditions (digestive disorders), allergies, goals and preferences. ```bash plsi state show --instance <instance> --map cardiometabolic plsi state show --instance <instance> --map care_context plsi state show --instance <instance> --map personal_context ``` 2. Weight: report `bmi` and `waist` as projected, with dates and the map's boundaries. If they are missing, put height, weight and waist in the step's `question` handoff and pass the answers to `processor/intake` in your `result`; never compute BMI yourself. 3. Fill gaps in the context in the same `question` handoff (ONE per step, with step 2's): food allergies or intolerances when `care_context` shows `allergies` as missing (never leave foods out for a missing list), digestive symptoms or diagnoses not yet recorded, food exclusions and preferences (vegetarian, halal, lactose, dislikes), cooking time and budget band. List the answers in your `result` as `condition`, `allergy` or `preference` observations for `processor/intake`. 4. Set 1-3 nutrition goals tied to coordinates (e.g. waist, ldl_c, hba1c) using evidence gathered now, and list each in your `result` as a `goal` observation; PLSI adds "Record these goals" to the plan's adoption card and PLSI Data Processor records them on Start, after Nostradamus adopts the plan (no separate goal question): ```bash plsi evidence search --source pubmed --query "<dietary pattern> <outcome> randomized trial" plsi evidence verify --kind pmid --id <pmid> ``` Reuse the evidence library and verify only what you cite (`shared/team`, Evidence speed). 5. Draft the diet as plan actions (patterns, portions, timing; no brands) with predictions and intervals. **Propose to PLSI** for `nostradamus/plan` (PLSI Nostradamus) steps 2-4: write the actions, claims and predictions to `work/<thread>/proposal-nutritionist.json` (`shared/team` rule 3) and return a `result` with its path; Nostradamus merges them into the one plan, screens against conditions and allergies, runs `plan check`, has PLSI hand it to `challenger/challenge` and records and adopts only after PLSI's adoption card. Never check, record or adopt a plan yourself. ## Rules - Every allergy and digestive condition is respected; screening cautions are shown before adoption. - Sample menus and recipes are fine in chat; only plan actions and predictions go into PLSI.
© Insilico-org · MIT · Insilico-org/plsi