Implement Pharma Serialisation
Implement pharmaceutical serialisation and track-and-trace systems compliant with EU FMD, US DSCSA, and other global regulations. Covers unique identifier generation, aggregation hierarchy, EPCIS data exchange, and verification endpoint integration. Use when implementing serialisation for a new product launch, integrating with the EMVS/NMVS, designing DSCSA-compliant transaction exchange, building an EPCIS event repository, or extending serialisation to additional markets (China, Brazil, Russia).
Install
npx skills add pjt222/agent-almanac --skill implement-pharma-serialisationgit 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/implement-pharma-serialisation ~/.claude/skills/implement-pharma-serialisationPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Implement Pharmaceutical Serialisation Set up pharmaceutical serialisation systems for regulatory compliance with global track-and-trace mandates. ## When to Use - Implementing serialisation for a new product launch in the EU or US market - Integrating with the European Medicines Verification System (EMVS/NMVS) - Designing DSCSA-compliant transaction information exchange - Building or integrating an EPCIS event repository for supply chain visibility - Extending serialisation to additional markets (China NMPA, Brazil ANVISA, etc.) ## Inputs - **Required**: Product information (GTIN, product code, dosage form, pack sizes) - **Required**: Target market regulations (EU FMD, DSCSA, or both) - **Required**: Packaging hierarchy (unit, bundle, case, pallet) - **Optional**: Existing ERP/MES system details for integration - **Optional**: Contract manufacturer serialisation capabilities - **Optional**: Verification endpoint specifications ## Procedure ### Step 1: Understand the Regulatory Landscape | Regulation | Region | Key Requirements | Deadline | |---|---|---|---| | EU FMD (2011/62/EU) | EU/EEA | Unique identifier + tamper-evident feature on each unit | Live since Feb 2019 | | DSCSA | USA | Electronic, interoperable tracing at package level | Full enforcement Nov 2024+ | | China NMPA | China | Unique drug traceability code per minimum saleable unit | Rolling | | Brazil ANVISA (SNCM) | Brazil | Serialisation of pharmaceuticals with IUM | Rolling |
Details
- Skill name
implement-pharma-serialisation- Repository
- pjt222/agent-almanac
- Path
i18n/caveman-lite/skills/implement-pharma-serialisation/SKILL.md- License
- MIT
- Repo updated
- 18 November 2026
- Listed in
- BehiSecc/awesome-claude-skills
FAQ
What does the Implement Pharma Serialisation skill do?
Implement pharmaceutical serialisation and track-and-trace systems compliant with EU FMD, US DSCSA, and other global regulations. Covers unique identifier generation, aggregation hierarchy, EPCIS data exchange, and verification endpoint integration. Use when implementing serialisation for a new product launch, integrating with the EMVS/NMVS, designing DSCSA-compliant transaction exchange, building an EPCIS event repository, or extending serialisation to additional markets (China, Brazil, Russia).
How do I install the Implement Pharma Serialisation skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add pjt222/agent-almanac --skill implement-pharma-serialisation. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Implement Pharma Serialisation 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
45pjt222/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.
Adaptic
45pjt222/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.
Add Puzzle Type
45pjt222/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.
Infringement Triage
43AlsKozlov/ru-legal
Analysis потенциального нарушения наших IP — ТЗ / патент / авторские / ПО / БД. РФ specifics: ст.1252 ГК пресечение + конкретные способы защиты; ст.1515 ГК (для ТЗ) компенсация 10k-5М или 2× стоимость контрафактных товаров; СИП подсудность для ТЗ / патентов; антипиратский закон через Мосгорсуд для онлайн нарушений.
Implement Audit Trail
45pjt222/agent-almanac
Implement audit trail functionality for R projects in regulated environments. Covers logging, provenance tracking, electronic signatures, data integrity checks, and 21 CFR Part 11 compliance. Use when an R analysis requires electronic records compliance (21 CFR Part 11), when you need to track who did what and when in an analysis, when implementing data provenance tracking, or when creating tamper-evident analysis logs for regulatory submissions.
Inspection Defense
43AlsKozlov/ru-legal
Защита компании при проведении проверки регулятором. Права + обязанности стороны проверяемой (248-ФЗ ст.36-37). Tactical handling: проверка идентичности проверяющих, требование подтверждения оснований, document delivery, fixation proverочных actions, отказ от давления / неправомерных запросов.
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.