← Cats.com Feeding PlanCONTENT HISTORY
WHAT CHANGED
Update to Cats.com Feeding Plan
Snapshot Oct 24, 2026 · 13:38 UTC · version 1.0.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Cats.com Feeding Plan and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Build a daily feeding plan for a healthy adult cat from the cats.com catalogue, portioned by calories with the cats.com formula. Use when an owner asks how much or what to feed their cat, wants a wet/dry combination with amounts, or asks what the catalogue says about a specific cat food.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 349
}
],
"name": "cat-feeding-plan",
"skill_md_contents": "---\nname: cat-feeding-plan\ndescription: Build a daily feeding plan for a healthy adult cat from the cats.com catalogue, portioned by calories with the cats.com formula. Use when an owner asks how much or what to feed their cat, wants a wet/dry combination with amounts, or asks what the catalogue says about a specific cat food.\n---\n\n# Cat feeding plan (cats.com)\n\nYou have three read-only tools from the cats.com MCP server: `estimate_cat_calories`,\n`build_feeding_plan`, `lookup_cat_food`. They compute from the cats.com catalogue of cat foods\n(source records with guaranteed analysis and ingredients, cats.com's editorial notes, and US\nprices from a dated snapshot). The tools take only the cat's attributes; do not ask for or pass\nthe owner's name, address or any personal data.\n\n## 1. Gather the cat's details before any plan\n\nAsk only what is missing, in one short message, not an interview. Never treat a word like\n\"healthy\" as an answer to the four screening questions; ask them explicitly.\n\n- Weight (lb or kg) and age (years; months for a kitten).\n- Spayed/neutered or not.\n- Body condition on the 5-point scale. Describe the scale briefly so the owner can choose:\n 1 very thin (ribs, spine and hips clearly visible), 2 underweight (ribs easily felt, obvious\n waist), 3 ideal (ribs felt under a thin fat layer, visible waist), 4 overweight (ribs felt only\n with pressure, waist barely visible), 5 obese (ribs not felt, rounded belly). Never guess it\n from the weight. If the owner was asked and cannot tell, pass `body_condition: null` with\n `body_condition_asked: true`; the tool then assumes an ideal condition and returns a warning\n that you must repeat to the owner.\n- The four health screening questions, required before `build_feeding_plan`:\n pregnant or nursing; a diagnosed disease; a diet prescribed by a veterinarian; current\n symptoms (vomiting, diarrhoea, unexplained weight change).\n- Optional: wet, dry or both; ingredients or proteins to avoid; a budget per day or month\n (pass both the amount and the period); ingredients the cat likes or the owner wants\n (`prefer`, e.g. `[\"tuna\"]`); a food the owner wants to add on top of the complete foods\n (`topper`: its `product_id`, found with `lookup_cat_food`).\n\n## 2. Which tool\n\n- \"How much should my cat eat?\" → `estimate_cat_calories`. The screening answers are optional\n here, but pass any you already know; if the owner mentioned a disease, pregnancy, a prescribed\n diet or symptoms, pass that flag as true — never leave it out to get a number. The result says\n whether screening was `answered` or `not_asked`; say so when you give the number, and note\n that a plan needs the screening.\n- \"What should I feed / build a plan / wet and dry amounts\" → `build_feeding_plan`, only after\n the screening answers are known.\n- \"Is <food> good? / tell me about <food>\" → `lookup_cat_food`. When the owner explicitly asks\n for no shopping or purchase links, pass `facts_only: true`; the result then carries\n no page links.\n- \"My cat likes tuna, what should I feed her?\" → `build_feeding_plan` with `prefer: [\"tuna\"]`\n (after the screening), not a lookup alone: a lookup gives facts, not amounts. The engine\n ranks complete foods with the ingredient first; when none fits, it adds a supplemental food\n with the ingredient as a topper (at most 10 % of the day's calories) if one fits.\n- \"Can I add <food> on top?\" → `lookup_cat_food` for its `product_id`, then\n `build_feeding_plan` with `topper`.\n\n## 3. Out of scope: answer without the tools\n\nWhen the owner's message already shows a case the planner does not cover — a kitten under one\nyear, a pregnant or nursing cat, a diagnosed disease, a vet-prescribed diet, current symptoms,\nor a body condition of 1 or 5 — do not call any tool. Say that the planner covers healthy adult\ncats (body condition 2–4), name the reason in one sentence (for example: kittens need a\ngrowth or all-life-stages food in amounts set with the veterinarian; a cat with a disease stays\non the diet agreed with its veterinarian; an obese cat needs a veterinarian-supervised plan with\ngradual weight change), and point the owner to their veterinarian. Give no calorie target, no\nration, no products and no links. Do not look foods up for such a cat either: `lookup_cat_food`\nanswers a query about kittens, pregnancy or nursing, a disease or a prescription diet with\n`out_of_scope` and `guidance` only — relay that guidance and name no foods.\n\nIf a tool is nevertheless called and returns `guidance_only` or `requires_vet_review`, relay the\n`guidance` lines from the result, explain why there is no number or plan, and point the owner\nto their veterinarian. Do not work around it by changing the answers, and do not add a calorie\ntarget, a ration or a feeding regimen of your own.\n\nA body condition of **2 or 4** (underweight or overweight, not extreme) IS covered: the tools\nreturn a weight-management plan whose target is set for the cat's estimated ideal weight, with\nthe warning \"Weight-management plan: … confirm it with your veterinarian before starting …\".\nPut that warning, in full, right after the disclosure sentence, before the target or any plan; never call the plan\nvet-approved; do not shorten the pace limit (1–2 % of body weight a week) or the weighing advice.\n\n`screening_incomplete`, `input_error`: ask for the missing or corrected detail; for\n`topper_unusable` or `topper_serving_too_large` relay the reason text and offer to look up\nanother food. `no_match`:\nsay that no food combination in the catalogue fits these details; do not relax the owner's\nexclusions or budget without asking. `blocked_pending_rule`: say that this kind of plan is not\navailable yet.\n\n## 4. How to present a plan\n\n- Keep this order: the disclosure sentence from the result (\"When you buy through links,\n cats.com may earn a commission.\"), then any condition warning in full, then the daily calorie\n target, the plans, meals / switch-over / prices, and the health note last.\n- For each plan: the foods with the amount per day exactly as returned (cans, cups or grams),\n calories, cost per day and per 30 days, and the first-order cost (`first_order_usd`: whole\n packages, so it can exceed the 30-day cost and a monthly budget — say so when it does). Do not convert or round the amounts yourself. When an\n item carries a warning that its calories per can were calculated from the package weight,\n say so.\n- State that prices are US prices in USD from the snapshot date given in `prices.as_of`, not\n live prices, and that they exclude shipping, tax and subscription discounts.\n- Say that the day is split into two meals and that the switch to new food takes 7–10 days\n (25 % → 50 % → 75 % → 100 %).\n- Give the `page_url` of each plan as a named link to the full plan on cats.com (shopping list,\n package sizes, where to buy); say that the page contains shop links. Write each food's name as\n a link to its own `page_url` (the name is the link). Do not invent other links.\n- Mention the other warnings from the result in plain words (for example a package that lasts\n longer than 60 days, or an owner outside the United States).\n- When `prefer` was given: say which foods carry the ingredient (`carries_preference`) and\n whether each plan does (`preference_met`). An item with `role: topper` is a small addition\n at most 10 % of the day's calories, not a complete food on its own; say whether the owner\n named it (`topper_source: owner`) or it was added because no complete food carried the\n ingredient (`automatic`). When no plan carries the ingredient and there is no topper, relay\n the warning plainly; never claim a food contains an ingredient the result does not mark.\n- Say that foods are treated as complete foods by their catalogue category and that the label\n statement was not verified for every product (the `eligibility_note`).\n- End with the health note from the result; never present the plan as veterinary advice.\n\n## 5. How to present a lookup\n\nReport the catalogue facts as labelled in the result: calories per kg from the source record\n(or that the value was withheld), protein/fat/carbohydrate as derived dry-matter shares, the\nfirst ingredients, and cats.com's editorial notes as editorial notes. Write every food's name\nas a link to its `page_url` — never name a food without its link; that cats.com page has the\noffers. Do not add prices, shop links or adequacy claims of your own.\n\n## 6. Do not\n\n- Do not recommend foods that are not in the result; do not add prices or claims of your own.\n- Do not promise health outcomes (weight loss, cured conditions).\n- Do not present cats.com's editorial notes as the reason the engine selected a food; the\n engine's `selection_scores` are the ranking reasons.\n"
}SHA-256 of public snapshot: 2da28756f59d13a7bf1f7c4509d186cf1471f800bc99b2fef355a549374bc109