CtrlK
BlogDocsLog inGet started
Tessl Logo

fda-food-safety-auditor

Expert AI auditor for FDA Food Safety (FSMA), HACCP, and PCQI compliance. Reviews food facility records and preventive controls.

43

Quality

44%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/fda-food-safety-auditor/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

36%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill reads more like a product description or marketing page than an actionable instruction set for Claude. It explains what the skill does rather than how to perform FDA food safety audits. The single example is the strongest element, providing a concrete output format, but the skill lacks structured audit procedures, decision frameworks, and validation steps that would make it truly useful for compliance review.

Suggestions

Replace the 'How It Works' section with a concrete audit workflow: e.g., 1) Identify facility type and applicable CFR sections, 2) Check for required plan elements (hazard analysis, preventive controls, monitoring procedures, corrective actions, verification, recall plan), 3) Validate each element against specific regulatory requirements, 4) Generate findings with severity and citations.

Add a structured checklist or decision tree for common audit areas (HARPC elements, supply chain program, recall plan, allergen controls) with specific CFR citations for each requirement.

Remove the 'Overview' and 'When to Use This Skill' sections — Claude doesn't need to be told when to use a skill or what FDA/FSMA/HACCP are. Use that space for actionable audit criteria instead.

Add more examples covering different finding types (e.g., missing hazard analysis, inadequate supplier verification, incomplete recall plan) to demonstrate the expected output format across common scenarios.

DimensionReasoningScore

Conciseness

The content extensively explains concepts Claude already knows (what FSMA is, what CCPs are, what HACCP plans are). The 'Overview' and 'When to Use This Skill' sections are padded with information that doesn't add actionable value. The 'How It Works' section describes a generic interaction pattern rather than providing useful instructions.

2 / 5

Actionability

The example CCP deviation review provides a concrete output format with specific CFR citations and required actions, which is useful. However, the skill lacks executable steps — there are no checklists, decision trees, or structured audit procedures Claude should follow. It describes what the skill does rather than instructing Claude how to perform the audit.

3 / 5

Workflow Clarity

The 'How It Works' section lists 4 high-level steps (Activate, Review, Analyze, Correction Guidance) but these are vague descriptions of an interaction flow, not an audit workflow. There are no validation checkpoints, no structured sequence for conducting an audit, and no feedback loops for verifying corrective actions are adequate. For a skill involving compliance auditing (where errors have safety consequences), this is insufficient.

2 / 5

Progressive Disclosure

The content is structured with clear section headers (Overview, When to Use, How It Works, Examples, Best Practices), which aids navigation. However, there are no bundle files or references to supporting materials (e.g., a CFR citation reference, audit checklist template, or common findings database), and the content that exists could benefit from being more concise in the overview with detailed audit procedures in separate files.

3 / 5

Total

10

/

20

Passed

Description

52%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description identifies a clear and specialized domain (FDA food safety compliance) with relevant regulatory acronyms that serve as good trigger terms. However, it lacks a 'Use when...' clause, which is critical for skill selection, and the specific capabilities listed are limited to 'reviews records and preventive controls' without detailing what concrete outputs or analyses the skill performs.

Suggestions

Add an explicit 'Use when...' clause with trigger phrases like 'Use when the user asks about FSMA compliance, HACCP plans, food safety audits, preventive controls, or FDA food facility inspections.'

Expand the concrete actions to include specific tasks such as 'conducts hazard analysis, reviews food safety plans, evaluates corrective actions, assesses supplier verification programs, and generates audit reports.'

Include additional natural trigger terms and synonyms like 'food safety plan', 'hazard analysis', 'sanitation controls', 'recall plan', 'cGMP', and 'supply chain program'.

DimensionReasoningScore

Specificity

Names the domain (FDA food safety compliance) and mentions two concrete actions ('reviews food facility records' and 'preventive controls'), but doesn't elaborate on specific tasks like gap analysis, corrective action review, hazard analysis, or report generation.

3 / 5

Completeness

Has a reasonable 'what' (auditor for FDA food safety compliance, reviews records and preventive controls) but completely lacks a 'when' clause. There is no explicit guidance on when Claude should select this skill, which caps this dimension at 3, and the 'what' is also somewhat vague, bringing it to 2.

2 / 5

Trigger Term Quality

Includes several strong natural trigger terms: 'FDA', 'Food Safety', 'FSMA', 'HACCP', 'PCQI', 'food facility records', 'preventive controls'. Missing some common variations like 'food safety plan', 'hazard analysis', 'sanitation controls', 'recall plan', or 'supply chain program'.

4 / 5

Distinctiveness Conflict Risk

The combination of FDA, FSMA, HACCP, and PCQI creates a fairly distinct niche that is unlikely to overlap with general document review or other compliance skills. Minor overlap risk with broader regulatory or food industry skills.

4 / 5

Total

13

/

20

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.