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.

55

Quality

63%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/fda-food-safety-auditor/SKILL.md

The canonical home for this skill is fda-food-safety-auditor in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

61%Weight 40%Scale 1-5

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

The body is well-structured and delivers a concrete, reusable audit-finding template with a real CFR citation, but the How-It-Works workflow lacks validation checkpoints and the opening framing adds minor padding. Tightening the prose and adding a verify-before-reporting step would raise the weakest dimensions.

Suggestions

Add an explicit validation checkpoint in the workflow (e.g., 'Before issuing a finding, confirm the gap against the cited CFR subsection and the supplied record') to support workflow_clarity.

Trim the 'This skill transforms your AI assistant into...' framing and tighten the 'Analyze' step into concrete checks (CCP presence, monitoring parameters, corrective-action completeness).

Consider extracting the finding template into a references file (e.g. FINDING_TEMPLATE.md) if the skill grows, to keep SKILL.md a lean overview.

DimensionReasoningScore

Conciseness

Mostly efficient with useful acronym expansions, but includes unnecessary framing ('This skill transforms your AI assistant into a specialized FDA Food Safety Auditor') and slightly hand-wavy How-It-Works prose that could be tightened.

3 / 5

Actionability

Provides a copy-paste-ready audit-finding template with a real citation (21 CFR 117.150) and numbered required actions, plus concrete Do/Don't best practices; minor gaps remain in the vaguer 'Analyze' step.

4 / 5

Workflow Clarity

A 4-step sequence (Activate, Review, Analyze, Correction Guidance) is present but lacks explicit validation checkpoints or feedback loops to confirm gaps are real before reporting.

3 / 5

Progressive Disclosure

Well-organized into clear sections (Overview, When to Use, How It Works, Examples, Best Practices) with no nested references and no bundle files needed for this short, single-file skill; minor room to formalize structure.

4 / 5

Total

14

/

20

Passed

Description

65%Weight 40%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 is specific to a well-defined niche and uses natural domain keywords, but it omits any explicit 'Use when...' trigger guidance, which caps completeness and limits its usefulness as a trigger surface. Adding concrete trigger phrases would lift the completeness and trigger-term dimensions.

Suggestions

Append an explicit trigger clause, e.g. 'Use when auditing a Food Safety Plan, reviewing HACCP/PCQI records, or preparing for an FDA FSMA inspection.'

Expand the action list beyond 'reviews' to concrete verbs (e.g., 'identifies CCP gaps, verifies corrective actions, checks supplier verification records') to improve specificity.

Add common synonyms users might say ('food safety plan', 'preventive controls plan', 'supply chain program') to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the domain (FSMA, HACCP, PCQI) and one concrete action ('Reviews food facility records and preventive controls'), but lists only 1-2 actions rather than the multiple specific actions that mark comprehensive coverage.

3 / 5

Completeness

The 'what' is clear ('Expert AI auditor... Reviews food facility records and preventive controls') but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Strong domain keywords a user would actually say ('FDA Food Safety', 'FSMA', 'HACCP', 'PCQI', 'preventive controls'); a few natural synonyms or trigger phrasings are missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear, narrow niche (FDA FSMA/HACCP/PCQI compliance auditing) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

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.