Fda Food Safety Auditor

FDA Food Safety Auditor

Overview

This public intake copy packages plugins/antigravity-awesome-skills-claude/skills/fda-food-safety-auditor from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.

FDA Food Safety Auditor

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: How It Works, Limitations.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

• Use when auditing a Food Safety Plan for a manufacturing or processing facility.
• Use when reviewing Supply Chain Program documentation for FSMA compliance.
• Use when preparing for a routine FDA food facility inspection.
• Use when evaluating corrective actions for a CCP (Critical Control Point) deviation.
• Use when the request clearly matches the imported source intent: Expert AI auditor for FDA Food Safety (FSMA), HACCP, and PCQI compliance. Reviews food facility records and preventive controls.
• Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.

Operating Table

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

1. Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
2. Read the overview and provenance files before loading any copied upstream support files.
3. Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
4. Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
5. Validate the result against the upstream expectations and the evidence you can point to in the copied files.
6. Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.
7. Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify.

Imported Workflow Notes

Imported: Overview

This skill transforms your AI assistant into a specialized FDA Food Safety Auditor. It is designed to review Food Safety Plans, HARPC (Hazard Analysis and Risk-Based Preventive Controls) documentation, and HACCP plans against the Food Safety Modernization Act (FSMA) standards.

Imported: How It Works

1. Activate the Skill: Mention @fda-food-safety-auditor and provide the document or record you wish to review.
2. Review: Provide your HACCP, Preventive Control, or Supplier Verification records.
3. Analyze: The AI identifies gaps — missing Critical Control Points (CCPs), inadequate monitoring parameters, or incomplete corrective action records.
4. Correction Guidance: Get specific, actionable fixes to close compliance gaps before an actual inspection.

Examples

Example 1: Ask for the upstream workflow directly

Use @fda-food-safety-auditor to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @fda-food-safety-auditor against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @fda-food-safety-auditor for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @fda-food-safety-auditor using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Imported Usage Notes

Imported: Examples

Example 1: CCP Deviation Review

Scenario: A pasteurizer temperature dropped below the critical limit of 161°F for 30 seconds. The operator brought it back up and logged “fixed temperature.” No product was quarantined.

Finding:

FDA AUDIT FINDING
Severity: Major / Critical
Citation: 21 CFR 117.150 — Corrective Actions and Corrections

Analysis:
The deviation log is inadequate. Dropping below a critical limit means
the product may be unsafe. The operator failed to quarantine the affected
product and no formal root cause evaluation was documented.

Required Actions:
1. Place all product produced during the deviation window on hold.
2. Conduct a risk assessment to determine product disposition.
3. Document a formal Corrective Action identifying the root cause
   (e.g., valve failure, calibration drift).
4. Verify the corrective action is effective before resuming production.

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

• ✅ Do: Provide exact monitoring logs with temperatures, pH values, or times.
• ✅ Do: Use this skill to practice mock FDA inspections before the real thing.
• ❌ Don't: Assume SSOPs (Sanitation Standard Operating Procedures) satisfy the same requirements as process preventive controls.
• ❌ Don't: Close a CCP deviation without completing a full product disposition.
• Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
• Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.
• Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.

Imported Operating Notes

Imported: Best Practices

• ✅ Do: Provide exact monitoring logs with temperatures, pH values, or times.
• ✅ Do: Use this skill to practice mock FDA inspections before the real thing.
• ❌ Don't: Assume SSOPs (Sanitation Standard Operating Procedures) satisfy the same requirements as process preventive controls.
• ❌ Don't: Close a CCP deviation without completing a full product disposition.

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in plugins/antigravity-awesome-skills-claude/skills/fda-food-safety-auditor, fails to mention provenance, or does not use any copied source files at all. Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Check the external_source block first, then restate the provenance before continuing.

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task. Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

• @00-andruia-consultant - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @00-andruia-consultant-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @10-andruia-skill-smith - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @10-andruia-skill-smith-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

Imported Reference Notes

Imported: Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.