本文へ移動
cccskills
無料GitHub で公開

controlled-substance-audit

Reconcile controlled-substance records and prepare for an inspection — the count against the register, the discrepancy investigation, the documentation an inspector asks for, and the reporting obligations a shortfall triggers. Use when asked to reconcile controlled drugs, prepare for a DEA or controlled-drug inspection, investigate a discrepancy or suspected diversion, or audit the CD register. Produces the reconciliation, the discrepancy investigation record, the inspection-readiness checklist, and the escalation and reporting decision tree. A process framework only; reporting thresholds, timelines and obligations are set by law in your jurisdiction and must be verified there.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md6.5 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Controlled Substance Reconciliation & Audit

A controlled-substance discrepancy is a countdown, not a puzzle. There are legal reporting obligations with real deadlines, an investigation that has to be documented as it happens rather than reconstructed, and a serious possibility that a colleague is unwell. This structures the reconciliation, the investigation, and the decision about who must be told and by when.

What This Skill Produces

  • The reconciliation — physical count against the register, by product and strength, with the arithmetic shown
  • A discrepancy investigation record — the sequence checked, documented as you go
  • The inspection-readiness checklist — the records, storage, and access controls an inspector examines
  • The escalation and reporting decision — what threshold triggers which obligation, and by when
  • The diversion considerations — handled as a personnel and welfare matter, not only a stock one
  • The corrective actions — what changes so the same gap does not recur

Required Inputs

Ask for these if not provided:

  • The scope — which products, which period, and what triggered the audit
  • The records — register, invoices, dispensing records, destruction records, and returns
  • The physical count — actual quantities held, counted by whom and when
  • Access — who has access to the safe or cabinet, and what the access log shows
  • Your legal framework — the controlled-substance rules, reporting thresholds and deadlines that apply where you practise

Framework: Count, Trace, Escalate on the Clock

  1. Count with a witness where required, and record both names. A single-person count is contestable and, in many jurisdictions, non-compliant.
  2. Reconcile against every movement, not just dispensing. Receipts, returns, wastage, destruction and transfers all move the number.
  3. Trace a discrepancy backwards to the last known-good count. Working forwards from the start of the period is slower and usually inconclusive.
  4. Check arithmetic and transcription first. Most discrepancies are recording errors, and ruling them out quickly is what makes the remainder credible.
  5. Document the investigation as it happens. A reconstructed investigation is worth very little to a regulator.
  6. Start the reporting clock the moment a loss is established. Deadlines are short, statutory, and not extended by an ongoing internal investigation.
  7. Treat suspected diversion as a welfare matter too. Impairment among colleagues is a health issue with a professional-support route, alongside whatever the law requires.

Output Format

CD reconciliation: [period] · [site] · [conducted by]

Scope: [products, strengths, period] · Trigger: [routine / discrepancy noticed / inspection prep]

Reconciliation

Product & strengthOpeningReceivedDispensedWasted/destroyedReturnedExpectedCountedVariance

Count witnessed by: [name] · Date/time: [when]

Discrepancy investigation — for each variance

  1. Arithmetic and transcription re-checked: [outcome]
  2. Traced back to last known-good count on [date]: [what the trace showed]
  3. Movements re-examined: receipts [ ] returns [ ] wastage [ ] destruction [ ] transfers [ ]
  4. Access log reviewed for the window: [what it showed]
  5. Conclusion: [recording error / stock error / unexplained loss] · Established at: [date/time — this starts any reporting clock]

Reporting decision: ☐ None required ☐ Internal only ☐ Regulator/authority — [which, by when, under what provision] ☐ Law enforcement Reported: [to whom, when, by whom, reference number]

Personnel considerations: [handled under HR and welfare policy · professional support route offered · no conclusion recorded about any individual without process]

Corrective actions: [what changes · owner · date] · Inspection readiness gaps closed: [list]

A process framework only. Controlled-substance record-keeping, count frequency, witness requirements, loss-reporting thresholds and reporting deadlines are set by law and differ sharply by jurisdiction. Verify every obligation against the actual statute and your regulator before relying on any step here, and take legal advice where a loss may have occurred.

Quality Checks

  • The count was witnessed and both names are recorded
  • Every movement type is reconciled, not only dispensing
  • Arithmetic and transcription errors were ruled out before anything else
  • The investigation was documented as it proceeded
  • The moment the loss was established is recorded, because deadlines run from it
  • The reporting obligation was checked against the actual legal provision
  • Personnel matters were routed through HR and welfare, not concluded in the audit record

Anti-Patterns

  • Counting alone. Contestable, and non-compliant in many jurisdictions.
  • Waiting for the investigation to finish before reporting. Statutory deadlines do not pause for internal process.
  • Reconciling dispensing only. Wastage and destruction are where records most often break.
  • Naming a suspect in the audit record. Serious, prejudicial, and properly a matter for a separate process.
  • Reconstructing the investigation afterwards. A regulator can tell, and it undermines everything else.
  • Fixing the count without fixing the control. The same variance returns next quarter.
  • Treating suspected diversion purely as theft. Impairment is a health issue with a support pathway.

Example Trigger Phrases

  • "Reconcile our controlled drug register"
  • "We are short on a controlled substance — what do I do?"
  • "Prepare for a controlled-drug inspection"
  • "How do I investigate a CD discrepancy?"
  • "What are our reporting obligations for a controlled substance loss?"

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

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,4412026年10月13日 更新

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,4412026年10月13日 更新

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,4412026年10月13日 更新

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,4412026年10月13日 更新

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,4412026年10月13日 更新

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,4412026年10月13日 更新

mohitagw15856 のスキルをすべて見る

このスキルの問題を報告する