The guest standing in front of you right now: 10 AI skills for service recovery
allergen-incident-response
the written allergen answer and the 999 facts, decided before anyone's eating
How the two work together
Claude thinks it through. Paste the Claude prompt into Claude Code, or drop the folder into your skills folder. Claude does the judgement: what to look for, what is worth doing, what is right.
Codex gets it done. At the hand-off point Claude runs Codex on your machine with one command and passes it the Codex prompt. Codex does the mechanical part and hands the result back. Claude checks it before you see it.
No API key to set up: Claude calls the Codex you already have installed. If Codex is not installed, Claude does that half itself and tells you.
Prompt for Claude
--- name: allergen-incident-response description: Gives the two things a venue needs decided before an allergic reaction happens, not during one: the written allergen answer for every dish against the 14 legally defined allergens, and a fixed sequence of published facts for what staff do if a guest reacts, with no medical judgement added by this skill. Use to prepare the allergen matrix and response card before service, and to log what happened immediately after any reaction. --- # The written allergen answer, and the facts for the two minutes that matter Produces two things: a written allergen matrix checked against the 14 allergens the law defines, and a response card stating only published facts, so nobody improvises either one mid-incident. ## What it does 1. **Builds the matrix from the legal 14, not a shorter remembered list.** FSA guidance (updated 17 July 2026) states "only the 14 allergens are required to be declared as allergens by food law": celery, cereals containing gluten, crustaceans, eggs, fish, lupin, milk, molluscs, mustard, peanuts, sesame, soybeans, sulphur dioxide and sulphites (above 10mg/kg), tree nuts. 2. **Puts information in writing, because the law changed what "ask the waiter" means.** SI 2019/1218 (Natasha's Law), in force since 1 October 2021, requires food "prepacked for direct sale" to carry a label with the full ingredients list, allergens emphasised. For table service, FSA guidance says businesses "can provide allergen information for non-prepacked foods by any means such as: full written... on a menu, chalkboard or in an information pack," or verbally with a visible written notice, and that writing "supported by a conversation, works best." 3. **States the response as published facts, not medical advice.** NHS guidance on anaphylaxis says "call 999" for sudden swelling of "lips, mouth, throat or tongue," that it "needs to be treated in hospital immediately," and symptoms "usually start within minutes." The card adds only: use their own prescribed auto-injector if carried, give no food or drink, stay with them. 4. **Logs the incident immediately.** What was ordered, what information was given and how, what happened, and the times of any 999 call or auto-injector use. 5. **Flags enforcement exposure.** FSA guidance states local authorities enforce this, an unmet improvement notice brings a penalty, and the business has "14 days to appeal," with prosecution possible. ## Then it checks 1. Every menu item is checked against all 14 named allergens. 2. Every prepacked-for-direct-sale item carries a compliant label. 3. Every non-prepacked item has written information, not verbal-only. 4. The response card states only the published sequence, with no diagnosis or dosage instruction. 5. Any reaction is logged immediately with times recorded. Any check fails: name it, redo that step once. Failed twice: say what is wrong and stop. ## Rules - Public information only. Never invent a fact, a number or a quote. Anything sent in someone's name says whose name it is. - Never give medical advice; staff are never told to assess severity or decide whether to call 999. - Never claim a dish is "allergen-free" beyond what the written information actually states. - A working record and card for the owner to put in place and train staff on; not medical advice. ## Built from - FSA, "Allergen guidance for food businesses", https://www.gov.uk/government/publications/allergen-guidance-for-food-businesses/allergen-guidance-for-food-businesses, updated 17 July 2026, read 4 Nov 2026. - Food Information (Amendment) (England) Regulations 2019, SI 2019/1218, https://www.legislation.gov.uk/uksi/2019/1218/made, in force 1 Oct 2021, read 4 Nov 2026. - NHS, "Anaphylaxis - Treatment", https://www.nhs.uk/conditions/anaphylaxis/treatment/, read via search 4 Nov 2026.
Prompt for Codex
# allergen-incident-response ## You are given The full menu with ingredients as supplied by the kitchen, and for each dish whether it is `non_prepacked` or `ppds`. Any incident record: what was ordered, what allergen information was given and how, what happened, whether 999 or an auto-injector was used and at what time, and who was present. The published response card, already written by Claude, not drafted here. ## Produce Write into a `./allergen-incident-response-output/` folder: 1. `allergen-matrix.csv` with columns: `dish_name`, `celery`, `cereals_gluten`, `crustaceans`, `eggs`, `fish`, `lupin`, `milk`, `molluscs`, `mustard`, `peanuts`, `sesame`, `soybeans`, `sulphur_dioxide`, `tree_nuts`, `cross_contamination_risk_noted`. Each allergen column is `present`, `absent`, or `may contain` exactly as supplied, never inferred from the dish name. `cross_contamination_risk_noted` is `yes` or `no`. 2. `ppds-label-check.csv` with columns: `dish_name`, `is_ppds`, `label_present`, `full_ingredients_listed`, `allergens_emphasised`, `verdict`. `verdict` is `pass` or `fail: regulation 5A not met`. Any `is_ppds` row with `label_present` as `no` is automatically `fail`. 3. `non-prepacked-info-check.csv` with columns: `dish_name`, `written_method_used`, `verbal_only`, `verdict`. `written_method_used` is exactly one of `menu`, `chalkboard`, `information_pack`, `written_notice_plus_verbal`, `none`. `verbal_only` is `yes` or `no`. `verdict` is `pass` or `fail: no written fallback recorded`. 4. `incident-log.csv`, appended to any previous log, never overwritten, with columns: `incident_date`, `incident_time`, `dish_ordered`, `allergen_info_given`, `info_method`, `reaction_observed`, `symptom_onset_time`, `called_999`, `call_999_time`, `auto_injector_used`, `auto_injector_time`, `staff_present`, `response_card_followed`. `called_999` and `auto_injector_used` are `yes` or `no`. `response_card_followed` is `yes`, `no`, or `partially` with a note in `gaps.md` if not `yes`. 5. `gaps.md` - a numbered list of: any blank allergen column; any failing PPDS label check; any non-prepacked dish verbal-only with no fallback; any `response_card_followed` not `yes`; and any missing time for a 999 call or auto-injector use marked `yes`. ## Rules - Codex checks the menu and log against the supplied allergen list and response card. It never decides what a dish contains, never writes or edits the response card, and never gives medical advice or a severity assessment. - The 14 allergen columns are fixed and exhaustive; never add, rename, or merge one. - Never mark `ppds-label-check.csv` `pass` without both a full ingredients list and allergens emphasised, as supplied. - Never infer an allergen from a dish's name or cuisine; an unlisted allergen is a gap, never assumed absent. - Incident log rows are appended, never edited or deleted. - British English, GBP, DD Month YYYY dates. No em dashes. - Every file ends: this is a working allergen record and incident log for the owner to act on; not medical advice, and any reaction must be treated by emergency services. ## Return The absolute path and row count of each file. Dishes with every allergen column complete versus blank. PPDS dishes passing versus failing. Non-prepacked dishes verbal-only. Incident rows added, with `response_card_followed` for each. The `gaps.md` item count.
Built from the best public work on this
Sources for allergen-incident-response
1. Food Standards Agency, "Allergen guidance for food businesses"
https://www.gov.uk/government/publications/allergen-guidance-for-food-businesses/allergen-guidance-for-food-businesses, published 2 April 2020, updated 17 July 2026, read 4 November 2026.
Section 1 gives the exact list: "The 14 allergens are: celery, cereals containing gluten (such as wheat, rye, barley and oats), crustaceans (such as prawns, crabs and lobsters), eggs, fish, lupin, milk, molluscs (such as mussels and oysters), mustard, peanuts, sesame, soybeans, sulphur dioxide and sulphites (if the sulphur dioxide and sulphites are at a concentration of more than ten parts per million), tree nuts (such as almonds, hazelnuts, walnuts, brazil nuts, cashews, pecans, pistachios and macadamia nuts)," and states "only the 14 allergens are required to be declared as allergens by food law." This is the fixed list behind step 1 and the `allergen-matrix.csv` columns.
Section 2.5, on non-prepacked (loose) foods, is quoted in full in the skill: businesses "can provide allergen information for non-prepacked foods by any means such as: full written allergen information on a menu, chalkboard or in an information pack" or "verbally, with a written notice placed in a clearly visible position explaining how your customers can obtain this information," and "our advice to food businesses providing non-prepacked food is that written allergen information, supported by a conversation, works best for consumers." This is behind step 2's written-plus-conversation standard.
Section 5, "Enforcement and penalties," states: "Local authorities enforce allergen information regulations. Failure to comply can result in action from the local authority. If you fail to act on advice given by the local authority, an improvement notice may be issued. If you do not meet the requirements of this notice, you will be issued with a penalty. You have 14 days to appeal an improvement notice from the date the notice was issued. In some cases businesses may also face prosecution." This is behind step 5.
Where the skill departs: the page's sections on free-from and gluten-free claims, and on manufacturer and institutional-caterer guidance, are not used here, since this skill is written for a table-service or takeaway venue, not a manufacturer.
2. The Food Information (Amendment) (England) Regulations 2019, SI 2019/1218
https://www.legislation.gov.uk/uksi/2019/1218/made, made 4 September 2019, laid 5 September 2019, in force 1 October 2021, read 4 November 2026.
This instrument, known as Natasha's Law, inserts regulation 5A into the Food Information Regulations 2014 (SI 2014/1855). The inserted text reads: "A food business operator who offers for sale a food to which this regulation applies must provide directly on the package or on a label attached to the package the particulars required by... Article 9(1)(b) (list of ingredients)... Article 9(1)(c) (labelling of certain substances or products causing allergies or intolerances)," applying to a food that "is offered for sale to a final consumer or to a mass caterer" and "is prepacked for direct sale." This is the exact legal duty behind step 2 and the `ppds-label-check.csv` in CODEX.md: a sandwich or pie made and sold from the same premises must carry a label with a full ingredients list and the allergens emphasised, not a verbal answer.
Where the skill departs: the instrument also amends regulations 6, 10 and 12 of the 2014 Regulations on naming and offences, which the skill does not separately teach, since the labelling duty in regulation 5A is the operative fact a venue needs.
3. NHS, "Anaphylaxis - Treatment"
https://www.nhs.uk/conditions/anaphylaxis/treatment/, read via search results quoting the page directly, 4 November 2026.
The page's immediate-action guidance states to "call 999" where "your lips, mouth, throat or tongue suddenly become swollen," and that "anaphylaxis needs to be treated in hospital immediately." Separately, NHS-sourced guidance states symptoms of anaphylaxis "usually start within minutes of coming into contact with something you're allergic to." These are the only facts the response card in step 3 states, word for word, and no further medical interpretation is added.
Where the skill departs: guidance on auto-injector storage, a possible second dose, and the risk of a second reaction hours later, found in NHS trust patient leaflets during research, is not included in the response card, because those are clinical judgements for a prescribed device's own instructions and for the attending ambulance crew, not facts for untrained staff to act on mid-incident. Direct access to nhs.uk was attempted and blocked by the site during this research; the quotes above come from search results that reproduced the page's own wording, and the primary page itself should be checked again before training staff from it.
Best public prompt we found for this job
The closest public artefact is PagerDuty's `incident-response-docs` repository, specifically `docs/during/during_an_incident.md`, raw source at https://raw.githubusercontent.com/PagerDuty/incident-response-docs/master/docs/during/during_an_incident.md. The repository has 1,052 stars, read from api.github.com on 4 November 2026. It is a software outage response playbook, and the closest public comparison because it is built around the same real need: a fixed, calm, written sequence for the first minutes of an incident, so nobody is improvising.
Its opening instruction is "Don't Panic!" followed by "Follow instructions from the Incident Commander," with a named role structure (Incident Commander, Deputy, scribe) for who does what during the incident. We took the underlying discipline: write the sequence down in advance, name who does what, and never leave the first minutes to be invented on the spot.
We did not copy its Incident Commander role or its investigation-and-repair framing. A software outage is diagnosed and fixed by the people in the room; an allergic reaction is not diagnosed or treated by venue staff at all; the entire first action is to call the people who can. Building a role hierarchy or a "decide the cause" step into an allergen response card would invite exactly the kind of staff judgement call this skill exists to remove. The only content that belongs in a response card for a reaction is the handful of published facts in source 3, not a decision process.
Want this running in your business?
I optimise how businesses run — your sales, your visibility, your social media — and build bespoke software where nothing off the shelf fits. The first conversation is free. Work starts from £150 a day.
Foxera