본문으로 건너뛰기
cccskills
무료GitHub에 공개

compounding-record

Write a compounding worksheet and record that reproduces the preparation exactly and survives inspection — formula, calculations shown, components with lot numbers, in-process checks, and the beyond-use date with its basis. Use when asked to document a compounded preparation, write a master formulation record, create a compounding worksheet, or prepare compounding documentation for inspection. Produces the master formula, the batch record, the component and lot table, in-process checks, labelling, and the beyond-use-date rationale. Documentation only; standards and stability data must come from current official references.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(1)

  • SKILL.md6.1 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Compounding Record

A compounding record has two readers: the person repeating the preparation next month, and an inspector asking how you arrived at a beyond-use date. Both need the same thing — the arithmetic visible, the components traceable to lot, and the reasoning written down rather than remembered. This produces a record that answers both without a phone call.

What This Skill Produces

  • The master formulation record — the reproducible formula, separate from any single batch
  • The batch record — this preparation, with every calculation shown rather than just its result
  • A component table — each ingredient with source, lot number, expiry, and quantity used
  • In-process checks — what was verified during preparation, by whom, and at what point
  • Beyond-use date with its basis — the date and the reference or data it derives from, which is what inspection asks about
  • The label and its required elements — assembled against your jurisdiction's requirements

Required Inputs

Ask for these if not provided:

  • The preparation — final product, strength, dosage form, and total quantity
  • The formula — ingredients and amounts, and the source of the formula
  • The components — actual products used, with lot numbers and expiry dates
  • Equipment and environment — what was used and where, including any controlled environment
  • The standards you work to — your jurisdiction's compounding standard and the reference used for beyond-use dating

Framework: Show the Arithmetic, Trace the Lot, Justify the Date

  1. Separate the master formula from the batch. The master is the recipe and does not change; the batch is what happened today. Conflating them is the most common documentation failure.
  2. Write every calculation out. Including the aliquot arithmetic and any potency or salt-form adjustment. A result without its working cannot be checked, and checking is the point.
  3. Have the calculation verified independently where your standard requires it, and record who verified.
  4. Trace every component to a lot. An ingredient without a lot number makes a recall impossible.
  5. Derive the beyond-use date, do not choose it. State the reference or stability data it comes from. 'Thirty days' with no basis is the finding inspectors write up.
  6. Record the in-process checks as they happen. Weight verification, appearance, pH, mixing time — at the point of the check, not reconstructed afterwards.

Output Format

Compounding record: [preparation] · [batch/Rx no.] · [date]

MASTER FORMULATION RECORD Preparation: [name, strength, dosage form] · Source of formula: [reference]

IngredientAmount per unitRole
[ingredient][amount][active / vehicle / preservative]
Equipment: [list] · Environment: [bench / controlled area, classification]

BATCH RECORD Quantity prepared: [amount] · Prepared by: [name] · Date/time: [when]

Calculations — shown in full

[the working, step by step, including aliquots and any potency or salt-form adjustment]

Verified by: [second person, where required] · [date/time]

Components used

IngredientManufacturer/sourceLotExpiryQuantity used

In-process checks: [weight verification · appearance · pH · mixing time — each with the result, who checked, and when]

Final product: appearance [description] · yield [actual vs theoretical] · discrepancy investigated: [if any]

Beyond-use date: [date] · Basis: [the reference, stability data, or standard relied on — cited]

Label: [product, strength, quantity, BUD, storage, prepared-by, batch number, and every element your jurisdiction requires]

A documentation framework only. Compounding standards, permitted preparations, environmental requirements, verification rules and beyond-use dating are governed by your jurisdiction's official standards and must be taken from current official references — never from this template and never from recall. Sterile compounding carries requirements this structure does not attempt to cover.

Quality Checks

  • Master formula and batch record are separate documents
  • Every calculation is written out, not just its result
  • Independent verification is recorded where the standard requires it
  • Every component has a lot number and expiry
  • In-process checks were recorded at the time, with the checker named
  • Actual yield is compared against theoretical, and any discrepancy is investigated
  • The beyond-use date cites the specific basis it derives from

Anti-Patterns

  • A result with no working. Uncheckable, and the first thing an inspector asks to see.
  • Components without lot numbers. Makes a recall impossible and is a serious finding.
  • A beyond-use date by habit. '30 days' with no cited basis is written up every time.
  • Reconstructing in-process checks afterwards. A check recorded later is not a check.
  • One document for formula and batch. The recipe becomes unreproducible once it is entangled with a single day's numbers.
  • Ignoring a yield discrepancy. An uninvestigated shortfall is the sign of an error nobody chased.

Example Trigger Phrases

  • "Write a compounding record for this suspension"
  • "Create a master formulation record"
  • "How do I document beyond-use dating for an inspection?"
  • "We are being inspected — what should our compounding records show?"
  • "Write a batch record with the calculations shown"

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mohitagw15856/pm-claude-skills1.5천2026년 10월 17일 업데이트

Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mohitagw15856/pm-claude-skills1.5천2026년 10월 17일 업데이트

Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mohitagw15856/pm-claude-skills1.5천2026년 10월 17일 업데이트

Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mohitagw15856/pm-claude-skills1.5천2026년 10월 17일 업데이트

Build or tailor an academic CV for faculty, postdoc, research or fellowship applications: publications, grants, teaching, supervision and service in the order the field expects, with consistent citations. Use when asked to write my academic CV, update my CV for a lectureship, tenure-track or postdoc application, format my publications list, or adapt my academic CV for an industry research role. Produces the full academic CV, a field-appropriate section order, a clean publications list in one citation style, and a two-page summary version when asked.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mohitagw15856/pm-claude-skills1.5천2026년 10월 17일 업데이트

Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mohitagw15856/pm-claude-skills1.5천2026년 10월 17일 업데이트

mohitagw15856의 스킬 모두 보기

이 스킬의 문제 신고