Prepare Inspection Readiness

Prepare an organisation for regulatory inspection by assessing readiness against agency-specific focus areas (FDA, EMA, MHRA). Covers warning letter and 483 theme analysis, mock inspection protocols, document bundle preparation, inspection logistics, and response template creation. Use when a regulatory inspection has been announced or is anticipated, when a periodic self-assessment is due, when new systems have been implemented since the last inspection, or after a significant audit finding that may attract regulatory attention.

45 stars 4 forksFrontend & Design

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add pjt222/agent-almanac --skill prepare-inspection-readiness
Manual install
git clone --depth 1 https://github.com/pjt222/agent-almanac.git /tmp/agent-almanac
mkdir -p ~/.claude/skills
cp -r /tmp/agent-almanac/i18n/caveman-lite/skills/prepare-inspection-readiness ~/.claude/skills/prepare-inspection-readiness

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Prepare Inspection Readiness

Assess and improve organisational readiness for regulatory inspection, covering documentation, personnel preparation, logistics, and response planning.

## When to Use

- A regulatory inspection has been announced or is anticipated
- Periodic self-assessment of inspection readiness is due
- New systems or processes have been implemented since the last inspection
- Industry trends (warning letters, 483s) indicate an emerging focus area
- After a significant audit finding that may attract regulatory attention

## Inputs

- **Required**: Inspecting authority (FDA, EMA, MHRA, or other)
- **Required**: Expected inspection scope (data integrity, CSV, GMP, GLP, GCP)
- **Required**: Compliance architecture and system inventory
- **Optional**: Previous inspection reports and observations
- **Optional**: Recent industry warning letters and 483 themes
- **Optional**: Open CAPAs and audit findings

## Procedure

### Step 1: Analyse Agency-Specific Focus Areas

Research the inspecting authority's current priorities:
Read the full skill on GitHub

Details

Skill name
prepare-inspection-readiness
Path
i18n/caveman-lite/skills/prepare-inspection-readiness/SKILL.md
License
MIT
Repo updated
18 November 2026

FAQ

What does the Prepare Inspection Readiness skill do?

Prepare an organisation for regulatory inspection by assessing readiness against agency-specific focus areas (FDA, EMA, MHRA). Covers warning letter and 483 theme analysis, mock inspection protocols, document bundle preparation, inspection logistics, and response template creation. Use when a regulatory inspection has been announced or is anticipated, when a periodic self-assessment is due, when new systems have been implemented since the last inspection, or after a significant audit finding that may attract regulatory attention.

How do I install the Prepare Inspection Readiness skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add pjt222/agent-almanac --skill prepare-inspection-readiness. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Prepare Inspection Readiness popular?

It lives in pjt222/agent-almanac, which has 45 GitHub stars and 4 forks, and is included in 1 curated skill list.

Related skills

Adapt Architecture

45

pjt222/agent-almanac

Execute structural metamorphosis using strangler fig migration, chrysalis phases, and interface preservation. Covers transformation planning, parallel running, progressive cutover, rollback design, and post-metamorphosis stabilization for system architecture evolution. Use when assess-form has classified the system as READY for transformation, when migrating from monolith to microservices, when replacing a core subsystem while dependents continue operating, or when any architectural change must be gradual rather than big-bang.

Software DevelopmentIn 1 list

Adaptic

45

pjt222/agent-almanac

Master skill composing the 5-step synoptic cycle for panoramic synthesis across multiple domains. Orchestrates meditate, expand-awareness, observe, awareness, integrate-gestalt, and express-insight into a coherent process that produces unified understanding rather than sequential compromise. Use when a problem genuinely spans 3+ domains and the interactions between domains matter more than depth in any one, when sequential analysis feels like compromise rather than integration, or before major architectural decisions affecting multiple stakeholders.

OtherIn 1 list

Add Puzzle Type

45

pjt222/agent-almanac

Scaffold a new puzzle type across all 10+ pipeline integration points in jigsawR. Creates the core puzzle module, wires it into the unified pipeline (generation, positioning, rendering, adjacency), adds ggpuzzle geom/stat layers, updates DESCRIPTION and config.yml, extends the Shiny app, and creates a comprehensive test suite. Use when adding a completely new puzzle type to the package or following the 10-point integration checklist to ensure nothing is missed end-to-end.

Testing & QAIn 1 list

Product UX Audit

41

wolverin0/claude-skills

Audits application usability with a focus on tasks, interaction design and information architecture. Evaluates user journeys, duplicated actions, avoidable steps, containers (modals, side panels, dedicated pages), forms, error handling and notification or pending-work policies in operational products (ERP, CRM, dashboards). Prepares before/after visual comparisons with selectable recommendations and keeps interaction decisions in DESIGN.md.

Frontend & Design

Oss Review

43

AlsKozlov/ru-legal

Review OSS (open-source) лицензий используемых в продукте. Universal + РФ specifics: ст.1286 ГК — лицензионный договор; OSS лицензии классифицируются по copyleft strength; potentially conflicting комбинации; РФ-specific considerations для IT-аккредитации (реестр Минцифры) — ограничения по OSS components.

Frontend & Design

Render Icon Pipeline

45

pjt222/agent-almanac

Run the viz pipeline to render icons from existing glyphs. Entry point for the viz subproject covering palette generation, data building, manifest creation, and icon rendering for skills, agents, and teams. Always use build.sh as the pipeline entry point — never call Rscript directly.

Frontend & DesignIn 1 list

Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.